[1.15.2] Game crashes when shaders are enabled or changed

[JCLaHoot]

Description of Issue

Game crashes (and auto-reboots the forge loader 🤨) when you enable a shader.

Steps to Reproduce

1. Choose a shader
2. The game will most likely crash

OptiFine Version

preview_OptiFine_1.15.2_HD_U_G1_pre28.jar

Installation Method

Drop the JAR file into "mods" folder

Fabric/Forge Version

Forge 31.2.21

Other Installed Mods

https://pastebin.com/GjuiCahB

Log Files/Crash Reports

https://pastebin.com/tPFXzE6A

Prior Testing

I've gotten shaders to work after a crash/reset but it's hit and miss. Sometimes my selection persists, sometimes not. 90% of the time choosing/changing shaders causes a crash.

Additional Information

Running on Mac OS with an AMD card.

[sp614x]

Most probably a conflict with one of the installed mods.

• To find the conflicting mod, split your mods into 2 groups (not including OptiFine). Remove one group, and test in-game. Keep the group that has the problem, and repeat until no more mods can be removed without the issue disappearing.

[SkyeRise]

I can confirm that this is most likely a mod conflict as I have been using Optifine with shaders since eve before this version. Especially in pre30, a large amount of issues was finally gone, so this ticket might already be obsolete anyway.

[JCLaHoot]

Update:

• This only happens when I'm turning on/off shaders, but not when I'm switching between shaders.

• The behaviour (game "rebooting" and reloading all mods) still happens when I have no mods installed, but the process is much faster (no mods to load) and it does bring me back to the game (without having to reload the world).

• With all the mods installed, the game reboots, all the mods load from scratch, and it hangs here forever:

  

• By testing with the 2 groups method, I found out that Immersive Engineering crashes when it tries to reload.

• Oddly, when I tried to reproduce the issue with all the mods except IE running, I got the hanging behaviour, so there must be a conflict between another 2+ mods that I won't be able to easily pinpoint with the two groups method.

• in 1.12, mods didn't have to reload when I turned on/off shaders, so I assume it's not normal, but maybe it is?

[Barerock]

I'm in 1.16.4 using the Complementary Shaders offshoot of BSL shaders (which run pretty okay on the new versions) and this issue is fixed. CS has a "compatibility mode" which is meant to address issues like this. Is also a pretty good shader pack in general, lots of configurability. I'm NOT using the compat mode btw, but I imagine some of it's features are implemented in the normal modes for... compatibility. Good luck!