Search Issue Tracker
Won't Fix
Won't Fix in 2020.3.X
Votes
11
Found in
2020.3.46f1
Issue ID
UUM-28982
Regression
No
Decals overlap when placed behind a mesh with subsurface scattering
How to reproduce:
1. Download and open the attached project
2. Open the "Gawain_DemoScene" scene
3. Observe the "Game" view window
Expected result: Decals do not overlap with the meshes on the model's face
Actual result: Decals overlap with the meshes on the model's face
Reproducible with: 2020.3.46f1 (10.10.1), 2021.3.20f1 (12.1.10), 2022.2.10f1 (14.0.6), 2023.1.0b7 (15.0.4), 2023.2.0a5 (16.0.0)
Comments (1)
-
unity_Suh2jwepow3xCA
Apr 17, 2023 12:37
How is THIS a duplicate if the link you provided leads to an issue that was reported a month LATER?
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
- Usymtool tries to upload GameAssembly.pdb when it doesn't exist after building with Mono backend
- “NullReferenceException” error thrown in the Console when running HDRP Wizard “Fix All” in URP project after installing HDRP Package
- "Debug Draw Mode" unchecked checkboxes are not visible
- [Android] App crashes when Volume Depth of Field is set to "Bokeh" while using Vulkan Graphics API
- Baked Off Mesh Links outside the modified area are deleted when using NavMeshSurface.UpdateNavMesh
Resolution Note:
This issue highlight a problem in the HDRP renderer design. HDRP made some render pass choice for performance reasons. Fixing this issue properly will have a perforce impact, thus the won't fix to not affect existing project. However there is a workaround. This issue only happen in deferred mode and with object that use object motion vector. For such case, the workaround is to enable a full depth prepass via "Depth prepass within Deferred" on the framesetting of the camera. This will fix the issue but have some cost on the CPU.
Resolution Note (2020.3.X):
This issue highlight a problem in the HDRP renderer design. HDRP made some render pass choice for performance reasons. Fixing this issue properly will have a perforce impact, thus the won't fix to not affect existing project. However there is a workaround. This issue only happen in deferred mode and with object that use object motion vector. For such case, the workaround is to enable a full depth prepass via "Depth prepass within Deferred" on the framesetting of the camera. This will fix the issue but have some cost on the CPU.