Chunk generation error:

I'm pretty new to this so feel free to give me tips. I get the following error after running Chunky in SP without DH in the mods, after chunky was done I re-added DH 2.3. (as it's recommended in /chunky)
[17:34:07] [CompletableFutureDelayScheduler/WARN]: Unable to get chunk at pos [[-41, -45]] after [180] milliseconds.
java.util.concurrent.TimeoutException: null
at java.util.concurrent.CompletableFuture$Timeout.run(CompletableFuture.java:2874) ~[?:?]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539) ~[?:?]
at java.util.concurrent.FutureTask.run(FutureTask.java:264) ~[?:?]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304) ~[?:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) ~[?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) ~[?:?]
at java.lang.Thread.run(Thread.java:833) ~[?:?]
[17:34:07] [CompletableFutureDelayScheduler/WARN]: Unable to get chunk at pos [[-41, -45]] after [180] milliseconds.
java.util.concurrent.TimeoutException: null
at java.util.concurrent.CompletableFuture$Timeout.run(CompletableFuture.java:2874) ~[?:?]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539) ~[?:?]
at java.util.concurrent.FutureTask.run(FutureTask.java:264) ~[?:?]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304) ~[?:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) ~[?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) ~[?:?]
at java.lang.Thread.run(Thread.java:833) ~[?:?]
I got this error a bunch of time for likely all chunks generated by chunky.
19 Replies
YAGPDB.xyz
YAGPDB.xyz•2w ago
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.
Miki_P98
Miki_P98•2w ago
Remove DH when chunky is running Add DH back when chunky finishes
Rackneh
RacknehOP•2w ago
Like I said above that's what I did! Otherwise I wouldn't be posting here hahaha
Miki_P98
Miki_P98•2w ago
Sorry Too tired
Rackneh
RacknehOP•2w ago
No worries lmao I can also imagine it becoming tiring when people post the same stuff without looking at basic stuff
Miki_P98
Miki_P98•2w ago
If this is what I think this is you can just ignore this or increase the timeout limit in DH settings
Rackneh
RacknehOP•2w ago
When this happened the game wouldn't go to day when I ran that command and after a restart it has a massive error when I try to load chunks The chunky generated chunks are also not taken by DH at all But I'm going to start a new SP world and redo the test
Miki_P98
Miki_P98•2w ago
I think my knowerlage is too low to help you with this one Seems like the whole internal server is lagging
Rackneh
RacknehOP•2w ago
Atm in this world I'm flying inside the LOD
No description
Miki_P98
Miki_P98•2w ago
What is your CPU usage (like in task megeger)?
Rackneh
RacknehOP•2w ago
Yeahh I'm redoing the test
Miki_P98
Miki_P98•2w ago
Try reducing the CPU load preset Do you have any other mods?
Rackneh
RacknehOP•2w ago
I tried setting the CPU load setting to minimal impact but the game is running fine so it's not being bottlenecked
Miki_P98
Miki_P98•2w ago
It does not seem to be running fine
Rackneh
RacknehOP•2w ago
Yeahh gimme a moment to redo the test See if I made any mistakes
Miki_P98
Miki_P98•2w ago
Sometimes the internal server dies, but you as the player can still play "normally" in it normally as, new vanilla chunks won't load, blocks don't drop and mobs don't move, but your fps is good and the game is not stuttering Never seen it caused by neither DH nor Chunky though
Rackneh
RacknehOP•2w ago
Okay so I got no errors on the second try around The only difference is that I removed chunky when I added DH back in Oh nope, it ran for a while and generated quite a bit of the 750 radius I generated But I still get these errors
[18:30:46] [CompletableFutureDelayScheduler/WARN]:Unable to get chunk at pos [[10, -36]] after [180] milliseconds.java.util.concurrent.TimeoutException: null
at java.util.concurrent.CompletableFuture$Timeout.run(CompletableFuture.java:2874) ~[?:?]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539) ~[?:?]
at java.util.concurrent.FutureTask.run(FutureTask.java:264) ~[?:?]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304) ~[?:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) ~[?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) ~[?:?]
at java.lang.Thread.run(Thread.java:833) ~[?:?]
[18:30:46] [CompletableFutureDelayScheduler/WARN]:Unable to get chunk at pos [[10, -36]] after [180] milliseconds.java.util.concurrent.TimeoutException: null
at java.util.concurrent.CompletableFuture$Timeout.run(CompletableFuture.java:2874) ~[?:?]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539) ~[?:?]
at java.util.concurrent.FutureTask.run(FutureTask.java:264) ~[?:?]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304) ~[?:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) ~[?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) ~[?:?]
at java.lang.Thread.run(Thread.java:833) ~[?:?]
Miki_P98
Miki_P98•2w ago
Do you have any other mods?
Rackneh
RacknehOP•2w ago
Yeah but we did a test on the server of the modpack and it's running fine afaik👌 Probably something with the modpack on SP The chunk loading isn't fast but it's still leagues ahead of playing without DH 2.3
Want results from more Discord servers?
Add your server