Distant Horizons doesn't load any LODs on server
Running on [1.20.1] with DH [2.3.2b] using Complimentary shaders.
While in singleplayer, everything loads as normal and as expected. On a dedicated server running it the client doesn't load any LODs whatsoever, even after explicitly generating them suing the pregeneration command. Embedded screenshot is with debug tool "Render all LODs with Wireframes" enabled.
Config file has been deleted and refreshed multiple times.
Logs from server + Modlist: https://mclo.gs/bI3FUXx
Solution:Jump to solution
Ok I think I figured out the issue?
There was a mod being used in order to pin the server as always available upon installing the modpack, but this server by default cannot have a name. The default configuration for DH is to save the location of LODs for a server in a folder based on the server name, but because it didn't have one it just didnt make the directory from what I can tell?
The issue was fixed after flushing everything out and reinstalling basically everything and not using the server browser mod that puts it at the top....
11 Replies
[Server thread/ERROR] [ConfigFileHandling, distanthorizons/]: Unable to convert config value [{}] from [class java.lang.String] to [class java.util.HashMap] for config [mapTest], the default config value will be used instead [{}]. Make sure a converter is defined in [ConfigTypeConverters].
My bad i didnt realize how bloated the log was, this is the main issue though from what I can tell.Can you try deleting the DH config file?
!config
To edit the config, press the button next to the FOV slider to edit the config.
The config file found in .minecraft/config/DistantHorizons.toml
i have, didnt change anything
It could have become corrupted
yeah i mean i figured, i did that first and it didnt change anything
i tried it 3-4 times
here's the last config file, still didnt work on this one and this is after having deleted it several times. Is there something borked i dont see?
also this from the embedded screenshot
Solution
Ok I think I figured out the issue?
There was a mod being used in order to pin the server as always available upon installing the modpack, but this server by default cannot have a name. The default configuration for DH is to save the location of LODs for a server in a folder based on the server name, but because it didn't have one it just didnt make the directory from what I can tell?
The issue was fixed after flushing everything out and reinstalling basically everything and not using the server browser mod that puts it at the top.
interesting fix
its a really dumb problem that's entirely caused by me misusing one mod and what just so happens to be standard config in DH
i apologize for the timewaste