Guidefor players3 min read
Why Distant Horizons terrain doesn't get shaded by most shader packs
Distant Horizons renders far terrain through a separate LOD pipeline that shaders don't automatically see. What Iris actually added, which shader packs opted in, and what to check if distant terrain still looks flat or missing.
What it looks like
Distant Horizons extends render distance well past what Minecraft normally loads, drawing everything beyond your real chunk radius as simplified level of detail terrain, LOD for short. With a shader pack running, that far terrain often looks wrong in one of two ways: it stays flat and unlit while the nearby, normally rendered terrain around it gets full shadows, water reflections, and lighting, or in some cases it does not render at all, leaving a gap or a hard seam where the LOD terrain should be. Players run into this constantly. Comments on Bliss Shaders and Sildur's Vibrant Shaders on CurseForge ask variations of the same question: why is this shader not compatible with Distant Horizons, and will it be.
Why it happens
Distant Horizons does not extend Minecraft's normal chunk mesh outward. It builds a separate, lower detail mesh for far terrain and renders it through its own pipeline, because rendering full detail geometry at Distant Horizons' range would be far too expensive. That separation is exactly what makes the mod fast, and it is exactly what breaks shader compatibility by default.
A shader pack's lighting, shadow, fog, and water code is written against Minecraft's normal terrain rendering. It has no reason to know Distant Horizons' LOD mesh exists unless someone specifically wrote code for it. Iris, the shader loader most current packs run on for Fabric and NeoForge, added the plumbing for this starting around version 1.7.0: three extra shader programs, dh_terrain, dh_water, and dh_shadow, that run against Distant Horizons' geometry specifically, plus a DISTANT_HORIZONS flag a shader pack can check for at compile time. Distant Horizons 2.1.0 and newer is built to pair with that.
That plumbing existing in Iris does not make a shader pack support Distant Horizons automatically. Each pack's author still has to write those three programs and decide how LOD terrain gets lit, shadowed, and colored. This is why compatibility is per shader pack, not a property of Iris itself, and why the same Iris version runs some packs that handle Distant Horizons well and others that do not touch it at all.
What actually supports it
Bliss Shaders is a clean, dated example. Its own CurseForge file listings for versions 2.0.3 and 2.0.4 carry NOT DISTANT HORIZONS COMPATIBLE directly in the file name, matching the comments asking whether it would be added. Support landed in Bliss 2.1.0. Complementary Reimagined and Complementary Unbound both support it, but it is an opt-in setting under Other, Compatibility, Distant Horizons Compatibility, not automatic. BSL, Photon, and Sildur's Vibrant Shaders have added support since. This is not a stable, permanent list. Shader pack authors add and sometimes rework this support release to release, so check the specific pack's own changelog rather than treating any list, including this one, as fixed.
OptiFine sits outside all of this. It has no comparable integration for rendering Distant Horizons' LOD mesh under a shader pack, so the combination tends to be unshaded or outright buggy regardless of which shader you pick. If Distant Horizons plus shaders matters to you, that is one more concrete reason to be on Iris rather than OptiFine; see setting up Sodium and Iris for shaders for the installation order.
What to check
Confirm the shader pack itself advertises Distant Horizons support, since Iris supporting the mechanism is not the same thing. Look for a Distant Horizons toggle in the pack's own options, since several supported packs gate it behind a setting rather than enabling it by default. Keep both Iris and Distant Horizons reasonably current, since the integration is version gated on both sides. If terrain still looks wrong at night or the sky renders incorrectly on a pack that does support it, try Distant Horizons' own LOD Shading setting, switched to Old Lighting or Forced, or its transparency setting under Advanced, Graphics, Rendering, set to Complete, followed by a restart. Both are documented rough edges even on otherwise working combinations, not signs that something is broken on your end specifically.
