NGX FMS TIME

[scullymec 0]

HI Fellow Simmers

 

I was wondering if anyone had encountered the problem of the fms eta times being out of sync with everything...sometimes its only out by 10 or 12 hrs more times it just keeps flicking times at random but always reads the correct time for last w/point passed..the clockin the plane always reads the correct time and the sim is set to real time, I also run Aiviasoft efb ( a wonderfull bit of kit and in my humble opinion a must have) and its correct with its eta's.....I'm running fsx with Xpack and think I read somewhere that it can be a bit quirky..but not too sure about this..any ideas much appriciated Many Thanks Fred TROUBLE FREE FLIGHT TO ALL

[wisefox7524 9]

It's a known problem, many people have had it in the past. I know a lot of tickets have been submitted about it, and I don't think PMDG has yet figured out what causes it. It's not a problem most of the time - I have only experienced a couple times, with almost 200 hours in the plane. The best is to hope they figure it out, and fix it.

[adamant365 28]

I had this issue once or twice pre-SP1b I think. It was very hit and miss...sometimes my ETA's would be way off, sometimes (mostly) they were spot on. Since SP1b, I haven't had any issue though. Have a read through this topic I started a while back and see if this fits the description of what you are experiencing:

 

http://forum.avsim.net/topic/352972-time-prediction-way-off/

 

Like I said though, I haven't had this happen in a while. Are you certainly fully up to date with the Service Packs?

[Jettix 1]

HI Fellow Simmers

 

I was wondering if anyone had encountered the problem of the fms eta times being out of sync with everything...sometimes its only out by 10 or 12 hrs more times it just keeps flicking times at random but always reads the correct time for last w/point passed..the clockin the plane always reads the correct time and the sim is set to real time, I also run Aiviasoft efb ( a wonderfull bit of kit and in my humble opinion a must have) and its correct with its eta's.....I'm running fsx with Xpack and think I read somewhere that it can be a bit quirky..but not too sure about this..any ideas much appriciated Many Thanks Fred TROUBLE FREE FLIGHT TO ALL

 

When you get sync times error, you can fix it for this flight such way: enter CDU and navigate to Nearest Arprts page (Int/ref index - altn dest - Nearest Arprts), inspect any of it and go back. ETA times will be corrected.

I Have not had this error after sp1c and have never had flickering of indication at all.

[ZKOKQ 984]

Read page 136 of Tutorial #2 and explains how to input winds aloft and temp. if you don't do this correctly, your DTG will be inaccurate.

[Tabs 2,790]

The problem is definitely related to inputting some sort of out of range temp/ISA deviation on the PERF INIT page - (ie +60 instead of -60). Problem is we can't replicate it in debug mode, it only happens with the release gauges... very hard to know what's wrong when that happens. If you avoid entering a wildly out of range temperature it shouldn't happen though. If you do though you have to reset the sim to fix it - the problem sticks even if you change the temp to a correct one.

[adamant365 28]

The problem is definitely related to inputting some sort of out of range temp/ISA deviation on the PERF INIT page - (ie +60 instead of -60). Problem is we can't replicate it in debug mode, it only happens with the release gauges... very hard to know what's wrong when that happens. If you avoid entering a wildly out of range temperature it shouldn't happen though. If you do though you have to reset the sim to fix it - the problem sticks even if you change the temp to a correct one.

 

This is actually very helpful info. After saying I hadn't had this issue since SP1c, I saw it again yesterday on a flight (WS108, CYEG - CYZF). The time just before T/D was 1848z, but the FMC was reporting my arrival at 0453z...obviously I wasn't going to need over 10 hours to descend.

 

I do clearly remember accidently entering my ISA deviation (+6 C) in the T/C OAT field, thus making the ISA DEV +62C. I quickly corrected it, but what Ryan says here must be the reason. I'll just have to remember to be extra careful and not enter the ISA DEV in the T/C OAT field in the future.