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
- Different text alignment in the column header in Entities "System" window
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
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.