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
-
sewy
Aug 06, 2019 07:50
-
sewy
Jul 22, 2019 10:38
If it is "by design" what about the blurrines when disabled?
-
joshcamas
Jul 05, 2019 14:39
Reproducible in Unity 2019.1.9
-
Tizzio91
Jul 01, 2019 20:01
Reproducible in 2019.3.0a7
-
joshcamas
Jun 25, 2019 05:59
Reproducible in Unity 2019.1.8
-
joshcamas
Jun 18, 2019 18:53
Reproducible in Unity 2019.1.7
I am stuck using 2018.3 due to this bug
-
mdrittel
Jun 12, 2019 07:21
Reproducible in 2019.1.6
-
Tomer-Barkan
Jun 07, 2019 09:45
Are there plans to fix this?
2019.1.5 and it's still there, preventing us from upgrading from 2018 to 2019. -
sumpfkraut
Jun 04, 2019 07:03
Reproducible in 2019.1.5
-
joshcamas
May 26, 2019 21:39
Reproducible in 2019.1.4
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
- Investigate why .meta files are sometimes not parsed right
- Cursor is not locked to Game window when pressing Windows key then clicking the Taskbar and refocusing the Game
- EditorGUIUtility.ShowObjectPicker doesn't allow to pick assets from derived classes
- Disabling and enabling an AudioSource component controlled by a Timeline causes a pop and ignores the mixer settings
- Build Pipeline functions cause a re-execution of the last Async task when called in an Async function
Resolution Note (fix version 2019.1):
This is by design. The "Direct to Camera Target" option is meant to be used to remove the final blit Unity does when outputting to the screen and instead let the post-processing stack output directly to that screen. This should only be used if you only have one camera or know that you won't be rendering any other camera after the one that has this option enabled.