Mike, the first 2 dates are the same, while the one of PMDG_777X_3.dll is 12/14/13, that is more recent than yours. Could this be the problem?

 

I suppose it's possible, but probably just an anomaly since your first install was w/ a version of SP1 and mine goes back to the original RTM.  But it wouldn't hurt to ask PMDG. 

 

FWIW, in "properties" my ...3.dll file has 532,480 bytes.

 

Did you ever run "repair"?  Sorry if you mentioned this earlier.

 

Mike

 

 

I am in cruise at say FL 360 and start the VNAV descent (early, before T/D, but ATC instructed me to descend) to say FL 200. One of the waypoints ahead has an altitude restriction, say /240A (FL 240 at or above). The airplane seems to be willing to reach that altitude immediately and starts an incredible dive up to 10000 ft/min, it goes into overspeed and there appears "VNAV PTH" crossed by a yellow bar on the PFD flight mode annunciator. I tried it several times and it always happens. I don't think this is normal... I have SP1c.

 

Hi, James,

 

Did you ever get this issue resolved?

 

Mike

Hi Mike, unfortunately I did not, I tried the situation with the computer at work and it's the same. It seems to me that, when the mode changes from THR/LNAV/VNAV SPD to HOLD/LNAV/VNAV SPD, since the speed is below the target speed (you can see that in my video at about 1:30), the airplane, by means of VNAV SPD, lowers the nose in order to reach the speed. It does that too aggressively, with that absurd -10000 fpm, so that the speed is reached and exceeded into a large overspeed, from which it takes a while to recover.  If you contrast the pitch down by quickly adding the right amount of thrust manually (you are in HOLD mode), you can some way anticipate the airplane's will to reach the target speed by means of pitch-down, and the sink rate doesn't reach those high values. I don't really think that's the way you would act in real life, though....

James,

 

Have you submitted a trouble ticket to  PMDG?

 

Every time I have PMDG has been quick to respond and worked diligently with me to get my issues resolved.

 

Billy Bluestar

I thought we had it traced to bad panel states.  You cannot reproduce this if you start with a default flight instead of loading a flight.

I thought we had it traced to bad panel states.  You cannot reproduce this if you start with a default flight instead of loading a flight.

 

Dan, I thought that, too, but the other day I did a complete flight by starting FSX with the Trike shown on the aircraft window, then  selecting the 777 and the airport, then the panel state "777 SHORT" and from there did everything according to the standard procedures. When I was in cruise, some 30-40 Nm from T/D, I started an early descent in VNAV and I had that problem again. That was the reason why I started this thread on Jan 5...

Must be a corrupt install.

 

I mean with the FSUIPC.ini deleted and rebuild, no self saved panel state used, no saved flight used.....what else could it be?

 

The only other thing I can think of is to check that you have "FSX/settings/customise/weather/do not use turbulence effects on airplane" selected.

And test without any external weather program....just default FSX weather!

 

I have been experimenting a bit what that and there are conditions where those effects, when selected on, can cause strange behaviour. (as confirmed by the PMDG intro guide)

 

 

Dan, I thought that, too, but the other day I did a complete flight by starting FSX with the Trike shown on the aircraft window, then selecting the 777 and the airport, then the panel state "777 SHORT"

 

One more shot at a possible panel state issue:  what panel state loaded before you selected the "777 short" state?  In other words, what is the default panel state that loads when you start a new flight?

 

Also, are you using the same flight plan or did you enter it from scratch?

 

Mike

what panel state loaded before you selected the "777 short" state?

 

It's the "no name" state, I suppose it's the default one. In the CDU initial state line I have dashes  (------)

 

 

Also, are you using the same flight plan or did you enter it from scratch?

 

It was another flight, different airports, different flight plan, entered from scratch.

 

 

It's the "no name" state, I suppose it's the default one. In the CDU initial state line I have dashes (------)

 

That would have been my preference to eliminate possible problem sources -- engines on, everything ready to go. Same for a fresh flight plan. -- so I really don't know where the problem is coming from.   Your best bet is to file a support ticket w/ PMDG.

 

Mike