Search Issue Tracker
By Design
Votes
1
Found in [Package]
1.0.4
Issue ID
1164531
Regression
No
HDR colors are lost from one Camera to the next when rendering multiple Cameras with their Clear Flags set to Don't Clear
How to reproduce:
1. Open attached project
2. Open 'Lost HDR Bug Report.unity'
3. Select the four player cameras and disable their Post Process Layer components
4. Select the Post Processing Camera and enable its Post Process Layer component
Reproducible with: 2017.4.29f1, 2018.4.3f1, 2019.1.8f1, 2019.2.0b6, 2019.3.0a7
Reproducible with PostProcessing package 1.0.4 to 2.1.7
Actual results: HDR content of the frame buffer have been clamped to LDR, and HDR dependent post processing effects like bloom don't give then intended result.
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
- Standalone Player crashes with "TDerived GetOrLoad<TDerived>() where TDerived : T" when IL2CPP Code generation is set to "Faster (smaller) Builds"
- IndexOutOfRangeException and InvalidOperationException when logging XML string
- Script missing in "Assets/Settings/Mobile_Renderer/GlobalVolumeFeature" of "com.unity.template.urp-blank" template
- “Font Asset Creator - Error Code [Invalid_File_Structure]…“ error is logged when generating Font Assets from fonts with meta files from previous Editor versions
- Input.mousePosition returns (NaN, NaN, 0.00) when Scene view is opened
Resolution Note:
In the builtin pipeline cameras render to a final RGBA8 framebuffer no matter what, with or without post-processing enabled. Camera stacking doesn't respect the HDR toggle all the way (which in turn affects post-processing in these kinds of setups).
Potential workaround: setting cameras to render to custom render textures instead of the builtin one and compositing these at the end.