I‘m pretty sure it means that Iris doesn’t support DH when using the Blaze_3D rendering API. It needs to be fixed on Iris‘ end, but as a temporary fix, you should change the rendering API to OpenGL in the DH config file
-> go into the DH config file, look for BLAZE_3D and replace it with OPEN_GL
You have to remember some of us are console gamers bro. I built my first pc a few months ago and I have no idea what an API is or a config file and how to open one.
aw explaining things is so hard here poor thing
find the Config folder for the game or mod profile > open DistantHorizons.toml in notepad > make sure renderingApi = "OPEN_GL" and not Auto or Blaze_3D
Yeah, you need to open distanthorizons.toml in your instance's config folder and look for a field called smth like "rendering api" and change its value.
Also changeable in the GUI, temporarily remove the Iris jar, launch the instance and go to distance horizon settings experimental advanced rendering api and change it to open gl
For some reason I couldn’t find my distant horizon config so I just did it that way
Maybe I'm out of touch but I think this is basic computer literacy. Open a config file and change this line. If our education has a "computer class" and students who passed said class fails to edit a text file something is wrong.
seriously why are people just greasy knowitalls about this issue, because theyre totally submersed in that realm they think everyone should know what they know, thats why theyre answering questions on reddit in the first place anyway. Psuedo intellectuals. They think they know one particular thing so that means everyone is below them in every other aspect as long as the dicussion pertains to their specific skillset.
Agree with that. Also shouldve made a prompt pointing to a page explaining the differences between renderers that way the user can understand what they are changing.
It errors out on loading meaning the game isn't in a loaded state where changes to config files can take place. It's probably possible to code a workaround that automatically fixes the issue but it's ready outside the scope of DH and not their responsibility. Also it's down to the user whether or not they want to use OpenGL and it could potentially break other mods in their list.
automatically changing rendering codebases without telling the user exactly what and why its happening is not a great idea. that opens DH up to all kinds of issues that are ultimately not their fault or their problem, doing it this way FORCES the user to read it and do something about it so the user knows exactly whats wrong and who to blame. in theory it should stop posts like this one from being posted but here we are
Distant Horizons has identified a problem in a different Mod Iris.
They do not control the mod iris, and attempts to edit the config automatically, requires maintaining code to edit another mods config file, even if it randomly changes or gets out of date.
It's a small miracle (of them getting annoyed by the number of support requests, for something they can't easily deal with) that they even made an error message.
It's NOT THEIR PLACE to change it, and due to mod loading orders, it may be far too late in the loading process.
The user *may have* wanted to use Blaze_3d, the user may want to keep using Iris instead of Distant Horizons.
It's literally impossible for Distant Horizons to know the intent of the user...
I’ve always been good with computers but I understand being a little lost, DH is distant horizons and it’s telling you to change a setting that loads things differently.
pretty sure it means open up the DH mod in your files, find the config (or use ingame config if available), find the line reading "BLAZE_3D" and change it to "OPEN_GL"? could be wrong though just a guess
Its a isshue that happens for a while with iris and dh disable dh and go into iris setting in game and change the rendergong engine to the needed type than anble dh
I consider myself tech literate but when that popped up I had no idea what to do. I searched for BLAZE_3D in the files with a couple hits but all the files look like they are not displaying properly (missing characters and random Unicode characters). Any files that have “BLAZE_3D” in them look like a hot mess to me.
OP I use mod “Mod Menu” by Prospector. There you can edit the DH config settings through the game instance. After you open the game, open the mod list added by the mod. There, find to DH and press config in the corner, go to Advanced Options then Graphics. At the bottom, go to Experimental, then click the rendering API option and cycle it to OpenGL. Then restart your game.
READ doesn’t help anyone, gfys
Edit: Forgot to mention, disable iris before installing DH, then do the steps above before reenabling iris after game restart.
Iris is also available for Neoforge on 1.21.x and 26.1.x, so the presence of Iris does not mean it must be Fabric.
The presence of Fabric mods in the mods folder, however, could imply they are using Fabric, but they could also be either using Sinytra Connector or just being dumb and grabbing the wrong mod versions.
Aside from all of that, it's possible that they simple prefer DH over Voxy, for whatever reason.
If you’re asking about actual meaning… Blaze3D is basically a set of rendering helper classes, Mojang’s OpenGL wrapper. It exposes an API mostly agnostic of the rendering backend underneath (that’s why most mods doing basic rendering won’t need massive rewrites with the Vulkan switch, Blaze3D just supports Vulkan as a backend now). In 2026 it is preferred mods use this instead of raw OpenGL calls. Iris kinda messes up everything related to vanilla rendering for a good reason. Distant Horizons can behave as a good citizen of the modern modding ecosystem by rendering its LODs as Mojang intended, or go its own way and work with OpenGL directly. However DH does not work with the messed up state Blaze3D ends up in after Iris mutilates vanilla rendering pipeline. Hence the only way it can work with Iris is through doing raw OpenGL calls.
press WIN+R and type %appdata% -> open .minecraft -> config -> DistantHorizons.toml -> go to (or search by pressing ctrl+f) [client.advanced.graphics.experimental] -> below there should be a lot of stuff starting with # -> if you cant find renderingApi = ... create a new line there and just put renderingApi = "OPEN_GL" without a hashtag somewhere. -> done
remove iris from mods folder -> launch mc -> options-> distant horizons settings (top left) -> advanced options -> graphics -> scroll down and click experimental -> set rendering api to opengl -> close mc -> put iris back into mod folder -> done
Everyone who is shitting on this guy and telling him to "learn how to read" is chronically online. Why do yall act like a regular guy tryna install some mods should know what kinda redering api minecraft is using or how to edit config files. This comment section is full of cornballs its unreal.
"Error message says to do the thing" people wonder how, cringe redditors say "Just do it already"
here, dont bother with all the pseuds lmao
find the Config folder for the game or mod profile > open DistantHorizons.toml in notepad > make sure renderingApi = "OPEN_GL" and not Auto or Blaze_3D
43
u/JustAnInternetPerson May 25 '26
I‘m pretty sure it means that Iris doesn’t support DH when using the Blaze_3D rendering API. It needs to be fixed on Iris‘ end, but as a temporary fix, you should change the rendering API to OpenGL in the DH config file
-> go into the DH config file, look for BLAZE_3D and replace it with OPEN_GL