Just now, Rockliffe said:

Hmm, I use the slider.... I'll check that one thanks.

 

8 hours ago, pete_auau said:

strange  issue   you have   so  what happens  when  you load  your  aircraft  at  your  home  town,  what  time  is  shown  on the  aircraft clock  to  your  pc  time   you  can  change  the  time  from  utc  to normal  time  the  time  should  match  your  pc  time  if  not  than  that will be  the issue

Not sure Pete, I'll check that out later today and let you know. Cheers.

It’s extremely important to set your Windows time zone correctly. If you are physically located in the US Eastern time zone, (for example), you would need to ensure that your time zone is set to “Eastern”. (GMT -5) By default, on a new Windows installation, (in the US), the time zone is set to “Pacific”. (GMT - 8). I’m not sure what the default time zone setting is for non-US versions of Windows.

You can set your local time and it will appear to be correct, but without the correct time zone setting, Windows itself (and by extension MSFS) will not calculate GMT correctly. For users who do not use GMT in their applications this may be unimportant and not something they would ever notice, but it becomes an issue for apps like MSFS which do use GMT internally.

Windows uses the combination of local time and time zone to calculate GMT. For the US Eastern time zone, GMT is local time + 4 hours (in summer) and + 5 hours in winter. If you were located in the US eastern zone, and had your local time set correctly but were using the default Pacific time zone, any app (like MSFS) which uses GMT would think the current GMT time is 3 hours later than it actually is.

This may not the the cause of the particular problem you are seeing, but it is something you should check.

6 hours ago, JRBarrett said:

It’s extremely important to set your Windows time zone correctly. If you are physically located in the US Eastern time zone, (for example), you would need to ensure that your time zone is set to “Eastern”. (GMT -5) By default, on a new Windows installation, (in the US), the time zone is set to “Pacific”. (GMT - 8). I’m not sure what the default time zone setting is for non-US versions of Windows.

You can set your local time and it will appear to be correct, but without the correct time zone setting, Windows itself (and by extension MSFS) will not calculate GMT correctly. For users who do not use GMT in their applications this may be unimportant and not something they would ever notice, but it becomes an issue for apps like MSFS which do use GMT internally.

Windows uses the combination of local time and time zone to calculate GMT. For the US Eastern time zone, GMT is local time + 4 hours (in summer) and + 5 hours in winter. If you were located in the US eastern zone, and had your local time set correctly but were using the default Pacific time zone, any app (like MSFS) which uses GMT would think the current GMT time is 3 hours later than it actually is.

This may not the the cause of the particular problem you are seeing, but it is something you should check.

Thanks for the suggestion Jim, but my Windows time is set correctly. Set UTC for London...

Edited August 4, 20232 yr by Rockliffe

16 hours ago, Rockliffe said:

 

Not sure Pete, I'll check that out later today and let you know. Cheers.

forgot  to mention this  before  your not  using  panel  save  states  or   could  be  one  of  your  liveries at fault?

7 hours ago, pete_auau said:

forgot  to mention this  before  your not  using  panel  save  states  or   could  be  one  of  your  liveries at fault?

Ahhh, I do use panel saved states Peter. I have one which includes stairs and one when I'm at a jetway... could this be the issue?

18 hours ago, Rockliffe said:

Ahhh, I do use panel saved states Peter. I have one which includes stairs and one when I'm at a jetway... could this be the issue?

could  be one  way  to find  out 🙂

Have the same problem now, i am at hetakion utc +3 in the 738 pmdg.

I can see in the weather menu time is 11h47, but in real it is 12h47. So msfs doesnt take in count correctly the correct local time.

On 8/7/2023 at 7:49 PM, grandfred29 said:

Have the same problem now, i am at hetakion utc +3 in the 738 pmdg.

I can see in the weather menu time is 11h47, but in real it is 12h47. So msfs doesnt take in count correctly the correct local time.

MSFS uses both your local clock time, and your time zone, to calculate what the actual current UTC is. The local time can be correct, but if the time zone is not set correctly, the UTC calculation will be wrong in the sim. If the time is “hours off” everywhere you go in the sim, this is likely the cause.7 Apr 2022

On 8/4/2023 at 11:48 PM, Rockliffe said:

Thanks for the suggestion Jim, but my Windows time is set correctly. Set UTC for London...

MSFS uses both your local clock time, and your time zone, to calculate what the actual current UTC is. The local time can be correct, but if the time zone is not set correctly, the UTC calculation will be wrong in the sim. If the time is “hours off” everywhere you go in the sim, this is likely the cause.7 Apr 2022

I did notice once that Hawaii was an hour off from what it should have been. Like if I set 'live time' at PHNL, at lets say 9AM local according to the sim when it should have been 10PM (or maybe it was the other way around), either way it was an hour off.

Edited August 10, 20232 yr by Tuskin38