When a new update for the sim comes out, it takes forever for the installer to update the game. the latest VR patch has now been installing for twenty hours and has only worked through eight of the nearly fourteen Gb of data. My internet has an average download speed of 50Mb/s with an upload of 15 so I KNOW it isn’t my internet that’s throttling it, it should have been completed well within an hour.
Either Asobo’s servers are literally on fire and have been for the entire day or there’s something very wrong with the patching software. This happens with every patch, taking an hour or more to sort out only a few hundred mb. At the moment I’ve spent more time patching the game than I have flying and honestly I’m a hair away from giving up altogether.
I feel you. Where are you located? I’m from Europe and already talked about this with my ISP and the answer is simple: the servers of FS2020 are located in LAX, USA only, so the further you are from them, the worse the speed. I get max 10 Mbit/s download speed, but usually 4-8 Mbps :(. Every single update is a pain. And sometimes the game looses all the data just like that, so redownloading the whole thing is a real pain to me. I made backup and it saved my life already twice in 2 months.
The funny thing is that the servers are not Azure, but Amazon AWS! Weird as for MS Studios signed production…
They made it so weird, that it takes no advantage of Windows 10 built in optimized software delivery, which uses other computers to get the software from in parallel to their own servers.
I’m in the UK. I’m really not very far from one of the biggest internet relays in the world so servers in the US should be fine unless they’re really out in the wilds.
We’re routed through the same underwater “pipe” mate. That’s the problem. Another problem is that the game is distributed from 1 central location. No regional servers involved as for e..g Windows updates or Google services…
Still doesn’t make sense though because I can route all of my internet traffic through a VPN physically located in the US and still get 40MB/s download speeds on average, which is all having to be routed through the same physical infrastructure, so it isn’t the general transatlantic distribution.
OK, then it must be either some weird load balancing ruling out some people on god-only-know what criteria or just really low performance servers. The truth is that when an update is issued - people form all around the world start their downloads. If you add just 1 single server to it (1 location) the result is predictable: not enough bandwidth to serve all or just not enough computing power for the server.
Imagine only 100 000 people downloading the updated content with 10 Mbps download speed. This give you 1 000 000 Mbps required bandwidth = 1000 Gbps which is already quite a lot and I bet even more downloads take place when an update is out.
Try running a tracert in command prompt window and see what you get. I’m on the east coast with a 1G line and patches usually take about 20-30 minutes, but even today I see that at times it bounces against the wall during a trace, mainly once it gets to microsoft. My understanding from other posts is this is the IP, I can’t say for certain it is.
Tracing route to 13.107.246.10 over a maximum of 30 hops