MSAA + Multi-Stack Camera Causes Black Screen in WebGL & Graphics API Failure in Unity 6.0.23f

Unity Engine
, , , ,
1

I’m experiencing an issue in Unity 6.0.23f (URP) when using MSAA with multi-camera stacking:

  • WebGL Build: Black screen when MSAA is enabled. It works only if I disable MSAA or unstack cameras.
  • Desktop Build: Automatic Graphics API fails, but works if I manually set Vulkan as the top API.
  • This issue did not exist in older Unity versions.

Steps to Reproduce:

  1. Use URP with Main Camera (Base) + Overlay Camera (UI).
  2. Enable MSAA (2x, 4x, or 8x) in the URP Asset.
  3. WebGL Build → Black screen.
  4. Desktop Build → Automatic Graphics API fails (works only with Vulkan set manually).

Expected Behavior:

  • WebGL should render properly with MSAA + stacked cameras.
  • Desktop builds should work with Automatic Graphics API enabled.

This issue worked fine in previous Unity versions but is broken in Unity 6.0.23f and other Unity 6 versions tested.

Can you please investigate this and confirm if there’s a fix?

Unity 6.1 is now available
2

Try to update to latest 6.0.41f and let us know if it doesn’t work. We have fixed a couple of issues with MSAA in the past months.

3

I tested the latest Unity 6.0.4f on Windows, and the issue is resolved. However, in WebGL, the same issue persists.

I’m attaching a screenshot of the error. Additionally, with Multi-Stack Camera and MSAA enabled in WebGL , certain objects are not rendering. If I disable MSAA, the objects become visible.

Screenshot 2025-03-10 103522
Screenshot 2025-03-10 103522973×600 65 KB

4

I’m facing an issue in Unity 6.0.34f where enabling MSAA with a Multi-Stack Camera setup results in a black screen in WebGL. The console shows a Graphics API failure. Disabling MSAA seems to fix it, but I need anti-aliasing for my project.

Has anyone encountered this? Any workarounds or fixes?

5

I tested the latest Unity 6.0.4f on Windows, and the issue is resolved. However, in WebGL , the same issue persists.

I assume you meant 6.0.41f? Can you confirm?

It looks like something is broken with WebGL and MSAA. Are you using any custom pass (ScriptableRendererFeature) or this is URP vanilla?

6

Yes, we are using the same Unity version (6.0.41f). We are not using any vanilla features. For confirmation, I am attaching a screenshot so you can check the issue yourself.

Desktop

01
011531×923 163 KB

webgl

02
021020×617 78.1 KB

7

Can you attach a screen capture of the Render Graph viewer in this setup?

8

Screenshots are limited in detail, and you haven’t specified exactly what you need. So instead of a screenshot, I’m providing a full video where I’ve captured all the details from the render graph. You can pause the video and check the details as needed.

Video

9

Thanks for the video. Can you submit a bug through the Editor with the repro case and all the explanations provided in this thread? We will have a look.

10

I did but its currently under review

Screenshot 2025-03-19 090807
Screenshot 2025-03-19 090807949×848 126 KB

11

You should probably mention it is 6.0.41f and not 6.0.4f. 6.0.4f < 6.0.23f < 6.0.41f. Unity QA reviewing the bug might be confused and consider it has been fixed in 6.0.23 if it only happens in 6.0.4f.

12

Unity teams close my request because someone already report this issue and team already aware of it.

here is the issue link

image
image762×461 22.5 KB

1 Like
13

Today i tested with Unity newly realised version 6.1 same issue