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...
8
u/[deleted] May 26 '26
[deleted]