Search Issue Tracker
Fixed in 2017.2.X
Votes
0
Found in
5.6.0b7
Issue ID
879378
Regression
No
[Graphics] CommandBuffer.Blit() writes to the first Depth Slice of a 3D render target, regardless of the depthSlice parameter
Reproduction steps:
1. Open the attached project
2. Enter Play mode
Result:
The cube on the left uses Graphics.Blit() which DOES NOT ignore the depthSlice parameter, hence the cube is rendered correctly
The cube on the right used CommandBuffer.Blit() which DOES ignores the set depthSlice parameter, therefore it only renders to the first depthSlice
Reproducible on: 5.6.0b1, 5.6.0b8
Couldn't reproduce on an earlier version, because Unity crashes on entering Play mode
Tested on Windows 10
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on _platform_memmove after entering large value in Graphics settings Preloaded Shaders field
- Disproportionally large impact on CPU frame time when writing to a rendering entity's LocalToWorld
- "Constant Force" Component numeric fields drift out of view while entering a really big value in the Inspector
- Scene view camera speed pop-up appears empty or cut off when Scene view is very narrow
- UnityEvent does not get pasted to a uGUI component when trying to copy it from a Script
Add comment