Distant Horizons: LOD Setup, Loaders, and Shader Limits

Current release check: Distant Horizons 3.2.0-b-26.2 is a beta for Minecraft Java 26.2. The creator publishes one Fabric/NeoForge JAR for this tuple. MineBrush checked the creator-controlled project and release metadata on August 24, 2026, but did not download or run the file. No FPS, memory, shader, server, persistence, or rollback result is claimed.

Distant Horizons adds a level-of-detail (LOD) layer for simplified terrain beyond Minecraft’s normal render distance. It can make faraway land visible, but it does not make one file compatible with every game version, loader, shader, server, or graphics setup.

Choose one exact game and loader tuple

The selected version ID is gBf0SaV1. Its primary file is DistantHorizons-3.2.0-b-26.2-fabric-neoforge.jar, listed at 29,705,395 bytes. Those are creator-published metadata values, not a MineBrush artifact inspection.

The creator’s loader note says Minecraft 1.20.6 and newer use combined Fabric/NeoForge files, while 1.20.4 and older use combined Fabric/Forge files. These are separate release families. Do not install the current 26.2 file in 1.21.11, and do not treat an older Forge label as current NeoForge support.

Know which layer you are tuning

Minecraft still renders nearby normal chunks. Distant Horizons builds and displays a simplified distant representation beyond that area. Changing vanilla render distance, Distant Horizons distance, LOD quality, generation, and shader settings affects different parts of the scene.

Start low enough that you can recognize each change. A huge distance number is not automatically a better setup: terrain quality, build time, processor load, graphics memory, storage, and visual seams can all become the limiting factor. The project markets a low-cost long-distance view, but MineBrush has no controlled benchmark for your hardware.

Client-only and server-assisted play are different

The project marks both client and server installation as optional. The creator says a client-only installation can save LODs between sessions as you explore. In the client-plus-server mode, a server running Distant Horizons can send LOD data to connected users who also run the mod when distant generation is enabled on the server.

A client-only result does not prove server delivery. A server component does not replace the compatible client mod. Proxies, plugins, permissions, bandwidth, world-generation mods, and hosting limits remain separate variables that were not tested here.

Check the 26.2 beta’s graphics boundaries

The 3.2.0-b release notes raise the minimum OpenGL version from 3.2 to 3.3. They also add LOD textures for the base Distant Horizons renderer, while stating that Iris shaders render those LODs untextured in this release. The notes say the Auto rendering engine no longer crashes merely because Iris is present, but explicitly selecting Blaze3D can still crash because Iris does not support that path.

Those statements belong only to the checked 26.2 beta. They are not a blanket promise for every Iris version, shader pack, graphics API, or older Distant Horizons release. If shaders matter, record the exact Iris release, shader pack and preset, Distant Horizons rendering engine, GPU, driver, and world scene.

Install in a disposable profile first

1. Confirm the launcher profile is Minecraft Java 26.2.
2. Confirm the profile uses Fabric or NeoForge. Do not place the same JAR in a Forge profile.
3. Open the creator’s versions page and select version ID gBf0SaV1.
4. Place the JAR in that profile’s mods folder and start with shaders and unrelated renderer mods disabled.
5. Use a disposable profile or copied world. Reach a familiar location before raising LOD distance or CPU load.
6. Change one Distant Horizons setting at a time and keep the last-known-good profile configuration.

For a general Fabric installation route, use the MineBrush Fabric mods guide. This page owns the Distant Horizons release, LOD, side, and shader boundaries.

Run a small acceptance route

1. Launch the profile and confirm it reaches the menu without a loader error.
2. Open a familiar test world and wait in one known location.
3. Confirm normal nearby chunks first, then observe whether distant LODs appear.
4. Save, exit, restart, and revisit the same view before claiming that LOD data persists.
5. If multiplayer matters, record client-only behavior separately from a deliberately configured Distant Horizons server.
6. If shaders matter, repeat the exact route first without a shader, then with one exact Iris and shader-pack tuple.

Troubleshoot the first failed boundary

Performance remains hardware-specific

Do not copy a creator screenshot’s distance or another player’s memory allocation into your profile and call it safe. A useful comparison needs the same hardware, Java runtime, Minecraft and mod tuple, world, camera route, vanilla and LOD settings, shader state, warm-up, and repeated measurements.

Without that controlled tuple, FPS, frame time, RAM, VRAM, server tick cost, bandwidth, and latency remain unknown. Lowering one setting is a diagnostic step, not a guaranteed fix.

Creator-controlled sources

• Distant Horizons project
• Distant Horizons 3.2.0-b for Minecraft 26.2
• Official versions list
• Creator-linked source repository
• Distant Horizons wiki

Rights and evidence: The software is labeled LGPL-3.0-only. That label does not establish reusable rights for every icon, gallery image, screenshot, logo, or video. MineBrush has no local creator JAR or original screenshot for this article and should link to the official versions route rather than mirror files.