There is a fundamental problem with how MSFS behaves when there is a connection issue.
The entire error capture and messaging to the user seems to assume that the Microsoft / Azure / 3rd party servers are 100% reliable, and if / when there is some kind of connection issue, it must be either the user’s own internet connection, or user error, configuration, etc.
There are 2 main problems with this:
- I don’t believe there is sufficient error capture and reporting by the software TO MS / Azure / Asobo when a particular server can’t be reached and causes a negative user experience … if they don’t see it happening with their own data, they certainly won’t pay much attention to subjective individual user posts here
- WHEN there is a problem caused by a server being unreachable, there is not enough nuanced testing / messaging to the user. It just has 1 or 2 generic “your bandwidth is too low” messages, when it should properly say, “sorry one of our servers is unreachable, and this issue has automatically been reported, MSFS will reconnect automatically when it can, in the meantime you can keep flying offline.”
MODERATOR EDIT:
Removed link to vote on a specific wishlist per Code of Conduct.