Have had no problems with Microsoft Flight Simulator in the past. As soon as the update happened on Monday, I believe that is the correct day. I have no connections to servers, just spins and shows Marketplace offline.
Also have this problem since the live release of the update. Forced to go through the data menu to reactivate, but it doesn’t seem to change much since two minutes later I have a new popup…
I didn’t have the problem in the beta version though.
So this is happening consistently now, I’ve cleaned everything out, deleted the rolling cache, tested my network. Flights also take forever to load now from the planner. Haven’t experienced either before AAU1.
Seeing same thing here since AAU release. Can’t go more than 10 minutes before it give me the error. Reapplying the setting pulls data, then 10 minutes later kills it again. Worse yet I’m on approach now and the ground textures are just green blurs…this sucks.
edit - what’s worse is I just landed on an invisible earth covered in fog. KATL had it’s building - I can see people’s planes parked at the gate. Heck even have my taxiways signs…but there’s no ground textures what so ever…come on.
I’ve had the same problem with Low Bandwidth messages. Two flights in two days had to be done in an offline status. On both occasions I measured my bandwidth speed at just over 270 Mbps. Hopefully this will be corrected soon. It’s no fun looking at offline scenery. It certainly makes one appreciate photogrammetry that much more.
I believe I’ll stop trying to use MSFS for a few hours. I’m getting the low bandwidth warning, no live weather, no clouds, REAL slow flight loading or freezing up, and other issues. (I’m currently on the East NA server and my home connection is operating.)
Also having the low bandwidth issue today. Photogrammetry and bing data won’t load. I think clouds aren’t there either. Have seen this before on occasion, usually due to a network issue on my end that is quickly resolved. Today it is consistent and I can’t find any issues with my connectivity. Must be a server problem.