Beacons not rendering in LODs.
I've read through as many messages here as I can about beacons, and it seems like most people want LESS beacon vision. I can't see them at all!
Multiplayer 1.21.4 Paper server
Neoforge-21.4.136
DH 0.9.0 / 2.3.2-b
Complimentary Unbound 5.1.1, but i've replicated this in BSL and without shaders.
DH is working fine otherwise, rendering is on, distant generation is off, in generic object rendering I have enable beacon generation: TRUE with default render height 6000. I made the change in the config file (set to true and removed note tag)
I've included an example of beacon visible at vanilla render distance, and beacon invisible (or culled?) with one step backwards.
This is driving me crazy, can somebody tell me what I'm doing wrong?
13 Replies
Any other mods installed?
Neoforge mods just Sodium and lithium. Is it possible these could be removing the DH render?
Server plugins are dynmap and stuff like chest sort, but nothing visual.
Does it work with just DH installed?
Does it work with default config?
Yes. I just set up a fresh curseforge instance with only DH, and beacons are visable at distance. I suppose this rules out a hardware issue or something.
I added stuff back one at a time, and it looks like Sodium is breaking the beacons for me.
I've ruled out as many sodium options as I can think of. Fog culling, entity culling, I don't know what it could be. I also switched between fast fancy and fabulous with no change, all with shaders turned off. The beacon blinks in and out right around the vanilla render distance.
I'll try this. Is there a better way to revert to default settings than deleting the config file?
You can rename the config file so that you can revert it later
That is it, no need for more
Update:
Fresh neoforge install works with fresh DH, fresh Sodium. However, in my preferred install, beacons are broken even when only DH and Sodium are the only active mods This suggests that something about my DH settings or my Sodium settings have screwed up beacon rendering.
To determine which mod is the culprit, I turned off Sodium on my preferred install, and the beacon problem persists. This means my DH settings are bad.
I know beacon rendering is not a problem with the server configuration, because "fresh install" was tested on the same multiplayer server and worked.
All signs pointing to DH client mod settings as @Miki_P98 suggested.
Have you deleted the config file or not yet?
Tried removing DH in curseforge, booting MC, and then reinstalling DH to reset settings, but I don't think it worked. I'm a little confused how to revert the DH settings. Is this something that is done client side or through the server settings @Puhpine (UTC +2)
like are we talking about the config file on the server plugin?
The config file on the client, which can be found in .minecraft/config/distanthorizons.toml
Excellent, I appended the name with "_brokenversion" and am booting now with fingers crossed
I renamed my .toml and DH made a new copy, presumably with default settings, but the issue persists. Something was certainly changed because server message "Received DH config" was produced. Unfortunate.
Is this without sodium?
Correct. Sodium not active.
Fresh neoforge modpack with DH and Sodium = working beacons at distance
Preferred neoforge modpack with only DH active, using fresh DH configuration = broken beacons at distance.
At this point I've done so much I kind of just want to set up a new instance from scratch until something breaks again. but it's driving me crazy not to be able to work this thing backwards. :aPES_GaCrazy: