It’s absolutely clear that they don’t. How many times are they completely surprised by a question? Prime example recently was the question about low resolution of the snow coverage map. I believe it was in the QA stream before the new year. A series of threads had been going on for literally years. We tried to troubleshoot it ourselves. Try to get them to notice. They were shocked to hear of it first time before the stream when Seb “tried it” and apparently noticed for the first time. It’s still not fixed of course and as we head into the spring time…hey, the problem solved it self …sorry cannot repro. See you again next winter…
Now we have gone half a week without live weather. For many of us it completely ruins the planned flights. Couldn’t fly on the weekend. Came home from work today, can’t fly again.
They don’t have tech support people on call 24/7…for one of the best selling games of all times. A showcase for Azure products. It’s treated like a hobby project where volunteer forum moderates have to be relied on to try and pass something like this on. And of course their absolute terrible communication where even when they start looking into things they can’t be bothered to give us any details. God forbid anybody shows their face they are all hiding behind the forum volunteers.
A proper way to handle this is have it escalated up the chain, provide regular updates, not just once a day if we are lucky, and most importantly of all after it’s been fixed provide a detailed post-mortem of what happened and what steps have been and will be taken to prevent it from happening again. You know, the way any even smallish tech company handles outages.
I doubt any of this will happen. We will get the sticker removed at the top and a 2 sentence apology from Joerg at the next stream in a few month if they even acknowledge it at all.
Like few hours ago I had weather on some 3-rd party aircraft and no weather on the longitude for example, and my thought was to the last update side… but now I do not have weather on any possible aircraft, and now I see that the problem is not on my side cuz I did everything to figure it out.
Anyway, for me the ATIS is Correct with 06 date.
The strange thing is that not everyone have this issue, but enough!
Do you have the same issue if you follow the OP’s steps to reproduce it?
No, I have a different issue with the metar being frozen at 021635
Provide extra information to complete the original description of the issue:
When I load into my home airport at KLNP, there is a heavy fog and the metar reads Feb 2 at 1635z. It has read that for days. I disabled all mods and was able to load in with the current metar. However, loading in a second time with all mods disabled produced the same fog with outdated metar.
If relevant, provide additional screenshots/video:
We are observing the same (non) communication approach that Microsoft applied during previous outages of similar scale. This is not surprising at all for the people how are long enough on these forums.
Seems like the communication policy is - “don’t admit failures, don’t promise resolutions - there is maybe a 1.000 users here on the forum, it’s a fraction (0.05% ?) of all the users, so it’s better to stay silent, possibly the information about the failure won’t spread”.
Legally there is no breach of the license agreement we all accepted when we bought the sim, so they act professionally if we understand professionalism as sticking to the formal agreements.
Hi all, a little update. For days now I have had the problem of live weather like many others, I live in Italy and use TIM as an operator for the fiber in my home. The network is ok, even if these days there have been international problems on the networks, so who knows that there is something to do with these problems, but at the moment we don’t know. In recent days I have done numerous tests and have come to the only conclusion that the weather loads me well and without problems, only if I use the VPN connected to a Japanese server. Try it yourself, I use protonVPN which is totally free. The only problem is that, using the vpn, PSXT+RealTraffic doesn’t work for me.
We have been told Asobo is actively investigating this issue, but no specifics outside of that yet. Just know that while there hasn’t been a resolution yet, they are working on it. It appears to be intermittent across the spectrum of users which always adds a layer of complication while investigating.
So I just tried spawning into about a dozen different US cities and got seemingly correct clouds at about 2/3 of them. Interestingly, spawning into the different airports in the same city sometimes had differing results - clear with fog and old metar at KSEA, rain and clouds at KBFI.
Wishful thinking but I don’t think it’s improved yet. But if it’s a back-end fix we might see it in-game before any forum announcements get written…
For me, as of just a moment ago, Live Weather has partial functionality. See screenshot. For starters, the METAR is four days old. On top of that, the temp indicated on the PFD 18°C higher than what’s being reported (and 9°C above the current actual METAR). It does seem to get the visibility right according to the METAR in use, with reduced visibility in haze.
Does REX at least inject clouds? I have no clouds anywhere as well, METAR stuck from the 2nd FEB, but wind is working correct like everyone else it seems. I will be shelving until this is fixed.
I am currently en route, KBFI → KHWD, with what appears to be live weather, clouds, and snow. Displayed METAR in the weather menu was still several days old, but ATIS weather at KBFI was pretty much bang on what Navigraph METAR gave me. I did have the odd “low bandwidth” error as soon as everything was loaded. I forced data back on in the menu and got the spinning wheel for several minutes, but then everything came back. My gut says server or lingering Azure issues on the MS side.
Edit: I am on East USA servers, on a Comcast 800 Mbps plan, currently showing 40-45ms latency, no VPN.
Edit 2: About halfway between KBFI and KPDX I lost ATC voices, so it’s got to be an Azure problem.
