Possible Texture Atlas Flickering Issue
For a few weeks now I have tried and failed to find the cause of a peculiar issue with shaders, strange groups of mods, and utterly random blocks. This group of mods causes blocks like stone to flicker at its edges when the camera moves, as if the model has a gap in it. I have tested with Complementary V4, Complementary Reimagined, and BSL, all have the same problem. The mods I'm using (Fabric 0.14.19 on 1.19.2):
Bclib-2.1.6, BetterEnd-2.1.4, Charm-4.4.4, Continuity-2.0.2, Ecologics-2.1.11, Fabric API-0.76.0+1.19.2, From The Fog-1.8.1, Immersive Weathering-1.19.2-1.2.9, Indium-1.0.9, LambdaBetterGrass-1.3.0+1.19, Moonlight-1.19.2-2.2.31[Library for Immersive Weathering], WilderWild-2.0.
Iris 1.6.2 and Sodium 0.4.4
Removing any of these mods can cause the affected blocks to inexplicably change. The full mod list causes at least Stone and Moss to flicker, removing a mod can cause anything from Andesite and Calcite to Grass Blocks and Sand to flicker. I asked on the Complementary Discord but no solution they provided worked. The only thing I can think of that could possibly cause this is maybe a glitch with Sodium, Indium, Continuity or LambdaBetterGrass. This is the farthest I could investigate with a glitch as erratic as this one.
Sorry for the long report, I hope I explained everything in detail. I also have a recording of this issue occurring (recording uses Comp V4 with Compatibility Mode on and Anti-Aliasing off to better show the issue):
![No description](https://cdn.answeroverflow.com/1103075266965819442/2023-05-01_15.31.51.png)
25 Replies
Do you want to upload this file to mclo.gs?
mclo.gs is a website that allows users to share minecraft logs through public posts.
It's easier for the mobile users to view the file on mclo.gs, do you want it to be uploaded?
Log Uploading is deprecated in LilyBot. It has been implemented in Allium instead. It will be removed in 4.9.0
Uploaded by DeerreeD#7702
After some more testing, I've discovered that--not only some blocks flicker without shaders--but that they flicker without any mods loaded, not even Fabric API. Some mods/shaders just make this more visible and/or change which blocks are affected.
This is either the fault of Nvidia, Fabric itself, or Minecraft? I've already tried updating drivers and restoring default settings in Nvidia Control Panel, but it doesn't affect anything. Is there anything I missed? I really want to fix this pain once and for all.
After even more testing, it still flickers in vanilla Minecraft...
After many more days of trying to fix this in vain, here's what I know about this issue: The vanilla bug appears to be https://bugs.mojang.com/browse/MC-175333 and also seems to happen on AMD GPUs. Shaders make the holes in blocks more visible. The block flicker is primarily affected by content mods and resource packs, which makes me think it might have something to do with the texture atlas. And the fabric mod "Model Gap Fix" does not help and sometimes even makes it worse.
So far I have tried: Resetting Nvidia Control Panel settings, turning Anisotropic filtering and Anti-aliasing off, updating graphics drivers, changing mipmap levels, changing Minecraft version, changing Java executable version, doing OS updates (using Windows 10) and doing a clean uninstall/reinstall of Minecraft and the default/legacy launcher, nothing fixed it. If I can't fix or mitigate this issue then I might not be able to play Minecraft on this PC at all anymore.
u mean like that white pixel?
![No description](https://cdn.answeroverflow.com/1106755056063234068/image.png)
can u send the seed for the world where u saw it happening?
so i can try to replicate from the exact location
Seed is -863979546414921381, coordinates -15 78 73
also what fov?
default
hm have you tried "Display Driver Uninstaller"?
No, but I have tried multiple clean installations of different driver versions
Well using display driver uninstaller (DDU) to fully uninstall could help
I'll try that then
Did it do anything?
Haven't downloaded it yet, I'll try it later
u could also use HWInfo64 to check VRAM and GPU temps
maybe one of those is overheating or somethin idk
why do they need to remove the display drivers