Search Issue Tracker
Won't Fix
Won't Fix in 6000.0.X
Votes
8
Found in
2022.2.17f1
2023.1.0b14
2023.2.0a12
2023.3.0a3
6000.0.0b11
Issue ID
UUM-34400
Regression
No
Decals are not visible when the "Use Rendering Layers" option is enabled
Reproduction steps:
1. Open the attached “ASDQWE” project
2. Open the “Assets/Scenes/Levels/Chapter1/C1L4/C1L4.unity” Scene
3. Select “Assets/URP/Settings/URP-Renderer.asset”
4. In the Inspector Window enable Decal > Use Rendering Layers
5. Observe the decals in the Game View
Expected result: Decals are visible and are rendered in their layers
Actual result: Decals are not visible
Reproducible with: 2022.2.17f1, 2023.1.0b14, 2023.2.0a12
Could not test with: 2020.3.47f1 (Multiple errors in Outline.cs and AssemblyImportSettingsAutomation.cs), 2021.3.24f1 (Render Layers are not available for this version)
Reproducible on: Intel MacOS 13.3.1
Comments (2)
-
UnityMOV
Oct 26, 2023 04:14
You also need to enable SMAA of RenderPipelineAsset, which enables the rendering layer of decals. Opaque materials will not be displayed on screen. All of this will only appear in the Forward/Forward+ Render path
-
v0lt1369
Jun 08, 2023 11:33
This only happens on the deferred rendering path
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
- Assets are created in the Package folders when creating assets via custom buttons in the Inspector window or other windows
- “Select” windows are named differently on Windows and macOS
- [Windows] No minimum “Select” window size
- Enabling “Editor Extension Authoring” in UI Builder doesn’t dirty the document and saving with shortcut doesn’t persist the state
- WebRequest.Create() function fails with "URI prefix is not recognized" errors when the project is built for Linux Standalone or Windows Dedicated Server
Resolution Note:
The user themselves has said that the bug is fixed. Closing.
Resolution Note (6000.0.X):
The user themselves has said that the bug is fixed. Closing.