New clients can't see server-pregenerated LODs on connect
Trying to figure out why newly connected clients can't see further than the vanilla render distance.
Fresh world dir on the server - the only server config change i made to DistantHorizons is to set
INTERNAL_SERVER, then run the dh pregen command to generate a 500 radius area around spawn before any clients connect. (used rcon, checked with status command, it completed fine before i connected a client).
Then I connect with my game using DH default client settings, and I expect to immediately be able to see further than the vanilla view-distance of 15, but i can't. I was expecting the pregenerated LODs to be sent from server to client up to the lodChunkRenderDistanceRadius of 256.
Afaik the default DH settings should do that? or am I misunderstanding something?
If i fly around to distant chunks and back, i can then see further than the vanilla distance as along as it's chunks i've already visited.
Minecraft server 1.21.10 with Fabric Loader 0.18.1. Latest c2me, distanthorizons 2.3.7-b-dev, a few other perf mods etc but nothing that should interfere.
Thanks!
server's latest.log: nothing looks relevant. Pregen finished before i connected:
Client log: https://mclo.gs/wTvyOxR1 Reply
I left the game running and it gradually populated lods in the distance. looks like it was just maxed out on the 500KiB/sec bandwidth limit. I have increased that and given it a bit of time to load in, and all good.
What's the best way to check how many LODs the client is waiting to receive within the configured DH view distance?
Is there a way to ship the server pregenerated chunks/lods to clients before they start their games, to avoid the initial LOD delivery delay? I want my players to see into the distance around spawn immediately on join if possible.