This issue crept in very slowly for me and is now apparent on every flight! The impact that it has on immersion is such I can’t use the sim in its current state.
Utterly hideous and massively disappointed this hasn’t been addressed in the beta as the devs eluded to in their last brief.
This is not how it works, there Bing transfer data to Microsoft Azure server then to Msfs, if it was easy to found out the root of the issue, would be already fixed, issue can be on Azure side, there variable can do this on several area.
This is a reminder that this thread is meant to serve as a bug topic, not a discussion topic. If you are experiencing this issue, please feel free to report your findings using the above template. In addition, if you find workarounds or processes that helped resolve the bug for you, please feel free to post about it, as it may help the team’s investigation.
Seems to be affecting certain regions e.g. i did a Caribbean flight and its not happening there neither America New York anyway but UK,Europe,North Africa and japan this is happening
Listening to developer stream last week they did touch on this issue and ensure a fix is due along with SU15, however, if this is the case then why are we not seeing it implemented into the beta? Surely they would have done so by now. I’m very sceptical that this can be fixed.
done a flight across the south coast of the USA and issue/Bug still remains seems to be only Caribbean thats not affected and the res of the world is… so can someone tell me if this is a bug or issue caused by the world update?
ive never had this before and since ive updated its started to happen everywhere i go the only place is the caribbean that i dont seem to have this issue and setting the LOD to 400 just makes it happen further away and am unsure if this is the same bug/issue everyone is on about in this topic?
hello all, i am new here i am experiencing this still to this day, i have done a fresh windows install and msfs install onto separate drives, . its making me so angry but glad im not the only one,
It was stated on the dev livestream that this is a code bug and fixed in SU15 but it clearly isn’t in the beta. Maybe it will be fixed with a server side change when SU15 goes GA, but it’s not looking very convincing.