Search Issue Tracker
Fixed
Won't Fix in 2022.3.X
Fixed in 6000.0.59f1, 6000.2.6f1, 6000.3.0a5
Votes
1
Found in
2022.3.62f1
6000.0.50f1
6000.1.5f1
6000.2.0b3
6000.3.0a3
Issue ID
UUM-107966
Regression
No
Decal Technique set to Automatic prefers the DBuffer option when using OpenGL
How to reproduce:
1. Open the project "IN-103403_DecalDBuffer"
2. Open the scene in the Project Tab, Assets -> _UnlitDecalTest -> "UnlitDecalTesting.scene"
3. In the same folder, click on the "UnlitDecalTesting Universal Render Pipeline Asset_Renderer"
4. In the Inspector, Decal -> Technique, set it to Automatic
5. Observe the Game View
Expected result: Projected Decals in the scene do not disappear
Actual result: The Projected Decals disappear
Reproducible with: 2022.1.0a1, 2022.3.62f1, 6000.0.50f1, 6000.1.5f1, 6000.2.0b3
Reproducible on: Windows 11
Not reproducible on: No other environments tested
Note: It is stated that the DBuffer technique does not support OpenGL https://docs.unity3d.com/6000.0/Documentation/Manual/urp/renderer-feature-decal-reference.html
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
- Reflection Probe “Probe Scene Editing Mode:” text is barely visible
- [HDRP] Game view doesn’t refresh after changing Camera Background Type until mouse moves over it
- Some Shaders appear twice in Material Shader selection menu
- Editor freezes with a StackOverflowException when certain asset types are assigned to a managed component in a SubScene via AddComponentObject
- Scale Snapping with Gizmos does not work in the Scene view when Snapping and Absolute Grid Snapping are toggled off
Resolution Note (fix version 6000.2.6f1):
Now when selecting the Decal Technique to Automatic, it chooses Screen Space. When selecting DBuffer, a box with an error message appears that states that DBuffer is not supported on OpenGL and Decals will not render.
Resolution Note (2022.3.X):
Thank you for reporting a bug to Unity.
This issue will be fixed in an upcoming release. We have reviewed the issue carefully, and in this case, the team is unable to prioritize backporting this bug to existing releases. 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 a backport may destabilize a release in production.
Today we will be closing this port. 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.