Consistent Shader Compile Errors
Using the latest DH release 2.3.3-b Complementary and Photon creates compile errors.
If switched to BSL which doesn't encounter them, and then back to the ones which encountered them prior it works again. I suspect that the
DISTANT_HORIZONS
is for some reason not set property as both photon and Comp declare DH uniforms under that defineSolution:Jump to solution
Can confirm it's fixed on 1.21.7 neoforge thanks to https://gitlab.com/distant-horizons-team/distant-horizons/-/commit/1e636072334098c748b6df43cf572ed370a65c22
GitLab
Fix AfterDhInitEvent not firing on Neo (1e636072) · Commits · Dis...
Fixes some Iris shader compile issues
62 Replies
latest.log
uploaded to mclo.gsUploaded by spaceagle17
To reproduce: launch the game and select Complementary or Photon
Multiple users confirmed this as well in my server and in the Photon one, that is why I came here :)





So yeah I think that shows that it's something consistent
Reminder that Complementary has those only under the
DISTANT_HORIZONS
define declaredTy will try when back home :)
I do hope this also fixes shader compile errors as that I believe to be a different error to the visual issues
Photon as well, and both of these had compile issues leading me to think that the said define was just undefined

Doesn't look like it
Will later try it out myself and if not comment on the gitlab issue as it doesn't seem that issues here in discord are looked at as often
latest nightly doesn't seem to resolve the issue for me
Nope it does not. I commented on the issue tracker https://gitlab.com/distant-horizons-team/distant-horizons/-/issues/1087#note_2629070970
If it's not the
DISTANT_HORIZONS
then I am out of ideas as everything point to that just being undefined
This is from iris source code to define said define
Perhaps the hasRenderingEnabled() part broke on DH end and iris does not read it correctly anymore? No clue how the API works, just guesses. I doubt it would be the first part.Does the issue only occur with Oculus? Iris works properly for me.
My test was with iris for 1.21.7 on neoforge
Will try rn with the nightly myself
I'm experiencing the same issue on 1.21.1 with Neo .192 / Iris 1.8.12 -- the nightly did not fix the issue. 2.3.2 works, also up to (sorry can't remember which build, early June?) a certain nightly of 2.3.3 was fine
Can reproduce with
DistantHorizons-neoforge-2.3.4-b-dev-1.21.7
on neoforge and Complementary r5.5.1 and latest release of PhotonAs I already mentioned both use the DISTANT_HORIZONS define
This is Complementary

This is photon - it also puts samplers and so on under the define

No issues on fabric 1.21.7 with the nightly
Only on neoforge
I was using iris as well to do the testing, no oculus
If y’all can find which nightly build broke it that help me fix the problem.
NightlyBuild_1.21.7-1edd8097-2025-07-11T07_29_46-05_00.zip
still works
so it is a rather recent issue
Seems to have broken in NightlyBuild_1.21.7-2bc5169c-2025-07-12T08_02_08-05_00.zip
unless I missed oneIf I did not accidentally skip over a nightly it should be this

