Search Issue Tracker
Won't Fix
Won't Fix in 2021.3.X
Votes
0
Found in
2021.3.24f1
Issue ID
UUM-35634
Regression
Yes
Camera displays objects out of order when more than one Camera with Post-Processing is used
How to reproduce:
1. Open the attached user’s project “Camera Bug.zip”
2. Observe the Game View or Build And Run
Expected result: Objects are rendered according to their render order (2, 5, 10)
Actual result: Objects are rendered out of order (5, 10, 2)
Reproducible with: 2021.2.0b2, 2021.3.24f1, 2022.1.0a16
Fixed in: 2022.1.0b1
Not reproducible with: 2020.3.47f1, 2021.2.0b1, 2022.2.18f1, 2023.1.0b15, 2023.2.0a13
Reproduced on: Windows 10
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Stacking multiple base cameras used to be undefined behaviour. In unity 2022.1 we defined this behaviour to disallow stacking of base cameras (the next camera will overwrite what is on the screen). If you wish to do camera stacking please use the overlay camera mode which is well defined and allows for explicit layering.
Resolution Note (2021.3.X):
Stacking multiple base cameras used to be undefined behaviour. In unity 2022.1 we defined this behaviour to disallow stacking of base cameras (the next camera will overwrite what is on the screen). If you wish to do camera stacking please use the overlay camera mode which is well defined and allows for explicit layering.