LODs being sent by server are not being loaded
I'm in a 1.21.1 lightly modded server (mostly trying out DH pregen with some optimization mods and some terrain generation mods like tectonic) and after letting it pregen 1000 chunks around 0 0, (no issues there, completed without errors) I hopped on the server to check it out but instead of the server sending the pregen LODs to the client on request for some reason the client started generating its own LODs.
This however might be me misunderstanding how the mod works so I apologize in advance. I'll share some screenshots under this see if someone can help me with this.
Some other notable information is:
-Server view distance in server.properties is changed to 256
-DH loading server wise is changed to INTERNAL_SERVER
-Recommended mods like C2ME and fasterrandom were used for faster rendering
-Mod is updated to latest stable release (2.3.2-b-1.21.1)
By the way screenshots were taken after not moving for about 10 minutes while I was waiting for terrain to load, which it didn't
47 Replies
The f3 menu is saying that its importing with around 12 chunks/s, which is not very fast
:/ Any idea why that could happen
Do you have distant generation enabled on the client?
Yeah
You can try increasing the thread preset on the server or max bandwidth/sync request rate limit
You can access those with the dh config command
I disabled limit
On bandwidth I mean
Not threads lmao
Could that be an issue you think?
Whats the thread preset on?
Balanced
Try increasing the generation and sync rate limit
My server is now crashing on me joining :0
What are default values for those?
20 for generation and 50 for sync
Btw if you run a config command without any arguments it will tell you the current value
Oh thank you
But the main problem now is that server crashes on me joining lol
Weird
How much ram do you have allocated to it?
8 gb
But I've run DH on other servers and never had this issue happen
Is there a crashlog
Yeah, it's launching a thread watchog error
Watchdog is a thing in mc that stops the server if a tick took too long to process
I'm going to edit the post for more accurate help request
Set the max-tick-time to -1 in the server.properties
What will that do?
Disable watchdog
Fair
So it doesn't stop your server while you try join
Alr I'm relaunching the server now
It lets me join, it crashes after
Log?
Does it happen with just dh?
What the server crashing? Yes
Server is now lagging behind again and it's going to crash
DH is now launching a Insufficient memory detected but I've already upped the ram to 12GB
DH CPU preset is balanced and DH quality is set to 2
may I ask why you set the server view distance in the server.properties file to 256?
I think that seems to be the problem
default is 10 I think, may be wrong though and it is 12
The server side limit in
server.properties is 32 anyway no matter what you put there, unless one of the mods is extending it, but then the server performance will be terrible as this is very high vanilla RD, 32 is already quite performance intensive on a serverI will try changing it when I get back home
I completely missed that line lol
It should be 12 or something like that
Alright that fixed problem two thx guys
However first issue persists
LODs are not loading
you haven't changed the request rate limit
I did, nothing changed then reversed it
I'm going to give up on this for now for a little bit since I'll be away from my computer anyways
I seem to be having the same/similar issue on my side. I'm on 1.21.1 fabric. At first, my client only sees roughly the server's default render distance and never loads past that. Relogging after a bit seems to let the server send me a few more LODs than before, but not much more. My f3 doesn't seem to be showing much of anything happening either. Going back to 2.3.0 on both server and client fixes it for me.
I'm using DH in a server; and it seems to be switching to LODs after 4 ish(?) chunks rather than the default 10; is there a way to change that?
maybe even less than 4; i'm not entirely sure how the "switch to seeing LODs" is determined so
based on in-game render distance, may also be a setting under dh settings tho
/overdraw
Q: There are holes at the edge of vanilla Render Distance, especially during movement
A: This is caused by either vanilla terrain not loading in fast enough, or shader's incorrect overdraw prevention implementation or configuration (if you use one)
Some world gen speed improvement can be found when adding these three mods, but the affect will be minor:
- Noisium
- Faster Random
- C2ME (DH 2.3.0+)
The easiest fix is to move slower and/or ignore it. This hole is most visible while moving over not generated (by vanilla) terrain. Moving over that terrain every subsequent time may not create the hole. And moving slower will give MC more time to load the chunks as you go.
If none of that helped, you can also tune the overdraw prevention, look at the third section to know how.
Q: There are low quality full blocks behind and around non-full block, e.g. fences or ladders
A: This is intended behavior, to prevent holes in the world while you move, DH will overlap with some part of the vanilla terrain.
How much of the terrain is covered is determined by the overdraw prevention:
1.0 will mean DH LODs start where vanilla chunks end.
0.1 will mean that DH render very close to the players position.
0.0 sets it on auto mode.
To fix this, you can either:
Increase your vanilla RD, which will move the DH LODs further from you.
Tune the Overdraw Prevention setting, see the next section to know how.
Q: Where do I edit the overdraw prevention setting?
A: Overdraw prevention setting can be edited inside the DH config under:
Advanced > Graphics > Quality
BUT: if you use shaders, they will influence overdraw prevention. The effectiveness of overdraw prevention depends on the shader’s internal settings, which may or may not be adjustable. However, the shader’s overdraw prevention will always operate within the limits set by DH’s overdraw prevention. To avoid conflicts, ensure that DH’s overdraw prevention is not set too high.
Section 2
ah
thank you