Search Issue Tracker
Fixed
Won't Fix in 2022.3.X
Fixed in 2023.3.X, 2023.3.0b1
Votes
1
Found in
2022.2.2f1
2023.1.0a24
2023.2.0a1
2023.3.0a3
Issue ID
UUM-21928
Regression
No
URP Decal Projector doesn't affect Terrain textures when Rendering Path is Deferred
Reproduction steps:
1. Open the attached “My project (30).zip“ project
2. Open “SampleScene” scene
3. Observe Decal Projector in Scene window
4. Change Rendering Path to Forward in “DefaultRenderer” asset
5. Observe Decal Projector in Scene window
Expected result: Decal Projector affects both Grass texture and Terrain with Deferred Rendering Path
Actual result: Decal Projector doesn’t affect Grass texture with Deferred Rendering Path
Reproducible with: 2022.2.2f1, 2023.1.0a24
Could not test with: 2020.3.43f1 (due to errors in Console Log), 2021.3.16f1 (crash on #0 0x0000010e8e7947 in IsPatchClamped(int, int, DetailRenderMode, float, DetailDatabase const&))
Reproduced on: macOS Monterey 12.6 (Intel)
Note: Also reproducible in Build
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
- VFX Graph particles are not culled when using URP and Frustum Culling is enabled on VFX Mesh Output
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
Resolution Note (2022.3.X):
Thank you for reporting a bug to Unity.
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.
A fix for this is available in 2023.3.
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.