Java Edition, Iris; Bedrock requires a separate graphics path · 3 min read

Shaders do not work: settings, ZIP files, black screens and GLSL errors

Start with a sign of failure. The missing button, invisible ZIP and black screen after Apply occur at different stages; Reinstalling all mods immediately hides the reason.

LonelyCraft editors · Updated

Computer with world Minecraft open and keyboard on table
Illustration: a computer with the Minecraft world open and a keyboard on the table. This is an artistic scene, not a snapshot of a specific server.

There is no Shader Packs button

Check the selected launcher installation and its Game Directory. Sodium without Iris does not add a shader loader. Open logs/latest.log of this particular profile and find Iris in the list of downloaded mods. If it is not there, check mods, the game version and the loader.

The individual profile and compatible components are discussed here. Installing Iris.

There is a button, but the ZIP is not visible

Open Shader Packs → Open Shader Pack Folder. This directory should contain the finished ZIP release. Take a look at the archive: the folder shaders is expected, and not another archive or directory with installer sources. Do not rename .jar to .zip: the extension does not turn the mod into a shader.

After Apply the picture broke

If the menu is available, turn off shader in the Shader Packs screen and apply. If nothing is readable, close the game and temporarily move the problematic ZIP from shaderpacks to another folder. Run without it, then check in the file and reset the package options before trying again.

Test the second package on default settings. If one is broken, the problem is most likely related to it or its combination with the driver. If both, temporarily leave only Iris, compatible Sodium and the necessary dependencies, disable resource packs. In particular, resource packs that replace core shaders have limitations in Iris.

What do the lines in the log mean?

Immediately after the failure, copy logs/latest.log, otherwise the next launch will replace it. Look for compile, link, GL_INVALID, OpenGL, ERROR and the program name, such as composite or gbuffers_terrain. Save 20–40 adjacent lines: the phrase “shader failed” alone explains almost nothing.

A GLSL compilation error means that the graphics program did not build; This is not proof of a lack of RAM. The OpenGL error number also does not indicate the culprit by itself. Attach Minecraft version, Iris, Sodium, ZIP, OS, GPU model and driver. The Iris documentation describes additional debugging capabilities for package developers.

Check your GPU model and known limitations on Sodium's driver page. Get the Windows driver from NVIDIA, AMD or Intel; On macOS, the graphics driver is updated along with the system. If the hardware feature is not supported, another ZIP or regular graphics is more useful than reinstalling Java.

When the failure appears only in the full assembly, reduce the set by dependent groups. Finding mod conflicts.

At what stage did the shader launch stop?
Editorial diagram: at what stage did the launch of shader stop.Scroll the diagram horizontally.Open full-size diagram

Frequently asked questions

Need to remove all config?

First, reset only the options of the problematic package and save a copy of the settings.

What to do with Exit Code 1?

Need latest.log: generic exit code doesn't explain why.

The driver is new, but the package does not work?

Check GPU limitations and minimum mod set; The update does not add missing hardware features.

Views: … · One view per browser per day

Was this useful?Total score: …

One reaction per browser. Click again to remove it, or choose the other reaction.

Sources and documentation

shaderIrisdiagnostics

Read on

Shaders do not work: settings, ZIP files, black screens and GLSL errors — Lonely Craft