Search Issue Tracker
Fixed
Won't Fix in 2022.3.X, 6000.0.X
Fixed in 7000.0.0a1
Votes
0
Found in
2022.3.16f1
2023.2.4f1
2023.3.0b1
6000.0.0b11
7000.0.0a1
Issue ID
UUM-59480
Regression
No
[URP] GameObjects are transparent in the Game view when MSAA is turned on
Reproduction steps:
1. Open the attached “BugRepro” project
2. Open the “Assets/Scenes/Terminal/TerminalScene” Scene
3. In the Project window, select the “Assets/Settings/PC/PC_High“ Asset
4. In the Inspector window, set the Anti Aliasing (Quality > Anti Aliasing (MSAA)) to 2x
5. Observe the Game view
Expected result: All GameObjects in the Scene are visible in the Game view
Actual result: All GameObjects are transparent
Reproducible with: 2022.3.16f1, 2023.2.4f1, 2023.3.0b1
Couldn't test with: 2021.3.33f1 (Universal RP compilation errors while importing project to this version)
Reproducible on: Windows 10, Windows 11
Not reproducible on: macOS Sonoma 14.2 (M1 Max), macOS Sonoma 14.2 (Intel)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note (6000.0.X):
Hey, thank you for reporting this.
I'm going to be closing this bug as "Won't fix", but this is only because we're going to be fixing this issue on another level.
Basically this bug is caused by the combination of Depth Priming and MSAA in URP. This is a problematic configuration for many reasons, and in a lot of cases it is not performant either.
In a future release, we're going to disable the configuration so that Depth Priming will be unavailable when MSAA is being used. As workaround for now, you should disable Depth Priming on the Renderer.
Resolution Note (2022.3.X):
Hey, thank you for reporting this.
Basically this bug is caused by the combination of Depth Priming and MSAA in URP. This is a problematic configuration for many reasons, and in a lot of cases it is not performant either.
In a future release, we're going to disable the configuration so that Depth Priming will be unavailable when MSAA is being used. As workaround for now, you should disable Depth Priming on the Renderer.