Take look at the screenshot which shows a clock time of 2013Z and the PROG Page which shows T/D at 0023Z which is 157 miles away. That is over four hours to travel a 157 miles. It just looks odd. First time I have ever seen this in probably 100 flights or more. Hope I never see it again. Finished the flight to KORD uneventfully.Michael Cubine

I am not sure if this thread will help !I have seen your problem mentioned recently.Maybe a search will find something !http://forum.avsim.n...me-out-of-sync/

JasonThanks for the thread link. I don't consider this to be an important issue since I only use the NGX for U.S.domestic flights. If I had the same issue with the MD-11 on 10-13 hour flights, then it would be a major issue worthy of being solved.Michael Cubine

Michael,Was the Captain's progress page also in error?

Michael,Was the Captain's progress page also in error?

VaughanYes, it had the same info as First Officer's progress page. I checked it about a minute after I took the screenshot.Michael Cubine

Here's another link where I first reported this a couple days after SP1. I noticed it every time I flew up until Daylight Savings ended in the US. I don't know if there's a coincidence there, but either way, PMDG did say they would look into it (reply 25):http://forum.avsim.net/topic/352972-time-prediction-way-off/

Is the problem with all flights and all liveries with SP1 installed?

What was the actual z-time at the time of the screenshot? Maybe the NGX goes straight to the system clock? Just a suggestion.

Is the problem with all flights and all liveries with SP1 installed?

Strangely, I'm not having the issue in any flights since about three weeks ago. But at the time, I only noticed it with the 737-600 (WestJet, PMDG version) and the 737-700 (AirTran, Marcelo's version). Now everything seems fine.

Here's another link where I first reported this a couple days after SP1. I noticed it every time I flew up until Daylight Savings ended in the US. I don't know if there's a coincidence there, but either way, PMDG did say they would look into it (reply 25):http://forum.avsim.n...iction-way-off/

AdamI believe FSX changes from daylight savings time to standard time on either November 1 or the first Sunday in November. The real world change in the U.S. is several weeks later.

Is the problem with all flights and all liveries with SP1 installed?

VaughanIt has only happened once which was yesterday with AAL livery in the 800.

What was the actual z-time at the time of the screenshot? Maybe the NGX goes straight to the system clock? Just a suggestion.

MagnusThe clock had the correct Zula time.One thing interesting thing to note is that the from waypoint on the Progress page had the correct time. It is almost like everyting in the past had the correct time and everything in the future had the incorrect time

What was the actual z-time at the time of the screenshot? Maybe the NGX goes straight to the system clock? Just a suggestion.

I don't believe that is it...In the original post I linked above, I was flying the WestJet flight during the afternoon (US Time) and it was giving ETA's in the 0500Z timeframe while my actual (real world...and system) zulu time was about 1600Z at the beginning and about 2000Z when I landed.

AdamI believe FSX changes from daylight savings time to standard time on either November 1 or the first Sunday in November. The real world change in the U.S. is several weeks later.

I realize that FSX was coded before Bush changed the end date of DST and therefore doesn't change on the correct date. What I do know is that after Sunday, November 13, I stopped seeing the issue. Obviously that's mere coincidence though since you saw this issue today. I can with 100% certainty say that I now double and triple-check the times on the PROG page and I have not had the issue in weeks after having it on two consecutive flights immediately after installing SP1 and the 6700 upgrade. PMDG had supposedly "flagged this issue in the system" and were looking into it. I would say if they found what the issue was, we'll know a bit more when the details of SP1b come out.

I have recently begun having this issue after SP1b. I've noticed that It isn't actually an ETA being calculated but ETE. Take away the z after the time and its enroute time. I have no idea why it started doing this though. Is this an option that is chosen by the operator and in the option files downloaded with liveries?Sheldon Paprota

My time on the NGX FMC is showing ETE instead of ETA. Anyone have a solution? My system time and zulu time in the ngx are right

My time on the NGX FMC is showing ETE instead of ETA. Anyone have a solution? My system time and zulu time in the ngx are right

But did you really need to bump a 3 years old thread ?

 

Update your NGX to SP1c, it'll fix it.

Im current. Version 1.00.3219.

 

 

Warren