lod building very slow

[System] [CHAT] Distant Horizons overloaded, too many chunks queued for updating. \nThis may result in holes in your LODs. \nPlease move through the world slower, decrease your vanilla render distance, slow down your world pre-generator, or increase the Distant Horizons' CPU load config. \nMax queue count [2500] ([500] per thread). maxed the cpu usage. What can I do, I tried a lot of things but I always get this +fps (massively drop) only when I play modded MC
No description
No description
No description
Solution:
Also alongside increased RAM allocation, you might want to use one of this GC flag sets: https://discord.com/channels/881614130614767666/1304910897658986570/1305234534492803165
Jump to solution
24 Replies
Miki_P98
Miki_P983d ago
/slowgen
YAGPDB.xyz
YAGPDB.xyz3d ago
World generation in general is quite slow, if you want to speed it up: Install Noisium and Lithium, these mods can improve generation speed by a couple percent. Make sure to remove the C2ME mod as it significantly slows down DH chunk generation by up to 35%. Increase CPU Load in Distant Horizons settings for faster generation, but you will experience more lag spikes and stuttering due to heavier workload on CPU. To see if Distant Generator is really working or not: 1) Check CPU usage while in-game, using Aggressive settings of CPU Load. If CPU usage's hovering around 80-100%, the LoDs are generating in the background. 2) Go to DH settings > Advanced Options > Debug > Wireframe, set Enable Debug Wireframe Rendering and Show World Gen Queue to True. Enabling both settings will show you the visualization of world gen tasks queued and working on the map (blue boxes for queued tasks, red boxes for working tasks)
Miki_P98
Miki_P983d ago
If you switch to nightly you can get a boost from C2ME instead of the slowdown How much RAM did you allocate to MC? What are your JVM/GC flags? What is your DH CPU load? What worldgen mods or datapack do you use? (Including pure world height changes)
Furiousjp01
Furiousjp01OP2d ago
4gb I PAID FOR THE WHOLE CPU
Miki_P98
Miki_P982d ago
How many threads does your CPU have? 4GB seems a bit low for that setting If you have 16 GB in your PC, try allocating 8 to MC
Furiousjp01
Furiousjp01OP2d ago
8 threads and 32gb available
Miki_P98
Miki_P982d ago
Then try allocating to MC 8 or even 12 GB of RAM If the overloaded setting still shows up, decrease the CPU load setting by 1
Furiousjp01
Furiousjp01OP2d ago
No description
No description
Furiousjp01
Furiousjp01OP2d ago
No description
Furiousjp01
Furiousjp01OP2d ago
No description
Solution
Miki_P98
Miki_P982d ago
Also alongside increased RAM allocation, you might want to use one of this GC flag sets: https://discord.com/channels/881614130614767666/1304910897658986570/1305234534492803165
Furiousjp01
Furiousjp01OP2d ago
I put the arguement there?
No description
Furiousjp01
Furiousjp01OP2d ago
will test by disabling the chunk mods (except dimension stackin) and I'll tell you how it went error- changing arguement
Furiousjp01
Furiousjp01OP2d ago
lot better
No description
Furiousjp01
Furiousjp01OP2d ago
each valley is lag spike
Miki_P98
Miki_P982d ago
yes
Furiousjp01
Furiousjp01OP2d ago
enabled debug and wire frame 32 DH render distance but nothing's showing up
No description
Furiousjp01
Furiousjp01OP2d ago
somehow fixed it
Furiousjp01
Furiousjp01OP2d ago
No description
Furiousjp01
Furiousjp01OP2d ago
still performance issu: updating DH and installing lithium noisium
Furiousjp01
Furiousjp01OP2d ago
been standing here for an hour, thats what it gave me
No description
Miki_P98
Miki_P982d ago
It is at least working If all the performance mods did not help, and you don't have any more worldgen mods, datapacks or structure mods that slowdown the generation I don't think there is anything more you can do
Rio
Rio12h ago
the mod is really broken not suprising also the newer versions eat up cpu and dont load much
Furiousjp01
Furiousjp01OP10h ago
@Miki_P98 looking back at the LOD generation speed and at my cpu load(task manager) I think the generation is being turned on/off constantly, maybe the thread duration is to low? I can't seem to find the "duration" setting in the nightly build (2.3.0-b-dev)

Did you find this page helpful?