Search Issue Tracker
Fixed
Fixed in 2021.3.28f1, 2022.3.3f1, 2023.1.1f1, 2023.2.0a12
Votes
0
Found in
2021.3.21f1
2022.2.12f1
2023.1.0b9
2023.2.0a8
Issue ID
UUM-31474
Regression
No
[Quest][URP] Enabling post processing on a camera when it's disabled on the URP settings forces rendering into an intermediate texture
Reproduction steps:
1. Open the attached Project “BugRepro”
2. Open Assets/crime scene
3. Inside the Assets folder there is a URP Asset, Disable Anti Aliasing (MSAA) in its Quality dropdown menu
4. In that same folder there is a Universal Renderer Data Asset, disable Post-processing on it
5. In the Hierarchy window select PlayerController > OVRCameraRig > TrackingSpace > CenterEyeAnchor
6. Open Window > Analysis > Frame Debugger and Enable it
7. Inside Frame Debugger select “DrawOpaqueObjects”
8. Observe its RenderTarget
9. Select the “CenterEyeAnchor” and disable Post Processing inside the Inspector window, under “Rendering” settings
10. Observe the Frame Debugger
Expected result: Having Post Processing enabled on the camera, will show the RenderTarget of “DrawOpaqueObjects” as <No name> in the Frame Debugger
Actual result: RenderTarget is _CameraColorAttachmentA
Reproducible with: 2020.3.46f1, 2021.3.21f1, 2022.2.12f1, 2023.1.0b9, 2023.2.0a8
Reproducible on: macOS 12.6 (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
- SHADERPASS has incorrect value when using Shader Graph for Built-In target
- [VFX] Gizmo still incorrectly rendered for a hidden property
- Nested object label indentation is incorrect when using the UI Toolkit Inspector
- Crash on tlsf_free when UI Elements are moved to the side by scrolling
- Setting VideoPlayer.time and pausing results in incorrect player.frame values
Resolution Note (fix version 2023.2.0a12):
URP: Fixed redundant blit is used due to postFX, although it is disabled in rendererData.