Bug report - Recurring “Insufficient bandwidth” message (MSFS 2024)
Summary
The message “Insufficient bandwidth, loading times may be longer and the dissemination of data from the world may deteriorate” appears recurrently, in flight and on the ground, despite a hardware configuration and an internet connection well above the needs of the game. The complete diagnosis (below) excludes a hardware or user-side network cause.
Hardware configuration
• CPU: AMD Ryzen 7 7800X3D (8 cores, 4.20 GHz)
• GPU: AMD Radeon RX 7800 XT Sapphire (16 GB VRAM)
• RAM: 32 GB DDR5 Corsair Vengeance (4800 MT/s, 31.1 GB usable)
• Storage: 1 TB Crucial NVMe SSD
• Power supply: Corsair RM850
• Cooling: Corsair Nautilus 360 RS
• Motherboard: ASUS ROG Strix B650-A Gaming WiFi
• Screen: 3840x2160 (4K), without FreeSync/G-Sync
• GPU driver: AMD 26.7.1
Network connection
• Wired Ethernet connection (Intel I225), real line ~2.1 Gbps
• When the message appears: reception measured at only 2.5 Mbits/s in the Windows Task Manager - the connection is largely underutilized, which excludes a local throughput problem.
Detailed observations (via Report-An-Issue / RAI)
Case 1 — On the ground, dense airport (Dublin), complex aircraft (737 MAX 8), advanced custom settings
• Frame time: 33.34 ms (~30 fps), Limited by MainThread
• MainThread: 27.7 ms / Graphics Queue: 22.0 ms
• Render 2258x1270 vs native screen 3840x2160
• GPUMem: 13705/13743 MB (almost saturated)
• Download speed / RollingCache read speed: 0,00 Mbps
• MarkersFailed: 150/621
Case 2 — In flight, alt. 1693 m
• MainThread: 22.6 ms (limiting)
• GPUMem: 11820/13666 MB (unsaturated)
• Download speed: 0.02 Mbps (almost zero)
• MarkersWait: 630, MarkersFailed: 125
• → In flight, VRAM is not involved; data streaming stagnates.
Case 3 - After switching to the “High” graphic preset (instead of Custom)
• MarkersFailed: 150 → 34
• MarkersWait: 630 → 2
• GPUMem: 10764/15409 MB
• → Significant improvement on the ground/cruise flight.
Case 4 — When approaching an airport, “High” preset still active
• The message “Insufficient bandwidth” reappears despite the healthy VRAM and the GPU at 82% / 64°C (normal load, no throttle)
• Actual network reception: 2.5 Mbits/s (Windows Task Manager)
• → Confirms that the message is independent of the user’s graphics settings, VRAM and actual Internet bandwidth.
Conclusion
The diagnosis isolates two distinct problems:
1. VRAM saturation on the ground (complex plane + dense traffic + advanced graphic settings) - mitigated by going back to the “High” preset.
2. “Insufficient bandwidth” at the approach, which persists regardless of settings and local network status - pointing to a bottleneck on the Microsoft/Asobo streaming infrastructure side, especially when loading dense approaching scenery/AFCAD data.
Request
Is there a known ticket for this behavior? Is the problem isolated or shared by other users on large airports?