Problems with DH 2.3 Server side
Hey i just recently wanted to help with the testing of the nightly version of DH 2.3 Server side, i found series of problems with it. First of all, as #help-me server-side thread i tried to access config via
/dh config but the command is not registered on any way on the server (see first pics, even on the server console itself doesnt exist) . Second a more relevant is that LOD generation won't start on any of the configs for server side, the f3 screen just debugs as task maybe are getting created (see image #4), idk if maybe im doing something wrong, i tried to wipeout the lod dbs both on client and server side without results
5 Replies
/logs
You should send your
latest.log file to provide additional useful information.
Logs are usually located in the .minecraft/logs directory.
On Windows: %appdata%\.minecraft\logs
On Linux: ~/.minecraft/logs
On Mac: ~/Library/Application Support/minecraft/logs
Please upload the file to mclo.gs instead of sending the raw file. This makes reading the contents of the file a lot easier and improves the chances of you getting the help needed.
After uploading the file, click on Save and send the link.Though the server side logs might be more useful then the client side ones
So send them first
Client Latest.log: https://mclo.gs/vClnFNl
Server Latest.log: https://mclo.gs/UvrDiin
Server Debug.log: https://mclo.gs/Z0cWP7p
Aditional info on the issues, the servers seems to not launch new generation jobs after on login sync request has been made, i tried with all diferent modes of native DH Generation like Surface Features and internal server, and with chunky i tried pre existing only, nothing worked except for the first few lods of the nearby chunks of the first join to server, no matter the render distance or config
I enabled briefly the network transit logs (Using Log config of client DH) on another test, and the server seems to send the request just fine, and client is accepting it, but no matter what i try the server never triggers new lod generation tasks, only send updates on existing ones as explained above