Search Issue Tracker
By Design
Votes
2
Found in
2021.3.31f1
2022.3.10f1
2023.1.16f1
2023.2.0b12
2023.3.0a8
6000.0.0b11
Issue ID
UUM-52680
Regression
No
Bloom is rendered incorrectly when using Camera.Render() on a RenderTexture
How to reproduce:
1. Open the user-attached project “TestPostProcessing”
2. Open the “SampleScene” scene
3. In the upper menu click Tools → Snapshot
4. Go to the AppData/LocalLow/DefaultCompany/TestPostProcessing/Test
5. Open the .png file and compare it to the Editor Game View
Expected result: The bloom is the same in the .png and the Game View
Actual result: The bloom in the .png is rendered differently
Reproducible with: 2021.3.31f1, 2022.3.10f1, 2023.1.16f1, 2023.2.0b12, 2023.3.0a8
Reproducible on: Windows 11 Pro
Not reproducible on: No other environment tested
Comments (1)
-
avea_autolegends
Oct 09, 2023 20:44
This issue seems to be reproducible regardless of which bloom solution is in use, be it the built in URP bloom, or an asset to do bloom such as MK Glow.
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
- Unity CIL Linker fails on Player build when persistent listeners have "<" and ">" in their XML attribute names
- ”Lighting data asset ‘LightingData’ is incompatible with the current Unity version…” warnings are thrown when saving Indoors (URP) and Outdoors (URP) Scenes as Scene Templates
- [iOS] The screen blinks when transitioning from custom to Unity splash screen
- [macOS] ”Ignoring depth surface load action as it is memoryless” warnings are thrown when taking Game View Snapshot
- UI Builder Inspector scrolls back up when changes on an expanded but not fully displayed Inspector tab are saved
Resolution Note:
The issue is in the format of the RenderTexture, as URP would use it to allocate internal buffers instead of default LDR/HDR formats specified in the pipeline asset. Camera.Render() does not contribute to this as the same happens if an RGBA32 texture is set as camera Output Target and the camera is let to render normally as part of the frame. A workaround would be to use DefaultFormat.HDR when creating a RenderTexture.