Server not sending LODs to clients
I’ve pre-generated using internal server to about 5000 in each direction. I was able to copy and paste the SQLite manually but other people and myself in testing can’t get any lods to be sent. Networking always reads 0 tasks and 0 done on the client. It does say server has full DH support in f3. I have a decent amount of performance mods and general server mods like servercore and ledger.
If you want other info or a photo of the f3 let me know, I’ve tried changing thread preset and all that but it doesn’t send any lods. I’ve also set network bandwidth limit to 0 (disabled).
14 Replies
This is every mod plus one library and yosbr

what i like to do to remove this process entirely for the first pregen is just copy the sqlite to the client's local lod storage because i also cant figure out how to speed it up
yeah this seems to be a problem for a lot of people
Where it completely stops sending them? Kinda defeats the whole purpose of it being server-side haha.
it doesn't completely stop sending its just really slow for me
for me it stopped when you didn't move around, once you do i recieved lods in small bursts
having the same issue
opened a new issue https://gitlab.com/distant-horizons-team/distant-horizons-server-plugin/-/issues/34
GitLab
Server not sending LODs to client. (#34) · Issues · Distant-Horiz...
Just installed the latest 0.9.0 onto my 1.21.4 PaperMC server. Plugin loads great, I run /dhs pregen survival 0 0 3000. Command completes-- but no LODs. The LODs...
Same issue here
It gets like a small area then stops
That area is much smaller then the one i put
if it's not working at all for you and the f3 networking section says 0 data is sent from the server, make sure all users have distant_horizons.worlds.* permission set to true
I just updated my server last night from DHS 0.7.0 to 0.9.0 and I also get no LODs sent to clients. I specifically gave my user the
distant_horizons.worlds.*
permission. I do use ViaVersions but that worked just fine with 0.7.0.
I did not do anything with the db for the upgrade, should I dump it and let it regenerate?
On the client side (2.3.2-b) I get this traceback:
Forgot to add, both server and client are 1.21.4
I may have found my issues (still testing)
distant_generation_enabled
is disabled at the top level and I was selectively enabling it for certain worlds. This does not appear to work anymore.Well, it kinda worked. The server is sending data to the client but it's all broken up. I tried issuing
/dhs pregen start world x y rad
and even though it said it was processing, running /dhs pregen status
shows nothing.
Same issue here
Exactly same

I removed my db file and let it start fresh. Everything works great and it's so beautiful now.
I'm using the nightly 0.10.0
