Minecraft: Best options.txt for Distant Horizons Mod

The objective is to maximize your Vanilla Simulation Distance ($D_{sim}$) while offloading the visual horizon to the DH engine, preventing the CPU from choking on full-detail chunk data.

Initial RAM Allocation (Launch Options)

Before editing options.txt, ensure your JVM arguments are optimized. Distant Horizons caches thousands of LODs in memory ($M_{lod}$).

• Recommended RAM: -Xmx8G to -Xmx12G (Allocation depends on your LOD radius).
• Garbage Collector: Use -XX:+UseG1GC or -XX:+UseZGC for smoother frame delivery in 2026.

Optimized “Infinite Render” options.txt Table

While many settings are now in-game, these options.txt flags act as the foundation for DH’s stability.

Parameter	Recommended Value	Technical Purpose
renderDistance	12 to 16	The Master Cap. Keeps the “Real” detail close to the player.
simulationDistance	8 to 10	Lowers CPU load for mob AI and redstone at long ranges.
graphicsMode	2 (Fabulous!)	Required for proper transparency sorting with LOD water.
enableVsync	false	Prevents input lag when the CPU is busy generating LODs.
maxFps	144 (or Monitor Hz)	Caps the engine to save CPU cycles for chunk generation.
clouds	false	Recommended to use DH’s internal cloud rendering instead.

HowTo: Engineering the DH Visual Pipeline

Follow these GameEngineer.net technical steps to bridge the gap between vanilla and LODs:

1. The “16-Chunk Rule”: Never set your vanilla renderDistance in options.txt above 16 when using DH. Doing so forces the CPU to generate full-detail chunks ($C_{full}$) that you won’t even notice, stealing resources from the LOD generator.
2. The CPU Load Protocol: Inside the DH in-game config, set CPU Load to “I Paid for the Whole CPU” during the initial world generation to fill the cache faster. Once the world is “baked,” switch it back to “Balanced” to reclaim FPS.
3. Horizontal Quality Adjustment: In the DH config, set Horizontal Resolution to “2 Blocks per Pixel.” This provides a sharp horizon at 1080p/1440p without the $4\times$ performance hit of “1 Block per Pixel” settings ($Q_{horiz}$).
4. Shader Synchronization: If using Iris/Sodium, you must use “DH-Compatible” shaders (like Bliss or Distant Horizons-specific versions). Ensure options.txt has entityShadows:true to avoid visual “ghosting” on the simplified terrain.
5. Data Compression ($D_{comp}$): If your DistantHorizons.sqlite file (the LOD database) is growing too large (40GB+), enable Lossy Compression in the DH settings. This slightly reduces distant color accuracy but slashes storage requirements by up to $60\%$.

Technical Explanation: LOD Radius and Vertex Buffers ($V_{buf}$)

Distant Horizons works by creating a “Shell” of the world. As you move, the mod swaps high-poly vanilla chunks for low-poly LODs.

$$Total\_Polygons = (Chunks_{vanilla} \times P_{high}) + (Chunks_{DH} \times P_{low})$$

By engineering your options.txt to a low renderDistance, you keep the $P_{high}$ count low. This leaves a massive “Vertex Budget” ($V_{buf}$) for the $P_{low}$ distant chunks, allowing you to see 10 miles away at 144 FPS. If you experience “holes” in the world, it means your CPU generation speed ($G_{rate}$) is slower than your movement speed; in this case, lower the LOD detail in the DH config rather than the vanilla settings.