So far it appears the Fritzbox DNS configuration using CloudFlare DNS fixed my problems. Interesting…
1 Like
Have you tried the workarounds suggested in this thread:
Works for me.
What vpn do you use? and which server location?
Yes, I tried that, but I wasn’t even allowed to save them in my router settings because I was asked to provide a password which I didn’t have. I described that already in a post above.
sorry I must have skipped that by accident.
Strange. So your router then has different passwords for access and for making changes to the settings? Was the router provided as a rental by the ISP or is it yours? There could be a way to get that password either by the ISP or the manufacturer.
The router is mine, but was provided to me by the ISP, it is a rather old Speedport model of Telekom. I really don’t know what it is about those passwords. To me, it looked like they needed the password for the DNS provider, in this case Cloudflare. I used my router password (which usually works in order to access the router and make changes to its settings), but that one was rejected for making the DNS change.
I try not to occupy myself too much with it, because the changed Windows ethernet settings somehow do work for me now, at least whenever I used MSFS 2024 during the past few days. But it is sad that Telekom does not seem too interested in solving the general problem.
I only hope that Microsoft and Asobo become aware of the problem and get in touch with Telekom in order to think about a common solution. Does anyone have an idea how we can turn their attention to this thread?
2 Likes
You can get their attention mainly by voting for it - if enough people vote for it, they will take notice, hopefully.
The Autor of this topic did try to get this into the Bug Reporting Hub. But it was moved back from the Admin. you will find this higher up in this topic.
Mainly as I understood, in the view of MS this is a ISP issue and they are not responsible/cannot do anything about this.
in this part of the forum you cannot vote for it.
4 Likes
You are right. I came from another thread, where the same topic is discussed:
There you can vote.
1 Like
Of course they could something about it, e.g. by making some for their servers directly available in the Telekom network.
With this kind of attitude, they could just put their servers in Seattle only, and if someone from Europe or Asia has a problem with that, it’s an ISP problem.
2 Likes
Tried it to no effect. No change. Problem persists.
I would like to know how many of the people that responded at first positively still think that it wasn’t just a timely coincidence. Is the problem still solved for them?
For me it still works fine. Not a single ‘bandwidth low’ message ever since I made the settings.
@GeorgeCurious1: Let’s double check: what exactly are your current settings now?
(on XBOX / PC / router)
I can confirm it is still solved for me, having flown almost every day since changing to cloudflare DNS. Mostly in “rush hour” so I’m pretty sure the problem is not server capacity on the far end, at least for the content I’m streaming.
1 Like
Could you please share the settings you adjusted? It would be incredibly helpful if you could outline the steps or changes that worked for you.
Thanks in advance for your help!
I assume you were asking me. The best description is in Post #100 by Wilbur: Low Bandwidth issues with Telekom - Germany only! - #100 by Wilbur3203
So far, I have experienced no downsides from this change, neither in MSFS2024 nor in other applications, such as DCS for example (which is rather picky with connections in multiplayer for me).
2 Likes
I’ll try to share MY experiences here as shortly as possible:
Technical status:
I am also with Telekom and use a business connection with a maximum of 300Mb, we have a standard 2-wire copper connection and the distance to the fibre optic network is 149m. There are no problems whatsoever with Internet use, neither in the business nor private area. So the line was and is very trouble-free, we have maximum data transfers to Frankfurt and Berlin and ping times of around 17ms. The ping times to the Fs2024 server Europa-West are usually around 50ms. On non-working days, they can sometimes be over 60ms.
The computer used is high-end, therefore rtx 4090 with corresponding board CPU and 64GB RAM and is also used for graphic tasks of my Company. The LAN is designed in 5Gb and should therefore not cause any problems.
Using the MS-Store Version.
Here mentioned disturbances:
I do not consider changes to DNS servers, VPN connections or accusations by Telekom that these would slow things down to be relevant. It must be taken into account that disruptions of this kind would affect the entire Internet traffic. But it definitely only affects the FS2024. Telekom is not interestet to slow down FS2024 or Microsoft Products.
Behaviour after a new installation:
If the 2024 is installed, it is noticeable at startup that the peak values when loading are only in the kb or single-digit mb range.
The Communty folder is empty, btw. which does not matter.
Starting in free flight and zooming in to a specific location results in a blurred image and it sometimes takes over 5-10 minutes until the image looks reasonably sharp. In addition, the low bandwidth status message appears, which can have an effect on the displayed landscape. If you wait patiently before flying, the view is more or less catastrophic. Blurred landscape and clouds like in Ninto64 times. This situation is sometimes better and sometimes worse, but never really usable. Loading the landscape is rarely accompanied by values above 2-3mb and is usually in the kb range.
This situation is absolutely reproducible and occurs with every new installation.
I have to say that I was pretty fed up with the situation and temporarily uninstalled 2024 to avoid wasting time on it.
Nevertheless, I have now looked into the issue again because I remembered the initial problems in 2020 that occurred with the rolling cache.
The miracle happens 
I have now increased the rolling cache to 32GB, which did not result in any noticeable change. However, a value of 64GB allowed an improvement at startup and zooming in to a location was much faster. Download peaks of up to 80mb occurred. However, the effect was only of limited duration. After I had randomly travelled to very distant places on the globe, everything was back to ‘normal’. Unfortunately, you can’t reset the chache. It is also not possible to reduce the size. Moving it to another location doesn’t help either. So I deleted the cache manually, which caused huge problems at the next start and the start time was extremely prolonged.
It seems to me that the rolling cache is not only used in 2024 for the landscape when flying, but also for programme content when starting or operating the software.
I then managed to restore the basic settings by reinstalling, which created the cache at the original location with 16GB. The speed problems can then be reproduced. I have tested this several times.
I then increased the cache to the current 164GB. Every time I do this, it has an immediate effect on the download speed.
I have spikes that go over 200mb both when starting the 2024 and when zooming in to a location. Even if there are situations where it takes longer, if there is no peak over 20mb when starting the FS or zooming in, I can say with certainty that something is wrong.
Please note: related to my internet connection.
With every new installation and increase in cache size, the speed peaks immediately became noticeably higher. This resulted in high values of over 70-100mb even for longer periods of time. This means that the bandwidth problem message no longer appears.
Final result:
The connection between the rolling cache and the download speed is 100% clear and reproducible for me. This was the result of repeating the tests after a new installation and increasing the cache size. I now achieve loading speeds between 100-200mb. This results in a completely different gaming flow.
With the new size of 164 GB, the situation has not worsened again so far.
If this happens again, I’ll have to see how to fix the problem without reinstalling. I can also add a hard drive to the system and set the cache to 1TB, but that doesn’t really solve the problem.
Basically, a cache reset option would definitely be useful. This could also happen automatically.
I had already noticed that an error log was automatically issued because the 2024 took an unusually long time to start. Therefore, monitoring the loading times is certainly a good way to influence the cache.
I am pleased that I have now found a solution to this major problem and hope that the developers will improve it and could help others in the same situation.
The rolling cache will certainly be used to a greater extent in 2024 than in the 2020 version, which may be why there are still problems.
I wish everyone a merry and peaceful Christmas who is celebrating the holiday.
Addendum:
I recently created space by uninstalling the Fs2020 and increased the cache to 500GB. The cache was set up with 250GB on a laptop. Both systems have been running since then without any problems.
2 Likes
Ohh man! Thank you! I can gladely confirm that Telekom with Speedport 4 and these settings works as a charm! Played 6 hours without any bandwidth issues anymore! Perfect! Before that it was 9/10 times with low bandwidth. Now I can enjoy the game. Thanks!!!
2 Likes
what settings you mean?
1 Like
Changed this a week ago - works like a charm since then. Loading times are consistently good and not a single issue loading into a flight to spawn or a low bandwidth warning.