Extremely slow world generation using datapacks (Terralith+Terratonic) or JJ Thunder.

Initially, I installed DH to make my game look like those videos on social media about hyper-realistic Minecraft worlds. After almost 7 days of racking my brain to get the game working with approximately 170 mods, I can say that I'm almost finished. I've fixed crashes, that bug where the LODs look like Swiss cheese, configured shaders, mods, etc. Now I have a small problem, which is nothing compared to the previous ones, but I would like to solve it as soon as possible. When watching some YouTubers generate their world with DH, I've noticed that on my PC, the worlds generate extremely slowly compared to how smooth they do for others. So I started testing and disabling mods to see if I could fix anything, and I managed to make the vanilla world generation go pretty well. So I went to the next step and started using datapacks. This is where my problem comes in. For some reason, the datapacks I use (Terralith+Terratonic) or (JJ Thunder) significantly slow down the generation of my world. It would make sense since the datapacks make the generation more complex, but I've compared it to the generation of other people and I feel like it takes longer than normal because I've seen people generate a JJ Thunder world in seconds. In my case (Terralith+Terratonic) it takes a bit longer and without problems, but JJ Thunder isn't even able to generate properly, it's extremely slow, generates gaps and throws errors. Summarizing everything a bit, I think everything works fine except for the speed at which the world is generated using datapacks and whether it's a bug or not and how I can fix/speed up the world generation. Postdata: It's nothing important, but I've noticed that when using bliss shaders and changing the field of view (either when running or using zoomify), some blocks like water and ice start to stutter while that fov change lasts. PC Specs: R7 5700X RTX 2070 Super 32GB DDR4 3200Mhz Sata SSD Samsung Evo 870 MSI B550 Tomahawk (You can see all the mods in the log)
7 Replies
Pochinkón
Pochinkón3mo ago
Log attached.
Miki_P98
Miki_P983mo ago
People on YouTube videos either generate their woleli before playing or they speed up the video during initial generation Only way to speed it up is CPU load in DH settings And performance mods from which the most important are those 3: - Noisium - Faster Random - Lithium
Pochinkón
Pochinkón3mo ago
I use all the performance mods that have been mentioned in this FAQ (since I've been reading for a while). I also use the "I paid for the whole CPU" option while generating the world. Regarding other people's videos, I know that a pre-generated world runs much better, but I can't even generate with JJ Thunder. I get a message similar to "features error timed out" (I don't remember exactly but it's similar).
Miki_P98
Miki_P983mo ago
/chunky
YAGPDB.xyz
YAGPDB.xyz3mo ago
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.
Miki_P98
Miki_P983mo ago
You can increase the timeout time limit by default it timeouts after a single chunk takes more then 60s to generate
Pochinkón
Pochinkón3mo ago
i usually use 240s but i will increase for testing
Want results from more Discord servers?
Add your server