only workaround right now seems to be using a weather plugin like rex to inject the weather for that hour unfortunately. hopefully they fix this soon.
Itâs been over 2 months now, so like 20% of a year. How soon is soon I wonder. Sometime in 2023 maybe?
6 Likes
agree and that we have said about many things since release too or from other updates that things got broken in that hasnât been fixed yet either.
I think itâs pretty sad this downtime, which is so absolutely reproducible for just about everyone who uses the sim, has gone this long without being fixed!
23:00-00:12Z is currently 6:00PM-7:12PM in the eastern US, when everyone is just getting home from work, finishing their dinner, and having some free time to fly hopefullyâŠonly to log in and see NO weather at all. Then if I choose to start a flight, Iâll have weather suddenly appear out of nowhere at 7:12 PM exactly.
No matter how much more accurate/not accurate you consider the weather to be post SU7, you canât say this is anything but a failure if we need to deal with an hour+ of downtime every night during prime flying hours for a large portion of the userbase.
They need to get it together. Enough is enough.
4 Likes
Agree itâs now more than 50h down time since su7 hotfix beta started. I think it was back then it started.
1 Like
Nice, Im glad the fix is this simple. Honestly not upset if Asobo just could not figure out this was the issue, but the silence on this issue is disappointing. Iâd rather hear them say we cant figure this out or we dont think this is a big enough issue to pay attention to then nothing at all.
Uh, this is marked as completed?!? Did Asobo fix this or am I now expected to change my clock settings to have the weather working each time I start a flight after 3pm PST?
No, if it was marked completed it would have a different tag. This is still under investigation.
I received a notification states that this is completed.
See the âfeedback-loggedâ tag? It means itâs still under investigation. If it was remediated (i.e., fixed) - it would switch to a Green âFixed on Liveâ usually following the release of a Sim Update.
Itâs been in feedback-logged for a few weeks, so thatâs not what triggered that notification as far as I know.
That is SO EMBARRASING for Asobo that itâs that easy of a workaround and it still has not been fixed for 2 months. Honestly I feel bad for them. Excited to see what they have to say about it in the Q&A.
It was first closed because it was to clean up topics about the issue or something. Maybe a misstake from a moderator? Hope it will be fixed soon though 
To be clear, this thread was never closed and re-opened. In fact, the only moderation history showing is several posts inside this thread were flagged for Code of Conduct violations and handled accordingly. It has remained open since the Topic Author first posted it.
1 Like
Strange. I did see it was closed when i clicked on that notification though. Well, letâs wait for a fix.
If you now look at the tags, it has switched to Bug Logged, meaning Dev Team has placed it in their queue for disposition. Iâm informed by the Community Manager who handles defect reporting that the notification people got is that status being changed on the Dev Team side. It just takes a while to get the tag to show up.
2 Likes
So if I anticipate my flight overlapping 2300z to 0012z, I should set my PC clock to something like 0100z and Iâll be good for the next 22 hours to fly with live weather?
After 23:00z real time if you set your PC time back to say 20:00z you will get live weather. From messing around last night it seems as if once youâre in a flight you can immediately reset your PC to real time and the live weather will persist for that session. I didnât venture out of the local area I started in so itâs possible if moving to a new weather spawn area you might lose the live weather. Youâre probably safe just to set your PC time to 23:00z minus the duration of the flight (and a bit) you intend to make.
Leaving you PC time wrong for too long might have unintended consequences outside MSFS 
1 Like
Asobo just confirmed in the Twitch Q&A that this issue is resolved already ?