Understanding DH's Range & Border Limits?
Hey all, I was just wondering if yall could help me figure out the numbers for where and how to set up DH border limit? I thought I read somewhere that there was a way to specificy a limit to which DH would stop generating chunks afterwards.
For reference, I used chunky to pre-gen a radius of 4000 (chunks, not blocks I believe?) by doing /chunky radius 250c and ran it to completion. I couldn't figure out at which point DH has reached that point if it makes sense. So far it's been running and genning really well on this modpack!
12 Replies
Using Chunky's pregeneration and Distant Horizons at the same time is known to cause LODs to turn into swiss cheese as can be seen in the attached screenshot.
Distant Horizons has a built-in LOD pregenerator called Distant Generation. However, Distant Generation only saves the LODs, not the vanilla chunks. This is in order to save file space, as pregeneration often leads to huge file sizes.
If you actually want to pregenerate vanilla chunks along with LOD data, remove Distant Horizons, use chunky to pregenerate, and add Distant Horizons back. Once the pregeneration is done and Distant Generation is enabled, Distant Horizons will convert all the pregenerated, saved chunks, inside your DH Render Distance to LODs.
If you only want the LOD data and don't need the vanilla chunks, use Distant Generation instead of Chunky's pregeneration.
Note, these issues may not only occur with Chunky, but also with other similar pregeneration mods.
I know I should switch over from chunky to c2me, but I already was half way genning the world over night so I wanted to try it on this for now!
Also, would there be any issues if I changed from chunky to c2me after all this genning?
No, you can still switch,
but the swich is from chunky to DH pregenerator, C2ME is just a mod that makes worldgen faster and it is required for Internal Server generator to not be painfully slow
250c is 250 chunks so 4000 blocks
:noted: :BCNod:
I imagine its definietely generated past that point by now, I remember reading else where you mentioned itll just keep genning unless prompted to stop or a border is put up or something like that?
If you set distant generation to per-existing only, DH pregenerator will be disabled and DH will only pull already existing pregenned chunks
Do I change that with the commands in game?
or is that a text file change
You probably can, but editing the text file will work for 100%
I think that server side DH indeed has additional maksimami radius from 0 0 config, but I don’t know much about it
It won’t generate anything past the client requested RD for sure, so you can controle it this way and after pregen set the distant generation to off/none or preexisting only to turn off any further generation or just decrease the CPU load preset
Okay! I would assume that DH's config is located within the general config files for mods right?
It should
I couldn't find it at the moment, but thats okay! I had a follow up question if you dont mind. When it comes to the generation.mode should that be set to Internal_Server? bc c2me would help DH's generator which you were talking about before?
If you want to keep vanilla chunks generates by DH and have 100% accurate LODs set it to Internal Server
If you want only LOD and don’t want vanilla chunks in order to save drive space and you skate happy with almost fully accurate LODs use Features
C2ME helps in both cases but is almost required by Internal Server if you don’t want to wait years, Features is quite fast on it’s own, C2ME speedup is smaller and it is still faster then Internal