Search Issue Tracker
Won't Fix
Votes
0
Found in
2020.3.46f1
2021.3.20f1
2022.2.9f1
2023.1.0b7
2023.2.0a5
2023.3.0a3
Issue ID
UUM-29588
Regression
No
Post Processing is not applied in camera preview
Reproduction steps:
1. Open the attached “testPanorama.zip“ project
2. Open “Scene_testPanorama” scene
3. Select “Main Camera” GameObject to activate camera preview
4. Observe camera preview and Game view
Expected result: GameObjects are rendered the same in camera preview and Game view
Actual result: GameObjects are rendered without bloom in camera preview
Reproducible with: 2020.3.46f1, 2021.3.20f1, 2022.2.9f1, 2023.1.0b7, 2023.2.0a5
Reproduced on: macOS Monterey 12.6 (Intel), Windows 10 (by the reporter)
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
- Blank, Light-Themed "Create Node" window becomes visible on the next project open
- UI Elements/Layout inconsistencies in the Particle System component
- The Game view and Scene view fail to render when launching the Editor with a maximized Render Graph Viewer window
- "List is empty" is poorly visible in the "Create Node" window
- [Android] GameObject with a custom shader becomes invisible when deployed with the Vulkan Graphics API
Resolution Note:
The problem is that the camera preview is creating a temporary copy of the camera component, copying data, then rendering that duplicate camera. It handles skybox components as a special case. We cannot do the same for post-fx because the PostProcessingLayer component exists as part of a package, and thus cannot be referenced from the Editor.
An alternative solution was explored, which called `Camera.Render` directly rather than creating a duplicate GameObject. While this partially worked, both URP and HDRP can require additional data to render properly. Ex, TAA works over multiple frames.
While this is possible to address, it would require large scale refactoring that is not commensurate with the inconvenience of the issue. After careful consideration, we have determined that other higher-priority issues should take precedence, and we have decided not to address your issue at this time. The priority level is determined by factors such as the severity and frequency of an issue and the number of users affected by it. We appreciate your input and understanding, and please let us know if you have any other concerns or issues you would like to report in the future.