Search Issue Tracker
Fixed in 2020.1
Fixed in 2018.4, 2019.2, 2019.3
Votes
0
Found in
2018.4
2018.4.11f1
Issue ID
1191487
Regression
No
Unity is submitting the depth buffer to a the next frame isntead of the current one
While using an internal debug tool that allows them to get the depth and color buffers at presentation time, Microsoft discovered that the depth buffer information was being written with data one frame behind the color buffer.
Favro: https://favro.com/organization/c564ede4ed3337f7b17986b6/2cb994fca38e514c8629373e?card=Uni-107637
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 2020.1):
Get render params from the frame's pose instead of the main camera.