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
- [Linux] Unity licensing command on Linux pops a progress bar when using -batchmode and -nographics
- SerializedReference GameObject property gets set to null after entering Play mode
- Profiler - RawFrameDataIterator ThreadID will always return 0 for profiler frame data loaded from .data files
- Crash on scripting_field_get_type when a Script has List<> of LayoutKind.Explicit struct with [FieldOffset(1)] ScriptableObject
- Frame Debugger doesn't work when using Camera.SetTargetBuffers
Resolution Note (fix version 2020.1):
Get render params from the frame's pose instead of the main camera.