Microsoft Flight Sim: Best RollingCache Settings in Config

The primary goal for Microsoft Flight Simulator optimization is I/O Latency Reduction and Data Throughput Stability. RollingCache stores streamed data on your drive so it doesn’t have to be downloaded again. This configuration focuses on balancing the Cache Size against your Drive Speed and utilizing the “Manual Cache” for your most-visited hubs like Heathrow or LAX to bypass the dynamic rewrite cycles that cause micro-stutters.

Hardware & System Prerequisites

• Drive Speed (SSD/NVMe): RollingCache is constantly writing and reading small files. An NVMe Gen4 or Gen5 is highly recommended. Using a mechanical HDD for cache will cause severe stuttering.
• Internet Bandwidth: If you have 100 Mbps or higher, a smaller cache is actually better to prevent the game from looking for “outdated” local files.
• VRAM Overhead: High photogrammetry settings require large amounts of VRAM. Ensure your RollingCache is on a separate physical drive from your Windows Page File if possible.

File Location

The main engine configuration file is located in the local app data or the installation root, depending on your version:

MS Store / Game Pass: %LOCALAPPDATA%\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\UserCfg.opt

Steam: %APPDATA%\Microsoft Flight Simulator\UserCfg.opt

Technical Configuration (Code Block)

Open the UserCfg.opt with Notepad. While the RollingCache size is usually managed in-game, these specific engine flags in the config ensure the streaming pipeline is optimized:

# Microsoft Flight Simulator Streaming Optimization 2026
# Source: GameEngineer.net

{PostProcess
	# Sharpens the satellite imagery without artifacts
	Sharpen 1
}

{Graphics
	# Essential for photogrammetry stability
	# 0 = Default, 1 = Prioritize Cache
	CacheCorrectiveMode 1
}

# In-Game Rolling Cache Recommendation:
# [8GB - 16GB] for High-Speed Internet (50Mbps+)
# [32GB - 64GB] for Low-Speed Internet (<20Mbps)
RollingCacheSize 16384

Strategy for Clear-Horizon Performance

To ensure your flight across the globe is as smooth as a real-world autopilot:

• The Cache Size Myth: Bigger is not always better. A massive 100GB RollingCache can become fragmented, leading to longer “search times” for the engine. If you have fast internet, keep it between 8GB and 16GB. This ensures the data is fresh and the drive index remains fast.
• Manual Cache for Hubs: If you frequently fly in a specific area (e.g., Manhattan), use the Manual Cache feature in the settings menu to download that city at “High” detail. This is stored separately from the RollingCache and prevents the engine from streaming that data while you are busy landing.
• Delete and Refresh: After every major “World Update” (UK, USA, Japan, etc.), it is vital to Delete your RollingCache via the in-game data menu. Old cache files can conflict with new terrain data, leading to “floating buildings” or jagged shorelines.

Key Performance Parameters

Parameter	Recommended Value	Impact
RollingCacheSize	16384 (16GB)	Balanced throughput for modern NVMe drives.
Sharpen	1	Restores detail to streamed textures without GPU cost.
Photogrammetry	On	Requires stable cache to prevent “melted building” look.
Manual Cache	Regional	Best for high-traffic flight paths and heavy airports.

Frequently Asked Questions (FAQ)

Conclusion and Expected Results

By manually refining your UserCfg.opt and right-sizing your RollingCache to match your hardware, you are optimizing the world-streaming bridge of the Asobo engine. You can expect the elimination of micro-stutters during takeoff, crisper satellite imagery at high altitudes, and a much more stable photogrammetry experience when flying through dense urban corridors.