Sildur's Shaders Compatibility | Versions & Loaders

Minecraft Java

1.7.10-26.2

Broad fallback code keeps old releases supported, though newer transparency features can be limited in Minecraft 1.7.10-1.15.2 under OptiFine.

Shader loaders

Iris & OptiFine

Iris is usually preferred for modern Fabric setups. Always match OptiFine to the exact Minecraft version.

World renderers

DH & Voxy

Current releases advertise Distant Horizons and Voxy support. The latest Vibrant pipeline also covers the Nether and End.

GPU and preset guidance

Hardware tier	Start here	Adjust first
Integrated / older GPU	Basic Fast or Enhanced Default Fast	Render distance and shadows
Entry dedicated GPU	Vibrant Lite or Enhanced Fancy	Shadow resolution and reflections
Modern midrange GPU	Vibrant Medium or High	Volumetric light and clouds
High-end GPU	Vibrant High, Extreme, or Extreme-VL	Resolution and distant rendering

These are starting points, not frame-rate guarantees. Resolution, render distance, mod count, world complexity, driver quality, and CPU performance all affect results.

Mod compatibility

Shader loaders alter the rendering pipeline, so visual mods are the most likely source of conflicts. Test the shader in a clean Iris/Sodium or OptiFine profile before adding a large modpack. Resource packs usually work, but packs with custom normals, specular maps, skies, or emissive textures can change the result.

Vibrant 2.01 notes that some reflections remain inaccurate and that fog can appear denser in OptiFine than Iris. Those are upstream limitations rather than broken downloads.

VERSION SUPPORT

Sildur's Shaders compatibility guide by version

This Sildur's Shaders compatibility guide uses current Modrinth release records for Vibrant 2.01, Enhanced Default 1.19, and Basic 2.6, which list Minecraft Java 1.7.10 through 26.2. That unusually broad range is possible because the shader code contains fallbacks for older rendering behavior. It does not mean every effect looks identical across twelve years of Minecraft versions.

Minecraft 1.7.10 through 1.15.2 can have limits around reflections through transparent blocks because older OptiFine versions do not expose the same features as newer loaders. Current releases and Iris can use more of the rewritten pipeline. When an old profile displays a simpler reflection or transparency result, check the release notes before treating it as a corrupt ZIP.

Loader compatibility is just as important as the version number printed by Minecraft. Choose an Iris build, Fabric Loader version, and Sodium combination intended to work together, or use the exact OptiFine build for that Minecraft release. A shader cannot correct an incompatible loader stack. Test the loader with no shader selected before diagnosing Sildur's Shaders compatibility.

Minecraft range	Expected support	What to check
1.7.10-1.12.2	Fallback support for older OptiFine-era rendering	Java version, OptiFine build, transparency limits
1.13-1.15.2	Supported with some older feature limits	Driver, loader build, reflections through transparency
1.16-1.21.x	Broad Iris and OptiFine coverage	Match all loader and mod versions
26.1-26.2	Listed by current releases	Use current Iris or OptiFine and rendering mods

IRIS OR OPTIFINE

Loader compatibility and differences

Iris is generally the preferred loader for a modern Fabric profile. It is designed around shader compatibility and commonly runs with Sodium. This combination gives players a clear route to current Minecraft support and performance-focused rendering. Keep Iris, Sodium, Fabric Loader, Fabric API when required, and Minecraft within a compatible set instead of updating only one component.

OptiFine remains relevant for older installations and players who already depend on its combined graphics options. Match its release exactly to Minecraft. Vibrant 2.01 notes that fog density can appear higher under OptiFine than Iris, so two correct installations may still look slightly different. That difference is not proof that one download is broken.

Angelica is an Iris-derived option used in some older modded environments. Vibrant release notes describe support and mention that it can provide reflections through transparency where older OptiFine paths cannot. Because large modpacks control their own compatible versions, follow the pack maintainer's loader instructions before replacing renderer components.

DISTANT TERRAIN

Distant Horizons and Voxy compatibility

Current Sildur releases advertise support for both Distant Horizons and Voxy. Vibrant 2.01 extends its updated handling to the Nether and End. Support means the shader includes code for those renderers; it does not remove the additional workload created by distant terrain. The visible result and performance still depend on the renderer version, loader, GPU, memory, resolution, and configured distance.

When Distant Horizons terrain clips, flickers, or uses the wrong fog, first confirm that the shader, Iris, and Distant Horizons versions are intended to work together. Clear old shader caches if the loader documents that step, retest default shader settings, and compare the Overworld before testing dimensions. Vibrant's release notes mention fixes for water clipping and emissive lighting, so older builds may show issues already addressed in 2.01.

Voxy can provide a different distant-world pipeline and its own performance profile. Start with a lower Sildur preset and conservative Voxy settings, then increase one distance or quality option at a time. Using Extreme-VL and a maximum distant-world configuration simultaneously is a high-end workload, not a sensible baseline for compatibility testing.

Resource packs, mods, and GPU compatibility

Most ordinary resource packs can be used with Sildur's Shaders because textures and shaders occupy different roles. Packs that add normal maps, specular maps, custom skies, emissive materials, or unusual connected textures can change the result more significantly. If colors, reflections, or glowing blocks look wrong, test the default resources before editing shader settings.

Rendering mods are more likely to conflict than gameplay mods. Anything that replaces chunk rendering, clouds, fog, the sky, entities, or post-processing should be tested carefully. Error logs and shader compilation messages are more useful than a screenshot alone because they identify the program or stage that failed.

There is no single GPU requirement for the entire family. Basic Fast and Enhanced Default Fast suit the widest hardware range. Vibrant Lite and Medium are appropriate steps for dedicated or capable integrated graphics, while High, Extreme, and Extreme-VL need increasing headroom. Driver support matters as much as raw performance, especially on old integrated GPUs that lack modern OpenGL behavior.

COMPATIBILITY FAQ

Sildur's Shaders compatibility guide FAQ

Does Sildur's Shaders work with Minecraft 1.21?

Yes. Current release records include the Minecraft 1.21 family. Use an Iris or OptiFine build made for the exact point release, because a loader for 1.21.1 is not automatically compatible with every later 1.21 update.

Is Sildur's Shaders compatible with Sodium?

Iris commonly runs alongside Sodium and is the usual way to combine Sodium's renderer with shader support. Use versions documented as compatible and avoid adding a second renderer that replaces the same systems.

Can low-end PCs run Sildur's Shaders?

Many can run Basic Fast, Enhanced Default Fast, or Vibrant Lite, but performance depends on resolution, render distance, CPU, driver, and mods. Start low and measure frame time in a normal world.

Why does OptiFine look different from Iris?

The loaders expose and implement some rendering behavior differently. Vibrant notes denser fog in OptiFine, and old versions have transparency limitations. Small visual differences can exist even when both setups are valid.

Does Sildur's Shaders work on Bedrock Edition?

No. The downloads here are Java Edition shader ZIPs for Iris or OptiFine. Bedrock uses a different rendering system and cannot install these archives.