Mobile Renderer with MSAA not working when using the viewport stretch mode (presents a black screen)

[norrath-hero-cn]

---

Bugsquad note: This issue has been confirmed several times already. No need to confirm it further.

---

Godot version

Godot Engine v4.0.beta2.official.f8745f2f7 - https://godotengine.org

System information

Windows 10, Vulkan API 1.2.0 - Using Vulkan Device #0: NVIDIA - NVIDIA GeForce GTX 960

Issue description

Steps to reproduce

Forward_Plus is OK, but something happened with mobile renderer

1. Project Settings->Renderer, switch Rendering method to "mobile"
2. Project Settings->Anti Aliasing, enable MSAA 2D "2x(Average)" and MSAA 3D "2x(Average)"
3. Present a black screen with massive error spam

Minimal reproduction project

demo.zip

[Calinou]

Does this occur if you only change 2D MSAA or 3D MSAA, not both?

[norrath-hero-cn]

Does this occur if you only change 2D MSAA or 3D MSAA, not both?

yes, single one or both, all present black screen

[norrath-hero-cn]

Re-rested on beta4

[norrath-hero-cn]

Re-tested on Beta5

[norrath-hero-cn]

Re-tested on Beta7

[Calinou]

Related to #18320.

I can confirm this on 4.0.beta7 (Linux, AMD Radeon RX 6900 XT with RADV). It's the good old MSAA + viewport stretch mode + window size different from viewport size issue, but in 4.0. The minimal reproduction project uses the viewport stretch mode:

[ClarkThyLord]

Ran into this issue with Godot 4 beta 16, tried different combinations of MSAA, but I'm only getting a black screen when MSAA_2D is set to something other than disabled.

[norrath-hero-cn]

Recent events on Cybereality and my experience makes me feel that keep the hope for Godot, provide detailed technical analysis, keep track of some bugs that will never be fixed is meaningless, so close it to reduce the number of issues for Godot.

[Calinou]

Reopening, as I can still reproduce this in 4.2.dev 0f7625a (Linux, GeForce RTX 4090 with NVIDIA 535.54.03).

Note that this does not occur if Scaling 3D > Scale is set to a value different than 1.0. This means that as a workaround, you can use a scale of 0.99 or 1.01.

[ozanyasindogan]

Reopening, as I can still reproduce this in 4.2.dev 0f7625a (Linux, GeForce RTX 4090 with NVIDIA 535.54.03).

Note that this does not occur if Scaling 3D > Scale is set to a value different than 1.0. This means that as a workaround, you can use a scale of 0.99 or 1.01.

Forward+ and Compatibility renderers works fine with my settings however when MSAA 2D is set to any value other than
Disabled, the scene does not render and gives a black screen in Mobile renderer.
It doesn't display any error information by the way.
Turning of MSAA for 2D makes it work fine again.
After the video, I downloaded latest stable version 4.1.3 (.Net) and the same issue persist there:
https://www.youtube.com/watch?v=XJAMBNlhN8U

[lfxu]

v4.2.1.stable.offical [b09f793f5] on Android (Pixel 3), turning on MSAA 3D with any option in a blank project produces a black screen. Turning on MSAA 2D doesn't. No error via Godot Debugger. No error via adb logcat.