The timezone boundaries are wrong in most areas of the world. They seem to be right in Europe and North America only. For example, landed in Hoton, China, where the time should be UTC+8 as it is in all China mainland. Instead the sim has it as UTC+6! It would seem that this issue is important to the realism in the sim. Rather than updates concentrating on scenery items, perhaps more emphasis on improving the realism as was originally promised.
TZs have always been a mess in sims because governments are always messing around with time zones and DST. We have had third party apps that update changes and fix time zones.
Not sure how the timezone data works in MSFS. Maybe someone like Navigraph could provide a solution.
Are you using Developer Mode or made changes in it?
No
Have you disabled/removed all your mods and addons? If the issue still occurs with no mods and add-ons, please continue to report your issue. If not, please move this post to the Community Support section.
No
Brief description of the issue:
When flying in Launceston, Australia, the calculation of local time vs UTC time is incorrect.
The UTC time is 00:18, and the corresponding local time should be 11:18. Instead it is 09:18. A 2 hour difference!
Provide Screenshot(s)/video(s) of the issue encountered:
I thought of posting this here because I wanted to see this corrected for MSFS 2024.
Some regions in the sim have time zones that do not match with their real life counterparts. These are some of the regions I found in sim that do not match up with real life (either incorrect time zone, or incorrect DST dates) from west to east. DST Dates are taken into account in this list.
Not really true. India uses a half hour time zone (+5.5), and so does Australiaâs Northern Territory and South Australia (which are both +9.5, with South Australia at +10.5 in DST). Those are correct in sim. Additionally, it doesnât make sense for Arizona to observe DST when Saskatchewan doesnât in sim.
Those other two on the other hand (Madeira and Arizona) are incorrect. They show -2 and -6 respectively when Madeira should be the same as mainland Portugal at 0 or +1 if DST, and Arizona doesnât observe DST at all, thus should be -7 all year round.
Parts of Tasmania Australia are incorrect, whole island should be AEST which is UTC +10. Currently in MSFS the east half of the island is correct, but the north and west is UTC +8.5
Thanks for telling me about Tasmania. When I looked at my sim, the entire island is +9 rather than +8.5 for the north and the west of the island. Either way, I added Tasmania to the list above.
BTW, I looked at the Canaries again. Itâs directly south of Madeira and share the same time zone in real life. Surprisingly, they have the correct time zone of +1 (in DST). So the Canaries get to have the right time zone but Madeira and Porto Santo are off by two or three hours in sim compared to the real world.
Do you have the same issue if you follow the OPâs steps to reproduce it?
Yes
Provide extra information to complete the original description of the issue:
check time zone in Armenia and then Greece. I did a flight from Yerevan to Athens - departed UDYZ on 00:20 UTC and reached TOD near LGAV at 23:57 UTC. Time zones are messed up!
If relevant, provide additional screenshots/video:
Hey Folks, after discussion by the MSFS Forum Team a Wishlist topic about the same issue was merged into this Bug Report.
Several off-topic posts have been deleted to tidy up this Bug Report, if you would like to contribute please click the button below and fill out the template.
Cheers
For anyone who wants to contribute on this issue, Click on the button below to use this template:
Do you have the same issue by following the OPâs repro steps?
Provide extra information to complete the original description of the issue:
This is still an issue as far as I can see. I live in Arizona and frequently fly out of KPHX. UTC shows correctly, however, local time shows as -6 when we are -7 and never change as we do not participate in DST.
Is there any plan to address this? Rest assured that I will not be purchasing 24 if this will be a continued programming issue.