Graphics Errors with newest (Jan 30, 2025) Nvidia Drivers and Vulkan in gzDoom 4.14.0

[DarkkOne]

With gzDoom 4.14.0 (as well as 4.11.something, I updated to see if a newer version resolved the issue) and Vulkan rendering (it's fine with OpenGL), the graphics are corrupted when using "Nearest" scaling for textures (any mipmap choice has the same results). As far as I can tell, it doesn't affect walls, floors, items, etc, just like... menu text, menu images (including the default Doom menu text), status bar, and things like that. Though I'm not sure that it's conclusive that it doesn't affect other things.

In the attached image, you can see the errors both in the menu text and the large background image. I don't know how to describe the issue, it looks like occasionally two adjacent pixels are swapped, but I feel it's very apparent in the attached image.

GZdoom rendering error small.png

[dpJudas]

Try delete the shader cache (pipelinecache.zdpc) in %localappdata%\zdoom\cache
Please let us know if that helps.

It could also be a driver bug. Keep an eye out for another release from NVIDIA. They sometimes release a couple of driver versions in short succession if they accidentally break something.

[DarkkOne]

Shader cache didn't help. Decided to launch other Vulkan games, particularly 2D ones, and, interestingly, "Doom + Doom 2" on Steam has the issue (though all games I tried prior to that don't). So apparently NVidia just hates classic Doom. Guess I'll hope for a driver update to happen soon, though it seems rare enough that I imagine I'm going to be waiting for the next major one.

[DarkkOne]

Further Update: I'm on a laptop. Some driver update (either Nvidia or perhaps a manufacturer one) reset from "dGpu only" to "Hybrid Mode." Upon restoring discrete gpu mode, the issue seems to have vanish, so I suspect it wasn't even the Nvidia drivers, but rather just the Intel GPU not liking Vulkan.

[Rachael]

Any time there is a graphical glitch related to drivers, this is almost immediately not a GZDoom bug. The reason for this is because drivers have a lot of things that are completely beyond programmers' control. If this is related to the Intel chipset, it will be mostly up to Intel to fix their drivers - they are already known to have texture sampler issues which are completely inconsistent with the way both AMD and NVidia work.

[undeadgamer9609]

I have the same issue too and i don't have a intel chipset i have a amd chipset so this may be a nvidia issue?

[undeadgamer9609]

Ok so i just figured out how to fix this hopefully go into display- Vulkan options (experimental)- and turn on high dynamic range that seemed to fix it for me.

[ArcturusDeluxe]

I'm getting the issue too on desktop with an RTX 3080 and Intel CPU/chipset (though the on-board graphics are disabled). Only seems to affect Vulkan, OpenGL still looks fine as a fallback.

[DarkkOne]

So it happens on AMD, Intel and NVidia GPUs?

[mr_daemon]

I'm also having this exact thing on Desktop, Windows 11 24H2, Nvidia 4090 with 572.16 drivers, Vulkan renderer. OpenGL does work fine.

[Rachael]

Please post your .ini files. Feel free to edit out personal data (i.e. home folder location)

When you do, please label your post to indicate whether you are affected by this glitch or not.

[mr_daemon]

Of course -- affected, ini file available here:

https://gist.github.com/mrdaemon/19ce27 ... 80c019b781

[vladkosi]

It's a an NVIDIA driver bug.

[GODOT/Red Dead Redemption 2/ImGui] Some Vulkan apps may display minor 2D pixel offset atifacts [5086373]

https://github.com/godotengine/godot/issues/102219