Since it’s been confirmed that the choice of server ONLY affects multiplayer population and not weather or traffic, it might help people from getting misconceptions by stating this in-sim.
Good idea, but remember to vote for your own wish 
1 Like
Well it would be really stupid to take traffic and weather data for the US from an asian or australian server (and not from the local). Anyway how should that work? Weather and traffic would have to be „transfered“ first from the source server to the asian and austrian server?
That‘s why i think it‘s absolutely clear and understandable for everybody, that server means multiplayer data only.
The weather and traffic models will be global since they are not being sampled in real-time. You don’t get different live weather for a particular location depending on what servers you’re on (well, not on purpose anyway!). I had always assumed that ‘servers’ meant the geographical allocation of Azure resources replicated around the world, and that the primary reason for switching servers is to achieve lowest latency and best performance based on where you are physically located. Latency from Europe to SE Asia, for example, is very high which is why MP performance for the Community Fly-Ins can be patchy for me.
Having multiplayer be local to regions has always seemed odd to me, but I assume that it’s simply impractical to replicate enough data in real time to maintain a single global multiplayer pool. Each individual player would only see a local ‘bubble’ of nearby players in any case. But it seems odd that someone connected to North Europe but flying in Australia can’t see players connected to South East Asia and also flying in Australia, and I would have thought that would be a desirable thing if practical.
1 Like
A quick look at the recent thread about weather difficulties and it’s obvious that misconceptions about what the server does are widespread.
2 Likes
That’s one of the reasons. Almost every, if not all, multiplayer servers are divided like this. Some may just have two, some many. User load and latency.
