Search Issue Tracker
Fixed
Votes
52
Found in
5.0.0b21
Issue ID
667265
Regression
No
[CmdBuffers] Expose a way to write depth in CommandBuffer before deferred "depth resolve/copy" happens [many votes, Rust]
CommandBufferTest renders a mesh with the default material. In the frame debugger both the black (unlit) color and the depth values show up correctly. However, image effects that follow do not see the mesh in the depth buffer.
To reproduce:
1. Open the project and the scene
2. Open the frame debugger
3. Observe that image effects that are applied after setting the depth buffer removes depth
Comments (2)
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
- UI Toolkit meshes are fully rendered and rasterized when opacity is 0
- Light rendering artefacts appear in the Editor when assigning unsupported 3D Custom Render Texture in Camera’s Output Texture, unclearable errors and warnings spammed
- Memory leak when running a test with "GfxThreadingMode" set to "SplitJobs"
- Loading Unloaded unsaved Scene throws “ArgumentException” error in the Console
- Crash on std::__1::__tree_const_iterator when opening the Build Profiles window in a specific project
Chromiqee
May 30, 2015 10:55
U just must to fix it :c
themosk
May 28, 2015 18:44
Please Unity fix this