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
- Frame Debugger is not disabled when switching Scenes if the Frame Debugger window is not open during the transition
- Standalone Profiler Targets another Project if a Standalone Profiler was launched in it before when switching between Edit or Play Mode Targets
- Crash on ForwardRenderLoopJob when opening a specific project
- [Android] Memory leak and eventual crash on Snapdragon 8 Gen 1+ devices when a Clear Pass is executed after Framebuffer Fetch
- Crash on EnumerateDisabledKeywordsInVariantsArray or UNITY_XXH32 when rapidly saving ShaderGraph or VFXGraph changes
Chromiqee
May 30, 2015 10:55
U just must to fix it :c
themosk
May 28, 2015 18:44
Please Unity fix this