DH 2.3.2-b Erroring and Crashing on Main World

Pertinent Info Version - 1.21.5 Modpack - Fabulously Optimized 9.0.0-beta.3 (Issue persists on a vanilla instance with no mods, but I am still mentioning my modpack because that's what I'm using) Launcher - Prism 9.4 Crash Log - https://mclo.gs/iztfQOZ Synopsis Distant Horizons works as intended with no error messages or crashes when creating a new world. It's only when I launch my main survival world (started back in 1.14) that the chat is filled with various errors and then subsequently crashes. I immediately loaded the world on a vanilla instance with no mods other than fabric API and DH2.3.2-b and the issue persists. Then I tried deleting the DH files located in my save's data folder and dimension folders, but the outcome was the same again. No fix.
41 Replies
majo24
majo245mo ago
/logstored
YAGPDB.xyz
YAGPDB.xyz5mo ago
You should send your latest.log file to provide additional useful information. Logs are usually located in the .minecraft/logs directory. On Windows: %appdata%\.minecraft\logs On Linux: ~/.minecraft/logs On Mac: ~/Library/Application Support/minecraft/logs Please upload the file to mclo.gs instead of sending the raw file. This makes reading the contents of the file a lot easier and improves the chances of you getting the help needed. After uploading the file, click on Save and send the link.
Nox
NoxOP5mo ago
whoops knew I was forgetting something here you go
Allium
Allium5mo ago
crash-2025-06-02_08.06.15-client.txt uploaded to mclo.gs
Uploaded by lieutenantprettybus100
majo24
majo245mo ago
And the same crash happens with only DH installed?
Nox
NoxOP5mo ago
Yes. DH and Fabric API.
majo24
majo245mo ago
Could you also send the crash report from only DH, without fabric api?
Nox
NoxOP5mo ago
yeah I just gotta make a fresh instance alright so wild conclusion here (hopefully) I created and launched a fresh instance with JUST Fabric Loader and DH2.3.2b and then loaded up my old world and I am still getting error messages like crazy but no crash even after 10 minutes of idling. "couldn't load or make chunk at [[etc, etc, etc]] Please try optimizing your world to fix this issue" over and over and over again (I have optimized the world before reaching out to you guys btw, that was the first thing I tried) wild guess but... is it possible that the reason MC was crashing was because the error log became too big? is that even a thing? oh god I started flying around just to see if things were running stable and I just learned all the DH LODs are incorrect they're generating what I can only assume is what would be at those coordinates had the world been made in modern versions when I fly close the LOD disappears, obviously, and actual terrain loads in which is completely different considering it was generated back in 1.14 update: let it run, flew around for a bit, consistent error messages and the issue mentioned above, but no crash this time
Miki_P98
Miki_P985mo ago
This error seems to not be uncommon on MC 1.21.5 DH works for most people it seems, but some have this error and there isn't a known fix It is the most common with wolrds edited or created with worldedit
Nox
NoxOP5mo ago
I have used MCA Selector in the past. Mainly when the Nether update dropped.
Miki_P98
Miki_P985mo ago
You can try to find a fix yourself or just go back to MC 1.21.4 and wait for a fix DH side (assuming DH bug is the cause)
Nox
NoxOP5mo ago
Bit of an update: I turned off error messages in chat through DH settings and it hasn't crashed yet so there might be a coorelation. But now the much bigger issue are these fake chunks LODs that are not at ALL similar to the terrain that actually exists.
Miki_P98
Miki_P985mo ago
CAn you send a screen shot or video?
Nox
NoxOP5mo ago
gonna trim down the recording now
Nox
NoxOP5mo ago
@Miki_P98
Nox
NoxOP5mo ago
dogwater quality, sorry, but you get the gist weirdly enough, the main base area has correctly generated LODs, but everywhere else is just wrong OH YEAH, and that massive error/fail at the end.. as if I didn't already have enough problems Oh, and for clarity, this was recorded back on my main Prism instance as initially outlined above, but these issues are happening on a "vanilla" install as well so I doubt mod conflicts are the issue Unless someone thinks of/finds a fix I'm gonna assume I just need to wait until the next Minecraft version/DH update. definitely an issue with the mod and my world specifically Fake chunks no longer an issue when you turn off Distant Generation
Miki_P98
Miki_P985mo ago
You can try setting distant generation mode to Internal_Server /generators
Nox
NoxOP5mo ago
but of course that means I'm missing out on the wonderful feature of Distant Generation
YAGPDB.xyz
YAGPDB.xyz5mo ago
- FEATURES: Complete generation of all LODs with mostly correct structures and trees. Does not save vanilla chunks, and is much faster than INTERNAL_SERVER unless C2ME is installed. - INTERNAL_SERVER: Generates and saves both DH LODs and vanilla chunks, has 100% correct LODs, because it also saves vanilla chunks it takes the most amount of drive space. Generation speed will suck unless C2ME is installed. - PRE-EXISTING: generates LODs for all existing vanilla chunks.
Miki_P98
Miki_P985mo ago
And delete your old LODs New LODs should match the vanilla terrain
Nox
NoxOP5mo ago
gettin' ready for a 30GB world lol y'know if it's any help btw I've installed DH and played on this world in the past, but only NOW has this stuff started happening brand new rig so that probably plays a part in it I'd imagine I was so excited to crank up the settings lmao
Mati
Mati5mo ago
i can help i think atleast
Nox
NoxOP5mo ago
yeah?
Mati
Mati5mo ago
are the lods correct for you now?
Nox
NoxOP5mo ago
after switching my generation mode to "pre-rendered chunks only" yes
Mati
Mati5mo ago
pre existing
Nox
NoxOP5mo ago
but it's still strange because in that video those chunks WERE already loaded that's why they're so off
Mati
Mati5mo ago
if i am not wrong then it doesnt generate lods i remember once having similar issue with a map, the lods that were being generated but were not the map blocks but just what it would look like on the version i have played i had to use chunky with dh set to pre existing idk if now the current version of dh still needs chunky or not
Nox
NoxOP5mo ago
exactly what I thought of doing, been loading chunks for the last 10 minutes now it works now, just like yours did but like jeez kinda ruins the whole point if I have to generate and load all these chunks
Mati
Mati5mo ago
generate? does it generate on its own
Miki_P98
Miki_P985mo ago
If you use Chunky, remove DH while it's running
Nox
NoxOP5mo ago
used chunky to generate a 2000x2000 square around me
Miki_P98
Miki_P985mo ago
Better to not use Chunky
Mati
Mati5mo ago
no..
Miki_P98
Miki_P985mo ago
And use Internal_server instead
Mati
Mati5mo ago
why though that wasnt a thing in the past tho
Miki_P98
Miki_P985mo ago
Casue it can couse holes in the LODs Not every time, not for everyone But when it happens, you baiucly have to start LOD generated again from 0 Not a risc worth taking
Mati
Mati5mo ago
it never happened for me
Miki_P98
Miki_P985mo ago
Indeed it wasn't Good for you
Nox
NoxOP5mo ago
yup I got holes after doing that oh well okay now I am ACTUALLY done I will try DH again once a few updates have dropped

Did you find this page helpful?