Completely black screen in the nether with embeddium (1.16.5)
When in the nether the screen goes completely black, even the gui. It doesn't crash, you can still move around and hear things but there are no visuals at all. If you manage to blindly use the menu to quit the world the screen remains black until you restart.
I've tried disabling rendering, fog and almost every feature in DH but if it and embeddium are installed this will happen.
The only thing that fixes it is removing embeddium, but the modpack I'm playing is pretty unplayable without it.
...
Broken render
Solution:
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...
DH 2.3.0-b not rendering far - MC 1.21.4 FRESH INSTALL
Hello, I have experience in modding and did a fresh install of all required mods and DH running 1.21.4 on the latest version of DH but does not seem to be working as intended. Image contains all the mods installed, freshly installed with the latest versions. I also tried debug mode and it SEEMS to be working, showing wireframe in debug mode but the distance is not that far.
WHAT DO THE NUMBERS MEAN
just a generic question about the dh rendering. more specifically the LoD radius rendering option. because when i enter 64, it most definitely is NOT 64 chunks. so what is it?
newest version of DH have very close overlap and on things like trapdoors its very noticeable,
how does one change this now? there used to be a setting for this but i cant seem to find it on the latest version and its like, very apparent even close up, any help would be appreciated thank you !
Solution:
It's at
Advanced options > Graphics > Culling
Distant Horizons server plugin complete generation?
I'm running the DHS plugin (DHS-0-1.8.1_for_MC-1.21.4 or DHS-0.9.0-SNAPSHOT_for_MC-1.21.4) on my paper server. There are no console commands as far as I understand it but the console continually logs lines such as,
[DHS] Generation in progress: 21 processed, 1 in queue, 0.32 per second. about every minute. I assume this is related to pregeneration. The associated data.sqlite file is around 1.3GB and doesn't appear to be growing.
Is there any way to determine if/when the pregeneration (assuming that is what this is) will be complete? I currently have bluemap disabled and want to wait until it is safe to re-enable this once DHS is complete doing it's thing....
superDuperVanilla shaderpack - Bamboo and similar blocks have these issues
Hi, I'm not familiar with the technical terms used throughout this server but I don't think these are mentioned (i.e. not "intended") because I can only see this issue when using the shader superDuperVanilla. According to the shader creator, the issue lies with DH (but what do I know) so I just thought I'd check in here in case you can tell what's going on.
Would be very thankful for any help. I've tried changing settings back and forth in both DH and the shader, with no result.
I am using the latest DH release and this issue has been there since I started using night builds a few weeks ago, so I waited for this major release before asking for help....
Solution:
Hole at the edge of vanilla Render Distance, especially during movement:
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 two mods, but the affect will be minor:
- Noisium
...
LOD flicker in water
EDIT: Based on advice below, I have tested and can confirm this is not an issue in DH 2.2.1. The specific error from the client logs (full: https://mclo.gs/eN9hHU4) from the run in the video that appears with the latest version of DH (not sure if it is related or tangential to the flicker issue) is:
[20:16:59] [Render thread/INFO]: OpenGL debug message: id=1282, source=API, type=ERROR, severity=HIGH, message='GL_INVALID_OPERATION error generated. Texture name does not refer to a texture object generated by OpenGL.'
Original: I have been having issues with LOD's flickering on water, I decided to create a completely clean instance to try and isolate the problem. I installed only 5 mods. (prism config attached in image) All latest versions on fabric 1.20.1 then fired up a world and recorded over a large body of water. I used two different shaders, both recommended for use with DH to rule out a shader issue. https://www.youtube.com/watch?v=66bxWZieEU8 Any advice on what I can do further to try and debug this?...
