This started happening before the SU5 update. Leads me to believe it’s something to do with the servers providing the live weather.
@Jummivana The problem is not, and never has been a problem in SU5 itself. The extreme high temperatures aloft started happening 6 days before SU5 was released. It was affecting ->SU4<-
This clearly and unambiguously shows that the high temperature problem is being caused by an error in the Live Weather server itself. Either MeteoBlue is exporting corrupt temperature data (highly unlikely), or the MeteoBlue model data is being corrupted in the process of importing/parsing it into the Azure servers for streaming to end-users.
Yes! I wonder if the issue is the provider, that happened for me first a week before SU5
Can keep us updated on what they say please Jayne? cheers
Yep, still broken. Cruising at 26,000 and temperature is 31C.
Hello, i was flying at FL380 and the temperature increase over to +50°C after today’s hotfix. I thought this was fixed today.
And when i opened the xbox menu to take the screenshot the game crashed.
Samething happening here too.
Time to change the Hotfix release notes
currently flying at FL250 with 27C OAT
And I too was seeing this well before SU5
+1 Yep temps are still bugged.
I wonder who is at fault, asobo or meteoblue, because, the problem started happening BEFORE update (Before SU5)
Meteoblue is absolutely fine
But them, how it broke without any update from asobo?
Great. Now they’re just lying about bug fixes that didn’t happen. Has anyone from asobo ever heard of a word called “testing”?
I don’t think the weather model that MeteoBlue provides for MSFS is used directly. I’m pretty sure that the model data has to be parsed/converted/processed into a form that can be used in the sim itself, and that processing is probably done at the Azure end.
I don’t know this is how it works, but it is logical, as MeteoBlue is in the weather business, not the flight simulator business, and their NEMS30 global weather model is used by many other clients besides Microsoft.
Please, don’t do that. We’re all frustrated. But don’t characterize them like that.
I wonder what is causing this bug. Does anyone have any hypotheses’?
There has been many an occurrence of a fix working in test but not in production. It happens literally all of the time. Don’t accuse them of lying without sufficient evidence to back it up.