Using the `viewport` stretch mode and resizing the window (or using "shrink" value other than 1) results in black screen if MSAA is forced on in NVIDIA or AMD settings

[Calinou]

Godot version: Git 7d6f210

OS/device including version: Fedora 27, NVIDIA 390.48

Issue description: When the window scaling mode is set to 2d or viewport, setting the display/window/stretch/shrink project setting to a value other than 1 will cause the running project's rendering to break (it will appear to be frozen at the splash screen). If the window is resized by the user, it will turn into a black screen. No errors can be seen in the Debugger dock of the editor.

This also occurs when using the viewport stretch mode after resizing the window, even if display/window/stretch/shrink is set to 1.

Steps to reproduce: After making sure the window scaling mode is set to 2d or viewport, set display/window/stretch/shrink to a value other than 1 in the Project Settings then run the project.

Minimal reproduction project:
Resize the window diagonally after starting the project.

• 4.x: shrink_bug4.zip
• 3.x: shrink_bug3.zip

---

Update: I can still reproduce this as of 6110bde (Fedora 30, NVIDIA 418.74). When the bug occurs, this appears in the console when Godot is started with --verbose:

ERROR: _gl_debug_print: GL ERROR: Source: OpenGL        Type: Error     ID: 1282        Severity: High  Message: GL_INVALID_OPERATION error generated. Source and destination dimensions must be identical with the current filtering modes.
   At: drivers/gles3/rasterizer_gles3.cpp:123.

[flashyincceo]

I am unable to replicate this bug on macOS 10.12.6 with the latest development version of Godot.

I've tried setting the mode to 2d and viewport, and tried a couple of different display/window/stretch/shrink values, but the issues you are describing never popped up for me.

[akien-mga]

Works fine for me on 3.1.1-stable and 9643b2b on Mageia 7 with both my graphic cards, KDE Plasma:
OpenGL ES 3.0 Renderer: Mesa DRI Intel(R) HD Graphics 630 (Kaby Lake GT2)
OpenGL ES 3.0 Renderer: AMD VEGAM (DRM 3.30.0, 5.1.3-desktop-4.mga7, LLVM 8.0.0)

[daniel-abbott]

I've also been unable to replicate this behavior, using Windows 10 Pro, version 10.0.17134, neither in Godot 3.1.1-stable nor in 7d42ca8 and the GLES3 renderer:
OpenGL ES 3.0 Renderer: GeForce GTX 980M/PCIe/SSE2
OpenGL ES 3.0 Renderer: Intel(R) HD Graphics 530

[Calinou]

I just found out why this is occurring (and why nobody else has been able to reproduce it 😛).

This is caused by enabling a setting in the NVIDIA driver that tries to force MSAA in all applications:

(It generally isn't effective on newer applications, including Godot. However, it helps when running some old games or niche applications that don't feature MSAA settings. For those looking to disable forced MSAA on a per-application basis, this can be done using application profiles.)

The Godot project setting that enables MSAA works fine with the viewport stretch mode otherwise:

I'm not sure if we can fix this issue on our end. Someone with a NVIDIA graphics card on Windows should try to enable the equivalent setting in their driver settings, and see if it causes the same bug.

[clayjohn]

Confirmed! :) Windows 10 NVidia GTX 1050 graphics card. When override MSAA is set it hangs on the splashscreen indefinitely and when resized turns black.

[RicardRC]

Windows 10 Nvidia GTX 1070 confirmed. Exact same sympthoms as clayjohn.

[Calinou]

Are there any resources on fixing this (from the developer's side)? I'm not sure if reporting this issue to NVIDIA would be useful, as forcing MSAA is generally considered to be a legacy feature since it only impacts old applications.

[softgripper]

I just stumbled upon this bug too.

Disabling Antaliasing - Mode inside NVidia inspector "hid" the problem.

So the question is - is this a bug that won't get addressed (too hard to fix), or something that can't be fixed because of NVidia setting.

[clayjohn]

@softgripper It is an NVidia bug. :) If you want something done about it, you can report it to them. We can't fix NVidia software.

Please do file a bug report with them though, the more people that report it, the more likely they are to fix the problem.