Search Issue Tracker
By Design
Votes
37
Found in
2019.1.0a10
2019.1.0a14
2019.2.0a1
Issue ID
1119198
Regression
Yes
Some Clear flags of Cameras are not working when using Post Process Layer and Directly to Camera Target is set to true
How to reproduce:
1. Open user attached project "PostProcessingWithMultipleCameraIssue.zip"
2. Open "SampleScene" scene
Expected result: Game view background is a skybox
Actual result: Game view background is black
Reproducible with - 2019.1.0a10, 2019.1.0b1, 2019.2.0a3, 2019.3.0a2
Not reproducible with - 2018.3.3f1
Notes:
1) Cant Test with 2019.1.0a1 - 2019.1.0a9 because Post Process Layer script component does not load
2) Could not reproduce with 2017.4 because Post Process Layer script didn't load
3) Don't Clear and Depth Only Clear flags are not working
-
Racot_A
May 21, 2019 16:00
Reproducible in 2019.1.3
-
sier_ua
May 11, 2019 10:57
Reproducible in 2019.1.2...
-
joshcamas
May 06, 2019 19:46
Reproducible in 2019.1.1
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
- GetCurrentAnimatorClipInfoCount() and GetNextAnimatorClipInfoCount() return 0 when animator is in transition
- GPU utilization increases by 20% on Meta Quest headsets when Render Graph is enabled on 6000.0.16f1 and higher
- Value on Slider (Int) control in UI Builder displays as default when saving UI Document
- Color mismatch in UI Builders Library panel when the Editors theme is set to Light Mode
- [Android ] "AndroidJNI.ToBooleanArray" returns a random non-zero value instead of "IntPtr.Zero" when the method argument is null
Resolution Note (2019.1.X):
The "Direct to Camera Target" option removes the final blit Unity does when outputting to the screen, instead letting the post-processing stack output directly to that screen for a small performance benefit. However, this means that any cameras which render after this camera will not be combined with what has been rendered so far, effectively clearing the screen for those cameras. So, this option should only be used on the last camera that you are going to render in a frame.
Note that some users have run into this behaviour when upgrading from older versions to Unity 2019.1 or later. This is because the option was unintentionally enabled by default, but did not do anything in versions prior to Unity 2019.1. (The default has been corrected, as of Postprocessing 2.1.7). Disabling the option will restore the Unity 2018 behaviour.
The behaviour can also be controlled at runtime, via the API on the PostProcessLayer component; for more information, see https://docs.unity3d.com/Packages/com.unity.postprocessing@2.3/api/UnityEngine.Rendering.PostProcessing.PostProcessLayer.html