holes in LODS after generating with chunky
So I fired up chunky and generated my chunks, with distant horizons disabled from multimc launcher (not installed) with the help of c2me. When it finished, i uninstalled chunky and let distant horizons generate LODS with the "pre-existing chunks only setting". Following that, i can see maany holes in the lods, whose position seems to be consistent across restarts. Also, when i travel to the holes, they fill up, never to be seen again. (I'm using lithosphere worldgen and the loaded terrain is 64000 ny 64000 blocks, or 4000 by 4000 chunks) Can anyone help??
version:1.21.5
35 Replies
Try changing the mode to FEATURES or INTERNAL_SERVER
And make sure DH RD covers the holes (or when on server run DH pregen command),
maybe then DH will realise the holes are there
Do i need to delete existing lods?? Also, what does internal_server do?? Thanks in advance
Also, as can be seen in the image, the outer part of my world has been generated using the level.dat file of a superflat world, to simulate a wall. If i generate with features, does it check what level.dat has been used for each chunk, or does it generate based on the current leve.dat? Is preexisting chunks only the only way to achieve my goal?
Internal_Server mode saves vanilla chunks, it is a faster and safer Chunky alternative when wanting both LODs and vanilla chunks
!generators
- 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.
You added DH after Chunky finished so deleting the LODs might not help much, though it always might
You can try this as a last resort, but first try letting DH generator find and fix those holes
What about the different level.dat for the outer chunks?
Is the best option to restart?
Oh so should I set it to features or internal server for this to work??
Also, since this is for use in a server, and im generating in singleplayer, is it more advisable to generate in singleplayer and then transfer the world to the server (less confusing settings for me), or do it directly in the server? Are there any drawbacks of the first method? Btw thanks for your time
As far as I know those are just vanilla chunks, assuming Chunky generated them correctly, and you wanted them to be saved as you used Chunky, just keep them as they are
Depends how long it took to generate
If setting the generation mode to FEATURES or INTERNAL_SERVER and waiting does not work, you can try manually forcing a LOD update, by going to every missing chunks and placing and/or destroying a couple blocks (the more the better), then waiting in close proximity to this chunk for a couple minutes (preferably with higher CPU laod and with lower DH RD to focus on missing/broken chunk)
If it will take longer to manually fix everything than to start again, then and only then starting again would be a better chaice
It should no matter where you generate,
when generating on the server you have the access to the DH's pregen command and you don't have to have any player connected to the server, but you also have to now configure the server settings for the pregen and then for the gameplay, and not only your local settigns
Ok i will resolve this when i test on my pc but can i set the shape of internal server to a square from the center of the world, similar to chunky, so i can do roughly the same things i did with chunky??
DH is always a square
Can't chnage it to anything else
Oh so i generate, then change level.dat, generate a bit more, and i sould achieve what can be seen in the screenshot? (Srry i talk too much and repeat myself it just took too many hours to get it wrong again...)
WDYM by
change level.dat?In the save's folder theres a file called level.dat which determines how the world generates (seed, custom noise settings and all). If you switch the level.dat of a world to that of another world, any chunk generated in the first world will generate the same as the same chunk in the other world
I guess...
why not just create the world with the same seed?
Or just copy the world folder?
Because i want to have chunks of both "settings" in the same world. For example, i may want the outer chunks to be a superflat world made of bedrock up to the build height, as can be seen in the screenshot i had sent
BTW does the radius refer to half of the diagonal of the square or half its side?
half the side
ok well, the pregen command did not work, very slow (with c2me), and just stopped in the middle of the night and said "waiting to unload". Is there a way to have distant generation continue while noone is online?
Yes, using the pregen command, if pregen command does not work there is no other way
Try updating to latest nightly, if that won’t fix the command, make a post in #bug-report or bump an existing post with the same problem
are "maxSyncOnLoadRequestDistance" and "maxGenerationRequestDistance" in blocks or chunks?
the generation seems to stop...
No idea, haven’t configured any DH server yet, you will have to wait for someone else to answer that
ok well i am now gonna try it in singleplayer with internal server...
do lods save as the highest detail regardless of the quality preset used to generate them? kinda stupid question but i just wanna be sure...
Yes, always highest, I would even say higher than highest as I think the LOD DB stores each block (with some lossy compression)
ok, good to know ty
well rn im using internal server singleplayer,
should these holes fill up?
They should
well, now that enough terrain has generated, i can tell that there are some holes, but significantly fewer than before. if they have all fiilled up by the time it has all generated, i will resolve the question
btw thanks for your help and time!
where can i find this internal sever mode in the dh setting ?
Distant generation mode, it is one of the options there, on 2.3.3 it was renamed to Full
@Miki_P98 I've left it for some hours after the square finished and still, there are holes. I am going to update the mod and give an update. Is there anything I should be aware of?
also, the farther from the player the terrain is, the more holes there are...
I think that I've identified part of the problem. The lods render fine at a high detail level, but have holes at low detail levels. When i get close to the holes, they fill up, and terrain that previously did not appear to have holes got holes. generally, low detail levels have holes
is this a known issue?
I just observed that the holes' positions are consistent across world rejoining and game restarts.
all i wanna know is if there is anything I can do as a server host to fix this, or if it is an unavoidable trade-off of having lods for 16 million chunks in one database
I was generating nether, and I could observe line formations of lighter grey on the nether roof when viewed from above. They seemed to vaguely follow a concentric pattern, though they were very random. This is a similar problem, so I figured I coulf post about it here. I cannot provide any screenshots or files right now, but can anyone tell me if it is a common problem? The configuration is, again, full generation mode with c²me and noisium. Did I do anything wrong?
I will provide a screenshot once I am able to..
should I worry about these weird formations?
Hello there. Seems like I'm not the only one having this behavior as well.
https://discord.com/channels/881614130614767666/1360923316679999638
I also have the problem where the generation stops...
Patate324
YouTube
Minecraft 1.21.8 Distant Horizons. Loading in. 3.2.4 server and cli...
Minecraft 1.21.8 Distant Horizons. Loading in. 3.2.4 server and client. Pregen chunks server side.
^Pregen 248 chunks around this island. Client never connected to server. Both client and server running 3.2.4, with fresh config files (all default)
Is it normal that the outer chunks are loading in at random, faster than chunks closer to the player?
This behaviour doesn't seem to occur in single player (chunks are always loading in nearest the player)