Game started crashing immediately on map load for specific map only
I have a world that I have been playing for a while now, and during that time I made backups as well.
Minecraft itself starts fine, and I can load any map, including the backups that are about 20 hours of game time old. But when I want to load the main world now, the game silently closes.
The launcher will state "exit code: 1". Loading the same world without distant horizons works fine. I have tried removing the "lod" folder, but this does not change anything.
This happens since the game crashed mid-game with a long, 10 or so digit exit code, which was a few days ago. Sadly I am not sure which of the past logfiles belongs to this crash in particular.
I have attached the latest log, and can give further ones if needed.
26 Replies
I don't see anything out of the ordinary in the logs.
Try running just DH and/or without DH and see if the issue persists.
i tried that - here's when it works:
- no DH active
- any world but my main world with DH active
here's when it crashes
- my main world with DH active
when i create a new world (which works) and then copy over the level.dat, it also starts to crash in the same fashion
on the other hand, i just tested creating a new world, and copying over everything but the level.dat/level.dat_old
this appears to work, but the player data is lost (and i am unsure what else)
edit: the seed, for example...
so apparently something related to DH is broken in the level.dat
if you would like to take a look
Are you running a old world? IE a world that was migrated to a new version of MC?
If so try disabling DH's world generator.
There is a bug with the world generator where worlds migrated from previous versions of MC can cause lag or other unforeseen issues.
no, the world was created in 1.19.4, using the terralith mod (but it seems to have worked fine together, and continues to do so in other worlds)
Hmmm... Still, try disabling the world generator and see what happens.
will do
this option?
Correct
crashed :(
Anything in the log?
this is the crash log from the launcher
should have realised before that it is not the same as the minecraft logs
minecraft log has nothing specific
(latest.log)
Oh that is fascinating (unfortunately in all the wrong ways).
It looks like this is a 4 way issue between: DH, Sodium, AMD, and something in your world.
There is a known issue between DH, Sodium, and AMD; although the fact that it is only appearing in a specific world leads me to believe that there is some entity or structure being rendered in your world that is specifically causing this issue.
Unfortunately I think most of the AMD fixes we've found have been outdated and need to be fixed on our end, sorry:
https://discord.com/channels/881614130614767666/1035937626944962641/1056622767585378304
interesting!
it does however appear now both with sodium on and off (i did definitely use it up to the point of trying to debug the issue)
pretty impressive how you could tell that interaction so quickly
also, yes, the fixes in that faq didn't work for me - i have drivers from before that point and changing sodium settings didn't affect anything
here's a crash log from without sodium, iris, starlight, lithium - if that helps in any way
what i noticed is that i could load up the world without DH, switch to creative, tp far away, close the game, add DH, and it would load again, so you are probably right about there being something screwing with the rendering
should be something vanilla, i guess, since it also happens with just DH active
Unfortunately we’ve had this issue fairly often so I’ve gotten good at spotting it 🙃
One last thing you could try is setting DH’s GPU upload method to “data” and rebooting the game.
However if that doesn’t work then we are back the previously suspected issue and you’ll just have to wait for a fix on our part.
tried it, but no change :/
but it's good to hear that you are aware of the issue and planning to create a fix in the future :)
btw, this is the crash message I get from the launcher when the game crashes while (thus far) successfully playing with DH on
after this, starting it again with DH on will crash with the exit code 1 and crash log I posted above
only solution apparently is to disable the mod, move away from this area (very far it seems) and re-enable it there
Translation:
An unexpected problem occured and the game has crashed. We are sorry [etc.].
This crash could have been caused by an outdated graphics driver or conflicts with screen recording software. Please make sure that your graphics driver is up to date and deactivate or uninstall any screen recording software that has been in use.
Click here for more information.this is the log of the latest run that lead to this crash
I have additionally noticed that it often happens when opening the inventory (i'd say 3/4 times when getting that crash)
could be unrelated though
one more update on this... I have noticed that the crash (possibly among other things?) happens for me when loading into a world with a map equipped in the offhand - unequipping it without DH on and relaunching the game with DH on again lets me load the world, with no other change in location
in general, there seem to also be some areas of my world that i can enter with DH on, but not load into from the main menu with DH on, but this time the bug seemed related to the map, I will check again if it appears in this fashion again at a later point
oh, though, @James Seibel (GMT-6) should I keep reporting my findings, or is the issue fully understood already and I'm just spamming? 😄
While I appreciate the extended reports, I think the majority of the issue has already been diagnosed. (AMD async uploading)
So all that’s left is to actually implement said fix.
Although, now that I think of it… I wonder if anything has been changed with the 2.0 pre-release.
If you have the time (and a 1.18.2 world that you can reproduce the issue on), could you try using the jar I linked in #announcements?