Time issue...

[MM7 42]

Please will someone help me with this error....http://img205.imageshack.us/img205/8800/71222165.png

[AirbusCG 52]

There is no error. You've got your time set to local. Depending on the location you fly at this can be a big difference from the UTC time which is shown in the ND.Hit the Time/Year Key on the clock twice and then it'll change to UTC. Then the times will fit again.

[MM7 42]

I was at London Heathrow, their UTC and Local time are the same which was the 15:34 cause I took off in South Africa local time at 17:45....

[scandinavian13 5,192]

There's a UTC/Zulu time error in FS. Google it and you'll find the fix.

[willywonka 36]

Weird. Your clock shows "MAN" which is displaying local time. The ND always show UTC time. If you press the TIME/DATE button on the clock twice to get UTC, does it still say 15:34?

[skysurfer 76]

There's a UTC/Zulu time error in FS. Google it and you'll find the fix.

HiCan you send me the link for that fix? I cannot figure out.Thanks.

[kevinh 409]

From what I can work out, FSX takes your PC's local time as it's local time at start up. If your default flight is not in your local time zone (and it won't be if you use the FSX default flight and don't live in Alaska ) this means that local time and UTC won't match up properly. The fix that works for me is to create my own default flight based in my time zone. Obviously FSX time can still drift, and it will also be affected if you pause FSX, or you use time acceleration. The OP's problem appears to be compounded by setting the clock manually to agree with actual GMT. The FMC will be working off what FSX thinks UTC/GMT is.Hope this helpsKevin Hall

[MM7 42]

Weird. Your clock shows "MAN" which is displaying local time. The ND always show UTC time. If you press the TIME/DATE button on the clock twice to get UTC, does it still say 15:34?

It is UTC on the clock cause I was in Heathrow...

From what I can work out, FSX takes your PC's local time as it's local time at start up. If your default flight is not in your local time zone (and it won't be if you use the FSX default flight and don't live in Alaska ) this means that local time and UTC won't match up properly. The fix that works for me is to create my own default flight based in my time zone. Obviously FSX time can still drift, and it will also be affected if you pause FSX, or you use time acceleration. The OP's problem appears to be compounded by setting the clock manually to agree with actual GMT. The FMC will be working off what FSX thinks UTC/GMT is.Hope this helpsKevin Hall

You lost me :(

[kevinh 409]

It is UTC on the clock cause I was in Heathrow...You lost me

I may have lost myself. What I meant was that setting GMT manually on the NGX clock won't change the times in the FMC, which will still be FSX zulu. It's still a local time setting even if it is the same as GMT. But I can only assume this because the only info you provided was a screenshot. A description of what you did would help.The gist of the rest of my post was make sure your FSX default flight starts at an airfield in your local time zone (i.e. same time zone as your PC clock) and local and GMT will work fine in FSX.Kevin Hall

[MM7 42]

Well, I set my plane at Heathrow, set it to Local Time (which is EGLL time), then the UTC was also the same but my plane showed 1023z when the ACTUAL ZULU time was 1330z....

[JRBarrett 3,195]

Well, I set my plane at Heathrow, set it to Local Time (which is EGLL time), then the UTC was also the same but my plane showed 1023z when the ACTUAL ZULU time was 1330z....

Did you set the FSX local time to 1330 using the FSX time/date menu after moving the aircraft to Heathrow? If so, I agree that the ND's displayed UTC time is wrong.In any case, putting the NGX clock into MAN mode does not automatically switch the clock to whatever local time zone the aircraft happens to be located in at the moment. It simply means that you are in a mode where you can manually set the clock to read whatever time you want. In your screen shot, not only is the hour wrong compared to UTC (15 vs. 10) but the minutes are off too (35 vs. 21).If you take the NGX clock out of MAN mode, it should automaticaly sync to whatever UTC time exists within FSX's own UTC time/date setting for the physical location on earth where your aircraft is positioned. In the real NG, the clock gets its UTC time from the GPS receiver. (Assuming that the GPS is fully initiallized and receiving valid data from the satellites.

[MM7 42]

Well, I started my FSX, went to EGLL and the times didn't sync...never did this before SP1..

[wildtrout1 0]

Sorry to be completeley off subject, MMC, how did you change the Front Panel ID plate to "G-VABA"?

[Niall Hanley 0]

Off topic, but isn't there something with the clock in airbuses when if you mess with them, the flaps jam? I remember seeing a sticker when I jumpseated in the A330 that said "NO MESSING WITH THE CLOCK". Just out of interest.

[adamant365 28]

The gist of the rest of my post was make sure your FSX default flight starts at an airfield in your local time zone (i.e. same time zone as your PC clock) and local and GMT will work fine in FSX.Kevin Hall

On this subject, I'm located in the eastern US time zone. I have my default flight set to KLEX. Before we went from daylight savings to standard time, the UTC/local time was always correct in FSX. Now that we're on standard time, my UTC offset in FSX is still -4 which is not correct. It should be -5. Strangely enough, sunrise/sunset times are correct in FSX if I strictly use Zulu when setting up my flights even though by local time, the sun sets an hour late. Any clue on how to fix this??