@James Seibel GMT-5 :)
Weird.
Thanks for finding that, can you share which versions of Neo, Iris, sodium, and the shader you used that had the problem?
Ofc
DId rn a fresh instance for testing
yup, breaks for me right on the same commit
https://gitlab.com/distant-horizons-team/distant-horizons/-/commit/2bc5169ce51e1b858ece0bcbc88a96ed2d070257
GitLab
Closes #1084 (AfterDhInitEvent firing before DH config setup) (2bc5...
This is a mod that adds a Level Of Detail (LOD) system to Minecraft. This implementation renders simplified chunks outside of the normal render distance allowing for an...
My guess is still on the DH define not being defined XD
Not sure why that commit would make it not work but I assume
DHCompat.hasRenderingEnabled()
this part in iris no longer is true after that commit
That is if it's actually the DH define and not something completely randomfor 1.21.1 i was using (all on the latest):
Neoforge: 21.1.192
Sodium: 0.6.13+mc1.21.1
Iris: 1.8.12-snapshot+mc1.21.1-local
^ Same. That's the commit that broke it
Glad that's confirmed :)
From what I can tell iris uses the
DhApiAfterDhInitEvent
that got moved in the commit, so i guess something is breaking there?
https://github.com/IrisShaders/Iris/blob/b4b2c22c1587264989d746ae57423c32cf6dfcb4/common/src/main/java/net/irisshaders/iris/compat/dh/LodRendererEvents.java#L52Why does it work on fabric just fine tho?
That's the odd thing
I think
postInit()
is not being called on neoforge, the Post-Initializing Mod
log message does not appear in the neoforge log, while it does on fabric
https://gitlab.com/distant-horizons-team/distant-horizons/-/blob/main/common/src/main/java/com/seibel/distanthorizons/common/AbstractModInitializer.java#L182
Before that commit the event was called twice in onInitializeClient()
and onInitializeServer()
@James Seibel GMT-5
@SpacEagle17 does Post-Initializing Mod
appear in your logs?Can check in a bit
Huh, interesting.
Well that should be pretty easy to test, thanks!
it's never reaching the delayed setup for me
This isn't being called i think
https://gitlab.com/distant-horizons-team/distant-horizons/-/blob/main/common/src/main/java/com/seibel/distanthorizons/common/AbstractModInitializer.java#L112
and some people on forge don't have the dh command, at least there were issues about that
https://discord.com/channels/881614130614767666/1382587321899155578 https://discord.com/channels/881614130614767666/1369897754264076339
Nope
Tested on Neoforge 1.21.7
then its basically what i guessed, the postinit isn't being called which causes iris to never see the event and not initialize relevant stuff
Yep makes sense. Any clue why it works on fabric and not neo?
DH needs a mod initializer for each mod loader
and this is the abstract mod initalizer which abstracts away most of the things needed for that
And I guess some event on the forge side isn't being called
Makes sense and sounds so nice to have a monojar like that XD
I gotta switch between branches whenever I do a change and copy paste that into the other branches myself for each mod loader I support lol
which is somewhere in here:
https://gitlab.com/distant-horizons-team/distant-horizons/-/blob/main/neoforge/src/main/java/com/seibel/distanthorizons/neoforge/NeoforgeMain.java
Did anyone test if the same issue happens on forge 1.20.1 with oculus/embeddium as well?
I can't test that rn since I'm reinstalling my OS
Also can't test rn and nope I didn't
I tried before but forge refused to launch for some reason lol
GitLab
Fixed Forge not firing AfterInit API Event on clients (Closes #1095...
This is a mod that adds a Level Of Detail (LOD) system to Minecraft. This implementation renders simplified chunks outside of the normal render distance allowing for an...
it's broken for me on 1.20.1 with forge / oculus / embeddium.
Unknown User•2mo ago
Message Not Public
Sign In & Join Server To View
broken on 1.21.1 with neoforge/iris even with the latest nightly build:pookiessadshake:
Well luckily for you that's because the nightly build that fixes the problem hasn't finished compiling yet. Give it another 40 minutes then try again.
ohh, I see, thanks a lot :pookieshihi:
i compiled the PR locally, but I still get the corruption/tearing when resizing. Reloading shaders fixes that
That is an old bug
Unrelated to this
Can you try if Complementary no longer has cimpile errors?
comp works
Nice, then this should indeed be fixed now hopefully
Solution
Can confirm it's fixed on 1.21.7 neoforge thanks to https://gitlab.com/distant-horizons-team/distant-horizons/-/commit/1e636072334098c748b6df43cf572ed370a65c22
GitLab
Fix AfterDhInitEvent not firing on Neo (1e636072) · Commits · Dis...
Fixes some Iris shader compile issues
Forge also had this issue right? Should I also test there?
Can confirm, also works fine again on forge with oculus
Thank you :CatCare: