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?
63 Replies
can you try with DH 2.2.1?
I will downgrade and check. I was avoiding that since I need to run on a server and other people reported no issue with the nightly.
yea this is the first time ive seen this issue with the nightly
i am trying with the older version now and there doesnt seem to be an issue
i have been hunting this issue for 4 days now lmao
any recommendations on what i can try to fix this on the nightly?
i will keep flying around on the older one to make sure it doesnt happen at all
see if there's anything in the logs
/logsstored
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.probably not, but just in case
on client or server?
client
its a giant spam of this:
[19:15:18] [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.'
I have 1 more idea, try latest Embeddium with Iris 1.7.5 and without Indium
well thats certainly not good. not sure what it means though
this is from the logs from the nightly run btw, with flickering
on it
do you have an apple pc?
nah
good
7950x3d + 4090
and i recently DDU removed nvidia drivers and reinstalled
just to be sure that wasnt the problem
nope, flickering is back, with this setup btw
and the log spam is back
[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.'
Hmm
Maybe call a priest? I'm out of ideas...
Your PC is cursed
Just 2 more things, this is a new world on the barebones instance?
And does this happen without shaders?
yup i literally made an instance for this, and no it doesnt happen without shaders
whats the command to summon a priest xD
what two shaders did you try?
photon, bliss and rethinking voxels
like 4 different versions of bliss alone
all have this issue
full log corresponding to the video the the OP: https://mclo.gs/eN9hHU4
and it works fine with just DH?
/summon villager ~ ~ ~ {VillagerData:{profession:cleric}} xDwithout shaders yes but let me test a little more to make sure
its perfect without shaders, still getting the OpenGL error spam in logs though
hhmm so maybe that isnt related?
someone smarter will have to look at this
i dunno, its too generic for me to make heads or tails of what is up with it
wish it would log the texture name at least
did not realize my post would be somewhat of a duplicate of this
for all I can tell this is easily replicated using a clean instance
just saw your post, do you have the issue of flickering LODs as well?
I did not pay attention to this but gimme just a minute to check it out
load a big are over a large water body, fly up high enough that everything below is being rendered as an LOD
my focus was solely on this
at least it means my PC isn't cursed
Can't replicate the LOD issue however
which shaders?
none, basic instance of DH nothing else
issue is with shaders
can you try with bliss/photon
use this: https://github.com/WATERFORCE99/Bliss-Shader-BSPT/archive/refs/heads/main.zip
whats that
current latest in-dev build
its just a version of bliss, it will happen with any of them but its what i used in the video
trying to limit variables
seems like its a fork of bliss
not a version of bliss
no
oh wait yeah
I just noticed the user
its the latest release in the thread on shaderlabs since Xonk isnt working on it, but you can use the mainline if you want
the issue is on both
latest from official github source has a bunch on bugs (ex: clouds don't change based on weather)
ok it does seem to glitch here and there even with embeddium + monocle + iris 1.8.6
definitely not as frequent as your video however
ngl, makes me happy to know i am not the only one
nevermind on that
i think i have settings cranked up high so maybe that increased the odds?
wait for the whole thing to load
xD
its pretty random, it wont happen for 30 seconds, followed* by 5 seconds of a horror show
ehh all I did was turn it down to a 64 chunk radius
luckily fixed by reloading the shader pack
reload shaders
press R
yup changing stuff like that causes visual issues
either way this happens which I also mentioned https://discord.com/channels/881614130614767666/1349036232969289831
yep ive got the same thing
already getting quite large within less than 10 minutes
@Miki_P98 @Puhpine (GMT +2) what do we do next? will some dev take a look this this thread when they have time or should i open another one in bug-reports?
The first option, probably
I mean they will eventually see this, but I guess a nice summary of what is known and confirmed in #bug-report would be nice
i was literally waiting for DH to add server side LOD support for like an year now and i came back to modded minecraft specifically for this :\
i'll do that, just for more clarity