Search Issue Tracker
Won't Fix
Votes
0
Found in
2022.3.62f1
6000.0.50f1
6000.1.6f1
6000.2.0b4
Issue ID
UUM-108291
Regression
No
Depth testing not working correctly for opaques rendered in "After Post-Proces" pass with TAA enabled
Reproduction steps:
1. Open the attached project "ReproProj"
2. Open the “/Assets/OutdoorsScene.unity” Scene
3. In Hierarchy, select “Main Camera“ GameObject
4. Set Fallback Post Anti-aliasing to “TAA“
5. Enter the Play Mode
6. Observe the Game view
Expected result: “ObjectWithAfterPostProcess“ can’t be seen through other objects
Actual result: “ObjectWithAfterPostProcess“ can be seen through other objects
Notes: Depth Test is enabled for After Post-Process pass in Frame Settings
Reproducible with: 2022.3.62f1, 6000.0.50f1, 6000.1.6f1, 6000.2.0b4
Reproducible on:
Play Mode
Windows Standalone Player
Testing environment: Windows 10 Enterprise 21H2
Not reproducible on: No other environment tested
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
- “No method with RuntimeInitializeOnLoadMethod attribute” warning from ReadmeEditor.cs is thrown after installing Project Auditor Rules
- Projection matrix is altered when using RasterCommandBuffer.ClearRenderTarget on DX12 and Metal
- Entities Hierarchy window allows Cyclic nesting and throws an “ArgumentException: Cyclic nesting detected” error when dragging a Prefab onto the same Prefab in the Entities Hierarchy
- EnterPlayModeOptions doesn't take effect if user manually modifies m_EnterPlayModeOptionsEnabled to 0
- VFX Graph Documentation dropdown button does nothing when clicked on the right side
Resolution Note:
Thank you for reporting a bug to Unity.
The depth buffer is not available in the AfterPostProcess injection point. It is the last event available in your frame as documented here: https://docs.unity3d.com/Packages/com.unity.render-pipelines.high-definition@17.4/manual/rendering-execution-order.html
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.