Search Issue Tracker
Fixed in 6000.0.22f1
Won't Fix in 2023.2.X
Fixed in 6000.0.X, 7000.0.0a20, future release
Votes
1
Found in
2023.2.0f1
6000.0.0b14
6000.1.0a7
6000.2.0a1
Issue ID
UUM-68284
Regression
No
[URP][RG][CameraStacking] Passes are failing when CameraStacking and RG are enabled
Steps to reproduce:
1. Download attached project and open in Unity
2. Build and Run Winter_Demo scene
3. Observe the Errors in Development Console:
Postprocessing Final Blit Pass/Screen Space UlToolkit/uGUI Pass - Overlay: Attachment 0 was created with 4 samples but 1 samples were requested.
NextSubPass: Not inside a Renderpass
EndRenderPass: Not inside a Renderpass
Actual results: Errors in the Development Console
Expected results: No errors in the Development Console when using Camera Stacking together with the RG
Reproducible with versions:
2023.2.0f1, 2023.3.0b7, 6000.0.0b14
Tested on (OS):
MacBook Pro (16-inch, 2021), CPU: Apple M1 Max, Memory: 64 GB, macOS: Ventura 13.3.1 (a) (22E772610a)
Comments (1)
-
bryanchew1994
Feb 16, 2025 17:39
Similar problem still exists on Unity 6000.38 :(
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
- Crash on _platform_memmove after entering large value in Graphics settings Preloaded Shaders field
- Disproportionally large impact on CPU frame time when writing to a rendering entity's LocalToWorld
- "Constant Force" Component numeric fields drift out of view while entering a really big value in the Inspector
- Scene view camera speed pop-up appears empty or cut off when Scene view is very narrow
- UnityEvent does not get pasted to a uGUI component when trying to copy it from a Script
Resolution Note (fix version 6000.0):
Camera stacking rendering to system backbuffer with URP Render Graph on iOS/macOS has been fixed. The error message regarding the mismatch of msaa samples for the final blit pass won't appear again. Thanks for having taken the time to report this bug!
Resolution Note (2023.2.X):
Closing as Won't fix due to 2023.2 reaching it's EOL.