The 777 issue is manifesting itself as early as the aircraft selection screen where the selected airplane spins around. Previously once one of my 777s were selected as the aircraft, it would spin smoothly - now it spins like tac, tac, tac, tac, and not smoothly as the rest of my aircraft.

Some more thoughts:

 

1)  Try several different 777s.  Most have their own initialization file, with the tail number  of the aircraft [TAILNUMBER].ini.  (They are in Flight Simulator X/PMDG/pmdg 777X/Aircraft).  So if something happened to one of these files, try several different T7s, restarting FSX each time.  See if some work.  (You can tell which aircraft share the same [TAILNUMBER].ini files by looking in the PMDG Operations Center, under PMDG 777>Aircraft.)

 

2) Just occurred to me that you may not be able to change the startup panel state because you need to do this through the CDU (FMC) and don't get to load the aircraft long enough to make the change.

 

However there is another way to change/remove the startup panel state.  In the folder

Flight Simulator X/PMDG/pmdg 777X is a file called 777X_Options.ini .  Make a backup of this file and put it in a different folder.  Then open it in notepad.  The very last entry looks like this:

 

[Panel State]

StartupPanelState= [Name of current startup panel state]

 

Just delete the name of the current startup panel state (make sure there is a blank line after  that one), save it, start FSX and see if the problem is still there.

 

Mike

Hello Gang!  Thanks to all for your replies.  I've been furiously trying to get to the bottom of this with no solution thus far.  To clarify, this is an issue only associated with the PMDG 777 - if I take this addon out of my FSX world, FSX operates magnificently well - no issues even with other complex aircraft such as the PMDG 737.  I have a pretty high-end rig and running very clean so I am confident there is no need at this point to go "Nuclear" with an OS re-install or anything of that nature.

 

At this point I have been unable to launch the aircraft - when I try to launch it the sim hangs until I have to kill it.  Is there a way to set the panel state outside of the simulator, maybe through an .ini file or something?  Since I haven't been successful at getting the aircraft to launch and change the panel configuration through normal means, I don't know if the panel thing is what's causing my issue.  I've changed the default flight as suggested by some but the issue persists.

 

Keep the suggestions coming.  This is a mystery!!!  Thanks!  Dennis

 

 

At this point I have been unable to launch the aircraft - when I try to launch it the sim hangs until I have to kill it. Is there a way to set the panel state outside of the simulator, maybe through an .ini file or something?

 

Hi, Dennis,

 

See the post I just added one minute ago!

 

Mike

Hey Mike!

 

Very interesting.  Two things:

 

1.  Since I re-installed the 777, the only livery I have is the default PMDG 777 livery.

2.  The Options.ini file is pretty much empty.  The only thing in it is the following:

 

[ADIRU]

LastPosValid=0

 

Is this normal?  Should the install have installed other liveries in addition to the PMDG?  I'm starting to wonder if I have a bad .exe, although that does not explain why the 777 was working fine a couple of weeks ago and now is exhibiting these issues.

 

Dennis

Hey Mike!

 

Additional information.  So I went ahead and added the following liveries form the Operations Center:

 

Delta

Emirates

Air Canada

The New American Airlines livery from Avsim

 

Tried them all and the same situation happens with all.  I also tried the freighters - same thing.

 

I have to try the Options.ini recommendation but as I mentioned above, mine is pretty empty!

 

Dennis

 

 

Is this normal? Should the install have installed other liveries in addition to the PMDG? I'm starting to wonder if I have a bad .exe, although that does not explain why the 777 was working fine a couple of weeks ago and now is exhibiting these issues.

 

Hi, Dennis,

 

I don't recall how many liveries are installed from the initial install, but pretty sure it's more than one.

 

My options.ini file has way more stuff in it - many settings for variables like ADIRU time to initialize, autothrottle settings, Vspeed settings, and a whole bunch of other stuff. 

 

Now I am thinking that something went wrong with your original install, but something else went wrong with the reinstall.  Maybe you need to run the installation exe with run as administrator.  Is your FSX installed in the Program Files or Program Files (x86) folder?

 

If you want I can send you my options.ini file, but if it's that empty I think something went wrong with the reinstall.

 

Mike

Hey Mike!

 

I just re-installed as Admin and my Options.ini is still blank.  I think I need to re-download the install.exe.

 

Stand-by  Dennis

 

 

I just re-installed as Admin and my Options.ini is still blank. I think I need to re-download the install.exe.

 

Did you uninstall first?  I think you can through the Windows Control Panel uninstall section.  Any more liveries showing up?

 

M.

Hey Mike!  OK!

 

1.  I de-installed the whole package using Control Panel and rebooted.

2.  Re-downloaded the installer form the PMDG store and re-installed.

3.  Downloaded and installed Delta, Emirates, and Air Canada liveries from the Operations Center.

4.  Launched FSX and selected the Delta livery.  Same problem.  Had to kill the sim as it took 10 minutes to only get to 8% of loading

5.  Checked Options.ini file and it's still empty with only the ADIRU entry.

 

Can you shoot me your Options.ini to see if that works by any chance?

 

Thanks again!  Dennis

x

Dennis -

 

I had this exact same problem.  I submitted a ticket and after going through all of the suggestions made by

PMDG, I wound up doing a complete re-install of FSX.  That fixed the problem and cleaned out a bunch of

old stuff in the sim that I had forgotten about.  I had narrowed the problem down to an apparent .dll conflict

but could not determine which one.

 

If you decide to do an FSX re-install, there is a helpful KB article in the PMDG Support section.  Here's the link:

 

http://support.precisionmanuals.com/KB/a87/how-to-uninstall-and-reinstall-fsx.aspx

 

Good luck!

Wholly Crap!  One of my worst nightmares.  That and a complete OS re-install!!  Yikes.  I've been, however, preparing myself for this psychologically - it may come to going "Nuclear" on FSX and starting over.Tremendous amount of work to get everything back in good working order.  Thanks for sharing Phil!  I'm surprised PMDG hasn't found the culprit .dll conflict.  I may report on this back in a couple of days, once my clean re-install is competed.

 

Cheers.

 

Dennis

To be clear:  I did NOT re-install W7 OS, only FSX (bad enough, I know).  Took about eight (8) manhours total.

Looking back it was worth the time; relocated FSX out of the "Program Files (x86)" as recommended and cleaned

out a bunch of "junk" accumulated over the years in the sim.  Again, Good Luck!

Hello Phil, Mike, and Team!

 

Issue solved.  As Phil mentioned, the FSX re-install is what did the trick.  I took a deep breath and went "Nuclear" on FSX.  Hey at least its a chance to start clean and get this beast flying.  Thanks to all for the input and Mike for all the help.  By the way, my Options.ini is now fully populated.

 

Cheers.  Dennis

 

 

Issue solved. As Phil mentioned, the FSX re-install is what did the trick. I took a deep breath and went "Nuclear" on FSX. Hey at least its a chance to start clean and get this beast flying. Thanks to all for the input and Mike for all the help. By the way, my Options.ini is now fully populated.

 

Very glad it's working now!  I'm curious to know what went wrong in the first place, but sometimes it's better to just get it fixed even if you don't know why it broke.

 

Mike

Dennis-

 

Glad you are working...  If you are reinstalling all of your "Stuff" and it magically reappears- please get back to us with the list of the last few items you installed.

 

More often than not, it is a red herring- but sometimes it does help us find/resolve conflicts/issues.