17 Replies
did you use chunky?
/chunky
Chunky is known to cause LODs to turn into swiss cheese and bloat up world size, as can be seen in the attached screenshot.
We recommend you enable "Distant Generation" in Distant Horizons' settings and wait.
If you actually want to pre-generate vanilla chunks along with LOD data, disable Distant Horizons, wait for chunky to finish, then re-enable Distant Horizons.
oh..
it should eventually fix itself though. but that can take some time
no i dont have chunky
another world pregenner?
I checked, no, only WWOO and Tectonic
what about ferritecore?
should work fine with DH
do you have C2ME?
No 🤔
hhmm weird, chunky or c2me are usually the culprits
regardless, it will still fix itself if you wait long enough
it's a world from the DH 2.0 version... is that why?
it could still be migrating the chunks at the holes, so maybe
i have the same issue with holes and i dont know what to do. i deleted the DB and set the data compresstion to LZ4. i did not use chunky but my cpu load is all the way up. even if i use all the threads in my cpu the lod's holes wont load. NOTE: I have 12gb of RAM dedicated and minecraft still uses it all up. it quickly rises to 100% then falls back down to 50% and repeats
i also have bobby installed
Should c2me not be used?
Holes? Tectonic? Those two things has been mentioned together since Distant Horizons 2.0.2-a-dev.
You know what? I'm going to test Distant Horizons with Tectonic just to examine this behavior better.
ive had this happen to, just super random, i notice it happens more when tps is bad, if that means anything
You could try placing or breaking a block.whete the hole is to force a chunk update
Not with DH no
The point of c2me is that it multitreads chunk generation, but DH is already multitreaded, and that can cause conflict with c2me