Search Issue Tracker
Fixed in 2021.3.24f1
Fixed in 2021.3.X, 2022.2.X, 2023.1.X, 2023.2.X, 2023.2.0a3
Votes
0
Found in
2021.3.22f1
2022.2.14f1
2023.1.0a26
2023.2.0a1
Issue ID
UUM-22996
Regression
No
[HDRP] In HDRP if the user selects a custom color & camera depth buffer with MSAA on, it silently breaks and doesn't render
Steps to reproduce:
1. Open Scene.unity in the attached user's project "MSAA_ScreenSpace.zip"
2. In "Avatar Custom Pass" GameObject, set Target Color Buffer to Custom
3. In "Avatar Custom Pass" GameObject, set Target Depth Buffer to Camera
4. In GameObject/Main Camera set MSAA Within Forward to None
5. Note that the hand is rendered OK in Game View
6. In GameObject/Main Camera set MSAA Within Forward to MSAA4X
7. Note that the hand rendering silently fails with no warning as to what went wrong
Expected: some kind of feedback to the user indicating why it didn't render, or a hint that they have accidentally selected incompatible buffers
Actual: no warning or error that selected buffers are incompatible, hence rendering does not occur
Reproducible on: 14.0.5 - 15.0.3 (2022.2.3f1, 2023.1.0a25)
Could not test on 2020.3.44f1 and 2021.3.17f1 due to project errors when downgrading the HDRP package and the GameObject not rendering
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Too little validation messages in the "WebAssembly Language Features" Memory settings
- Project Settings Search Highlights are misaligned when using the Bitmap Text Rendering Mode
- "GetControlID at event ValidateCommand returns a controlID different from the one in Layout event" Warning is thrown when undoing the deletion of Sprite Shape Profile
- Memory related fields in the "WebAssembly Language Features" can be set to the negative numbers
- "WebAssembly Language Features" Header in the Player Settings has a smaller indentation
Add comment