[Neoforge] Crash on world join (Singleplayer)
Both 2.3.2 beta release and 2.3.3-b Nightly crash on world join. Latest AMD driver (25.5.1), DH 2.3 works fine on Forge 1.20.1 for me.
Latest.log https://mclo.gs/dyxxBt0
Debug.log https://mclo.gs/lEysaqJ
hs_err_pid.log https://mclo.gs/n3qzzWt <---- 🥺
4 Replies
I was using vanilla launcher, using Modrinth or Prism doesn't cause this.
thats very curious
any java arguments you have in the vanilla launcher that you dont have in modrinth or prism?
Or the other way around
No different args. I actually saw a post in #help-me with basically the same issue, and hardester said it's a common AMD issue.
https://discord.com/channels/881614130614767666/1379613154769764392
So interestingly enough the solution for the vanilla launcher is to disable shaders + world gen in DH before loading a world, then re-enabling after in.
Also discovered the updater doesn't delete the old .jar for me when updating on the vanilla launcher (2.3.2 --> 2.3.3-b-dev). Tested it twice. But, works fine under Prism.
b.3.15.40-2.3.2 is the Mojang launcher version
I tried using lwjgl 3.3.6 with arg --enable-native-access=org.lwjgl, but that didn't help. I'm using 3.3.3 with Prism.
There are similar issues opened on the issue tracker that are related to using mesa/macs with fabric, but I couldn't find any for Neoforge specifically.
From what I've seen reported is this only happens on 1.21.x, not in 1.20.x -- and I can confirm DH 2.3 works on 1.20.1 for me on Forge or Fabric (with the vanilla launcher).