The time to next waypoint in the navigation display (upper right hand corner) just keeps changing at a really fast rate. It never settles down and just keeps running through the numbers. Any ideas on how to fix this?

 

Chris Herner

Has nobody else experienced this problem? Any ideas?

I too have had this intermittently. I have never been able to track it down to a cause, but I have my suspicion.

 

As a matter of interest, did you change the time on the clock during pre-flight checks? As if I have a culprit in my experience I think it may have been linked with this.

No, I never mess with the clock. It started after installed the Superbug by Vertical Reality, so I removed it but the problem persists.

 

Chris

I've notice that problem when i change the sim time after programming the FMC.

Maybe some other software change your time setting - FSUIPC or FSInn?

I have had this problem and have been told that the FMC is not set up right - I went to DES page FORECAST and set that up with transition, temp, etc and the time stopped jumping.

It may just be "our" computers that do this but the "tweak" may only "work" on my machine.

 

Denis

I think mine occurs like yours Sagi.

 

I guess the issue is that if you set up the FMC and then change the clock after, the FMC has decided the timings for your legs, etc and then the effective change of the sytem clock messes things up with the FMC.

 

I have always finalised the DES page in-flight and about 40nm prior to TOD.

Yes. Looks like the FMC calculate its times only one time, as you execute the FP or something like that. Clock changes after that make its nuts

Anyone work out whats causing this since now for the first time iam getting the same problem as well.when i enter all my info in the fmc, i notice the time switching very fast before starting the engines

 

Edit tried again restart fsx and problem has gone away for good hopefully

Ok i found the cause of my nd time changing rapidly, is that everytime i enter the temp in the fmc in the t/c oat field it starts. if i dont put any temp in the field its ok. Does anyone else have the same cause if you enter the temp in it starts changing?

I don't see what you're seeing, related to your OAT assumption.

 

However, I did have this about a half year ago...

I've noticed Flight Sim has an issue with Daylight Savings time, where the sim actually assumes DST a lot earlier than it actually occurs (in the States at least). Since I use the option where the sim is supposed to match my system time, I have a feeling it's getting lost in the GMT offset between what it's assuming, and what my system says is accurate.

 

My flight the other day had my NGX's clock showing 1930Z (or thereabout), but a T/D time of beyond 0000Z, with only about 160nm to go. This doesn't normally happen, but given that I recall having time issues about a half year ago, I'm assuming this is the issue.

 

I could be wildly wrong, however.

Pete,

 

Yes, I believe Ryan mentioned a bug a while back where if you accidentally put your expected T/C OAT in the T/C ISA DEV field (or vice versa), it will screw times up for the entire flight. This had happened to me at least once and now I double check that I use the correct field. The only solution is a reload of FSX. If you ever get dramatically incorrect ETAs both on the ND and on the PROG page, it is probably due to this. Even if you delete the entries and enter them fresh, the flight is screwed, so to speak. Make sure to enter numbers in the TC OAT -OR- the T/C ISA DEV field that are sensible. For example, really nothing outside of +/- 20 deg C or so in the ISA DEV field and nothing +/- 20 degrees of 56C in the T/C OAT field.

 

I believe also they were having trouble replicating it so I don't know if it will be fixed.

 

EDIT: Minor details...

Pete,

 

Yes, I believe Ryan mentioned a bug a while back where if you accidentally put your expected T/C OAT in the T/C ISA DEV field, it will screw times up for the entire flight. The only solution is a reload of FSX. If you ever get dramatically incorrect ETAs both on the ND and on the PROG page, it is probably due to this. Even if you delete the entries and enter them fresh, the flight is screwed, so to speak. Make sure to enter numbers in the TC OAT -OR- the T/C ISA DEV field that are sensible. For example, really nothing outside of +/- 20 deg C or so in the ISA DEV field and nothing +/- 20 degrees of 56C in the T/C OAT field.

 

Ah thx for the heads up on this

Yeah the bug has to do with putting an out of range temperature (ie, positive 58 instead of negative or something like that) into the T/C OAT or ISA DEV fields. Will be fixed in SP2 most likely.

Thanks Ryan

 

As ever the boys (and girls) at PMDG doing a cracking job of keeping us informed and dealing with these slight anomolies.