Confirm Clients are receiving Chunk LOD's from server?
Recently did a pre-gen on a MP server and I'm trying to figure out if one the server is sending the LOD data from the server to the clients and two if there's a way to speed up the rate the clients get the LOD data? I've already allocated more bandwidth (100000) but are there other settings I should be looking at both client and server side?
21 Replies
Are you using the plug in or the mod server side?
The mod is server side as well as installed with the clients as well. I should have mentioned it's Fabric .
You didn't need to because you tagged the post
if the client sees new chunks showing up without moving, then its recieving new LODs
i think there is a bandwith limit on the client as well, but im not 100% sure of that.
It seems to, but the rate seems slow. In the F3 menu there's a line that goes something to the affect of "CLIENT_WORLD_ONLY", is that a cause for concern?
no you can ignore that
how did you do the pregen? did you pregen with DH or with another mod?
Did the pregen with DH, and it definitely finished. Did 2048 chunks.
okay thats good
and did you look at the bandwith limit on the client?
Yes, I found the setting in the client on the "server" tab but I don't know if that would impact the client directly or if it only impacts if the client is also acting as the server, if that makes sense?
fair point. im not sure either unfortunately
but its worth a try i'd say
I tweaked it to zero on the client (just because the rate is already enforced server side) and not really a difference. it looks like the lines In the F3 that are firing off are the "WorldGen/Import Tasks" and and "Requests"
okay then it is indeed working
I guess it's just a matter of time before everything gets sent to the client then? I. Just wondering if there's some sort of bottle neck somewhere. This is a little bit off thread but which numbers should match with each other? Like request distance comparing to pregen size, etc?
the config setting max request distance is that in chunks or blocks?
it could be as simple as just not having that fast of a connection to the server
chunks
The setup is roughly that the server machine and the client are on the same network, but different mahcines. I've seen the send bandwidth spike on the server to like 25Mbps, not even touching the 100Mbps limit imposed or the 1Gbps speed of the interconnected devices. The behavior being observed is that the Chunks stopped appearing approx 6KM away from the client standing sitll.
/slowgen
World generation in general is quite slow, if you want to speed it up:
Install Noisium, Lithium and C2ME(DH 2.3.0+). These mods can improve generation speed by a bit, but it will still not be fast.
Increase
CPU Load in Distant Horizons settings for faster generation, but you will experience more lag spikes and stuttering due to heavier workload on CPU.
To see if Distant Generator is really working or not:
1) Check CPU usage while in-game, using Aggressive settings of CPU Load. If CPU usage's hovering around 80-100%, the LoDs are generating in the background.
2) Go to DH settings > Advanced Options > Debug > Wireframe, set Enable Debug Wireframe Rendering and Show World Gen Queue to True.
Enabling both settings will show you the visualization of world gen tasks queued and working on the map (blue boxes for queued tasks, red boxes for working tasks)try the wireframe thingy from the second part
see if any wireframes show up past that 6km
It seems that there is nothing past that 6KM or so
This might be a stupid quesiton, will the client have to have gone there before for DH to send the LoDs? Like it won't send LoDs to chunks the client hasn't been?
If the server has DH, it will try to send, or first generate then send, the LOD for every client sent request with no limitations
Unless the server side config prevents this from happening
To add on more to the environment, the server was pre generated with 2048 chunks worth of LOD'S, no one has really been outside of that distance, if even coming close to that distance. All the server config is default except for bandwidth which was increased as well as number of threads to use.
Looks like things seem to be working properly, just had to give it a bit of time. It also generated really quickly for the client as they moved towards the unrendered bits. I'll go ahead and mark as solved, thanks for everyone's help!