"Database Disk Image is Malformed"
Game version 1.21 and running the latest dev build 2.3.0 (had the same issue on 2.2.1 however)
honestly not sure what's causing this, but there are a few large chunk holes, and when I move to the area to load them, my disk & CPU usage spike for ~30 seconds, and then after the usage goes down, when i move away the holes reappear.
My CPU is running at a constant 70% even when idling, which is unusual. Turning down LOD builder threads does nothing for CPU performance, but turning file handler threads down instantly drops it.
17 Replies
I'm not sure where the weak link is, as I cant tell the game is trying to build/write them due to the disk & CPU usage spike when moving to areas without LODs built.
I can provide a recording of the game and a resource monitor if need be, just let me know
I've looked through a few threads that have had similar issues and they said the issue was fixed, so idk
anytime i sit in one of the areas with one of these glitched chunks, it just EATS up my resources, because (I assume) its just continually trying to write/read/build the LODs and just never doing so
do you care about your LODs? if not, can you try resetting them and seeing if that fixes the holes? you can reset them by deleting the sqlite at
/lodstored
Single Player:
- Overworld:
.minecraft/saves/WORLD_NAME/data/DistantHorizons.sqlite
- Nether: .minecraft/saves/WORLD_NAME/DIM-1/data/DistantHorizons.sqlite
- End: .minecraft/saves/WORLD_NAME/DIM1/data/DistantHorizons.sqlite
- Custom Dimensions: .minecraft/saves/WORLD_NAME/DIMENSION_FOLDER/data/DistantHorizons.sqlite
Multiplayer:
- .minecraft/Distant_Horizons_server_data/SERVER_NAME/unfortunately my sqlite file is about 3GB and would take ages to re-fill out.
this is actually the second time I've had to rebuild my LODs because i accidentally deleted the old ones when clearing out some space on my drives lol
so is there just no way to fix the corrupted chunks? I just have to live with the holes in the world?
I don't know if there is a fix to this problem. You are the first person I come across that has it. Most of the time going to the chunk, with a high cpu load in DH's settings, and placing/breaking a few block in the affected chunk, then waiting a few minutes, resolves the issue. But I doubt that will help here
messed with the debug output settings, and this warning seemed of interest
ill try what you recommended in a bit, it might help
Oh, that's not a good sign
yeah building on it didnt work, just cuts off in the same place
should move this post over to #bug-report since it seems like this is possibly an issue with the mod?
Only if you can provide more info, like a reliable way to get the same issue, or logs that tell what the problem is. Otherwise the bug-report will be a bit useless
Im going to try and see if there's any other warnings/errors of note, but for the time being I'm going to rename the thread in-case anyone recognizes that error and has a fix
Alright
I'm going to take a wild guess and attribute the corrupted chunks error to hard drives being hard drives.
I bought an NVME and put Minecraft on there, and I haven't had any issues. My assumption to what caused the error was a mix of low write speeds combined with a game crash/game close before the mod finished building/writing the LODs to file, and the mod wasn't able to figure out what to do with the partially completed chunk data
hhmm interesting. havent heard anything like that before