Graphical glitches all over the place in both game and editor - Nvidia drivers 572.16+ regression

[francogp]

Tested versions

• Tested on Godot 4.3, 4.4beta1 and 4.4beta2

System information

(Forward+) 4.3 - 4.4beta2, Windows 11, latest Nvidia drivers 572.16 - GeForce 30XX

Issue description

Since latest nvidia drivers update, texture filtering get a lot of glitches on godot only. My games and IDE included.
The GLITCHES moves (pixels start to jump on X coords) when you pan or move the camera.

Applying NEAREST filter shows the problem. It affect shaders too.
Applying LINEAR filter seems to HIDE the problem in lots of cases.

2025-01-30.20-33-12.mp4

Steps to reproduce

Just open an empty project with the default sprite can reproduce the problem

Minimal reproduction project (MRP)

Just open an empty project with the default sprite can reproduce the problem

[clayjohn]

Can you check your driver settings and ensure that there are is no contrast boosting / sharpening setting? I had a similar issue a few years ago (but with an AMD graphics card) and the problem turned out to be that AMD had quietly enabled contrast boost in all games and the Godot editor was accidentally included.

I think this would be the setting to turn off https://nvidia.custhelp.com/app/answers/detail/a_id/4920/~/how-to-enable-image-sharpening-in-the-nvidia-control-panel

[francogp]

Can you check your driver settings and ensure that there are is no contrast boosting / sharpening setting? I had a similar issue a few years ago (but with an AMD graphics card) and the problem turned out to be that AMD had quietly enabled contrast boost in all games and the Godot editor was accidentally included.

I think this would be the setting to turn off https://nvidia.custhelp.com/app/answers/detail/a_id/4920/~/how-to-enable-image-sharpening-in-the-nvidia-control-panel

It is not enabled, I tested also creating a profile for godot, and force disabling that feature, but the problem continues.
Also tested with my other PC with a Geforce 2080, but the problem cannot be reproduced there

[AeioMuch]

I can confirm the issue on latest Nvidia driver version 572.16 on Windows 10 and a 3060, only with Forward+ & Mobile rendering methods. Edit : Tested using DirectX12 and the issue is not there. So it's related to Vulkan.

The option @clayjohn mentionned is not available in the Nvidia control panel unless you enable integer scaling which is not enabled by default, and if you enable it, the option is disabled by default, so it is not that.

[clayjohn]

Could you look for other sharpening settings? I don't have an NVidia card so I don't know what is there, I just found that link with a quick Google search.

[francogp]

Could you look for other sharpening settings? I don't have an NVidia card so I don't know what is there, I just found that link with a quick Google search.

there's only one, and in my case is disabled in general, and in a particular profile for godot too (just in case).

[mrjustaguy]

Is Godot the only Vulkan thing you've got to test?

Given my experiences while i was on a 1050 ti Nvidia constantly breaks stuff at totally random, which has especially been the case for OpenGL (which at few points refused to run at all) and Vulkan.

If you roll back drivers, do the issues get resolved? If so it's better to just bug report to Nvidia, there's likely nothing we can do.

[AeioMuch]

Yes rolling back to 566.36 fix the issue of course.

Is Godot the only Vulkan thing you've got to test?

The issue is also present in Doom + Doom II using Vulkan, nothing else installed right now that use Vulkan, but I checked the issue council of Star Citizen and there's an issue with lots and lots of reports about this driver version and the same visual glitches when using Vulkan.

Yes it should be reported to Nvidia and they are probably already aware imo, but it's good to have this issue here in case others have the same problem, they can refer to it.

[francogp]

Is Godot the only Vulkan thing you've got to test?

Given my experiences while i was on a 1050 ti Nvidia constantly breaks stuff at totally random, which has especially been the case for OpenGL (which at few points refused to run at all) and Vulkan.

If you roll back drivers, do the issues get resolved? If so it's better to just bug report to Nvidia, there's likely nothing we can do.

I already did the report to nvidia, and give a reference to this thread.

[Conz3D]

Yep, can confirm, that there is a massive bug in the lates nvidia (studio) drivers. Found this thread on discord.
I have glitches with my 3060 in the editor and in my app. (Win10)

