Shaders stop working after reloading them
Mohawk1025 opened this issue · 13 comments
Minecraft Version
1.21.1
Iris Version
1.8.0-beta.7+mc1.21.1
Sodium Version
0.6.0-beta.4+mc1.21.1
Operating System
Windows 11
What is your GPU?
Nvidia GeForce RTX 3080
Java Version
Java 8
Reproduction Steps
I am playing on All the Mods 10. Everything was working fine until I updated to All the Mods 10 1.16. Now the shader pack works when I first start up the game, but if I travel to another dimension (e.g., the Mining Dimension), it stops working and cannot be reloaded. A message pops up that says:
"Iris encountered an issue trying to load the shader; please report this to Iris developers. Copy Info"
The info just says
"Shader compilation failed, see log for details"
I'm not sure which log to upload.
Crash Report file and latest.log
No response
Additional context
No response
Just checked, and the issue also happens without traveling to a different dimension. I loaded up the game; shaders are working. I hit the hotkey to reload shaders, and after the second reload it stopped working and gave me the same error message.
I should also add this is happening with multiple shader packs (specifically BSL Original, and Complementary Unbound + Euphoria Patches).
OK, just checked again and it appears to be happening with every shader pack that's in All the Mods 10. As soon as I reload shaders it stops working.
I downgraded to ATM 10 1.15, and the issue disappeared, so it's something with version 1.16.
This is their changelog for 1.16.
• Added KeybindsPurger
• Added Mekanism Covers
• Removed Achievement Optimizer
• Made Omega Upgrade use unobtainium nuggets (Satherov)
• Added Stave's carts to the ATM Star (wtd)
• Added Nature's Aura Quests (Toblerone)
• Added Ore hammer dust from various modded ingots (pr0saic)
• Added Undergarden Quest (ToshibaEC0Microwave)
• Neoforge Version is 21.1.73
That's the same version of Neoforge as 1.15, so maybe it's something else in one of those updates? I suspected Mekanism Covers at one point, but I removed all the covers I had placed in the world, and issue still persisted.
The relevant log file will be located at .minecraft/logs/latest.log when the issue occurs, and can be uploaded here in it's entirety
Are you sure you're running this version of Minecraft with Java 8, by the way? I'm pretty sure 1.21.1 requires Java 21+ unless there's some mod or Neoforge itself lowering that requirement. Both the vanilla launcher and the Modrinth app should install and use Java 21 by default, regardless of what Java version you might already have on your system
I have confirmed this is a bug with Mekanism Covers. It edits the shader code of all shaders to try to make their covers change in real time.
I have confirmed this is a bug with Mekanism Covers. It edits the shader code of all shaders to try to make their covers change in real time.
I had a suspicion it was that mod. Thanks for confirming. Hope it gets patched soon. I was super excited when I saw they had released Mekanism Covers.
The relevant log file will be located at
.minecraft/logs/latest.logwhen the issue occurs, and can be uploaded here in it's entiretyAre you sure you're running this version of Minecraft with Java 8, by the way? I'm pretty sure 1.21.1 requires Java 21+ unless there's some mod or Neoforge itself lowering that requirement. Both the vanilla launcher and the Modrinth app should install and use Java 21 by default, regardless of what Java version you might already have on your system
No, you're right. I had to download the JDK to run this modpack, and it's Version 23. I got confused because I checked the Java control panel, and for some reason it says Version 8. (I'm launching through Curseforge.)
Also I don't know if I still have the relevant log file since I downgraded to ATM 10 1.15. But another user commented in here that they confirmed the problem is with Mekanism Covers.