Server stops sending LODs

My problem is the same or similar to help-meServer sending LODs slowly/with complete interruptions

I have the latest neoforge DH on both client and server. Both client and server have distant generation enabled. I ran dh pregen start overworld 0 0 50 to create a small world, then joined the server and immediately tp'd to 0,0. (I did a radius of 50 for this test, but I had the same results with much larger pregent tests as well). Initially, it works well - lods are clearly being sent and correctly loading to a radius of 500+ blocks. So I generate more terrain (say 100 chunks) - at some point in this process lods stop getting sent. If I teleport my player to any random point within the generated radius, zero lods will get sent no matter how long I wait (I've let it AFK for hours with no success). Server and client restarts have no effect.

Result: Server-side lods stop getting sent to clients. Is there any kind of handshake or smoking gun I can look for in the logs to determine what's not working?

I've attached the client config and the server config. I raised the rate limits on LOD requests significantly to see if that was the bottleneck (the server is on the same LAN as me), but it made no difference.

DH is working fine on the client, if I fly around local lods will be generated and used as expected, even when joining a server.

Possible problems: Pregen throws a lot of errors. I'm not sure how many of them are critical or routine, but errors like [STDERR/]: [java.lang.ThreadGroup:uncaughtException:698]: java.util.concurrent.RejectedExecutionException: Task com.seibel.distanthorizons.core.util.threading.PriorityTaskPicker$TrackedRunnable@48c26a28 rejected from com.seibel.distanthorizons.core.util.threading.RateLimitedThreadPoolExecutor@3db6784f[Running, pool size = 6, active threads = 6, queued tasks = 6, completed tasks = 393] constantly.

I have a normal render distance of 12, and a DH render distance of 256.
Was this page helpful?