In bug01 you can see the check boxes and the Button (in the editor) has a glitched pixel column. In my app (bug02 and 03) you can see no AA in project settings (no bug) and MSAA2D 2x (same for 4x) settings with bugged line, see the x-axis (draw_line in Godot, x start and end are 100% equal).

[francogp]

I created a report to nvidia support, and they insist that the correct place to complain about this, is this thread: Please, upvoat my report or create others.

https://www.nvidia.com/en-us/geforce/forums/game-ready-drivers/13/556258/geforce-grd-57216-feedback-thread-released-13025/3495991/

[akien-mga]

I created a report to nvidia support, and they insist that the correct place to complain about this, is this thread: Please, upvoat my report or create others.

https://www.nvidia.com/en-us/geforce/forums/game-ready-drivers/13/556258/geforce-grd-57216-feedback-thread-released-13025/3495991/

It seems like they edited the OP of this thread go acknowledge the Godot/Vulkan issue, with an internal bug number:

[GODOT/Red Dead Redemption 2/ImGui] Some Vulkan apps may display minor rendering artifacts with GRD 572.16 [5086373]

[IAmSegfault]

Hi I wanted to add that this recent update from Nvidia broke the Transparent BG option for the SubViewport node for me.

This happened on an Ubuntu 24.04 machine running nvidia-driver-535 with a project using the Forward+ renderer. The Transparent BG check box will no longer make the background of a child environment transparent. The issue appears to go away when switching the renderer to compatibility.

[Naros]

This also seems to affect 571.96, which I am using on Windows 11 and I'm seeing odd graphical glitches with Godot 4.4.beta2.

[arujano]

Can confirm the latest Nvidia drivers cause issues on a bunch of different versions of Godot.

[KeyboardDanni]

I saw a writeup on the recently released "The Sims Legacy Collection" where someone noticed the bug there too: https://gist.github.com/riperiperi/78c843b7fc3b11a92e3d5585a7815fee#misplaced-pixels-on-nvidia-dxgi-swapchain

Of note, they found that the artifacts don't appear on in-game screenshots or Renderdoc captures. The glitch seems to only be present in the DXGI presentation layer. So in-engine graphics settings don't have anything to do with it.

[KeyboardDanni]

Hi I wanted to add that this recent update from Nvidia broke the Transparent BG option for the SubViewport node for me.

This happened on an Ubuntu 24.04 machine running nvidia-driver-535 with a project using the Forward+ renderer. The Transparent BG check box will no longer make the background of a child environment transparent. The issue appears to go away when switching the renderer to compatibility.

@IAmSegfault Sounds like you're running into a different issue. Possibly this? #99715

[MacjaZival]

I am also having this issue on the latest Game Ready and Studio drivers from NVIDIA but it is much more noticeable and harsh on the Studio driver than on the Game Ready driver.

[Elrinth]

I have 3090 RTX

Same issue for me... Problem is, windows 11 force-updated to 24H2 yesterday and since then computer randomly started autorebooting. So I think previous graphics drivers are problematic with 24H2. So I update to 572.16... Now I got this problem display instead...
Is it because some kind of FSR/DLSS is being forced on applications now?

[MacjaZival]

I have 3090 RTX

Same issue for me... Problem is, windows 11 force-updated to 24H2 yesterday and since then computer randomly started autorebooting. So I think previous graphics drivers are problematic with 24H2. So I update to 572.16... Now I got this problem display instead... Is it because some kind of FSR/DLSS is being forced on applications now?

I just downgraded to 566.36 and everything works fine now, I am also on 24H2 but did not have the issues you are describing even when I was on the latest driver, just the visual artifacts.

[vedarthjoshi]

I had the same issue changing the forward+ to compatibility fixed but isn't solution
so choose to reinstall the previous drivers (basically downgraded 566.36) and that fixed it for now
I am using godot 4.2.1

[Anixias]

Switching to d3d12 rendering device instead of Vulkan is another alternative instead of downgrading your drivers.

[WiLuX-Source]

I experienced this problem with 4050 and I reverted back to older version it is fixed for me now.

[swissdude15]

I also noticed this on Godot 4.x after updating to 527.16 (studio-driver, 3080). It only seems to affect Vulkan on my Win11 system, I haven't noticed any problems with DirektX.