Search Issue Tracker
Fixed
Won't Fix in 2022.3.X, 6000.0.X, 6000.3.X
In Progress in 6000.4.X
Fixed in 6000.5.0a3
Votes
0
Found in
2022.3.68f1
6000.0.61f1
6000.1.16f1
6000.2.8f1
6000.3.0b8
6000.4.0a3
6000.5.0a1
Issue ID
UUM-124869
Regression
No
URP Decal Projectors don't render when they are hidden in the Hierarchy, unlike other GameObjects
How to reproduce:
- Open the “URPDecalProjectorBug.zip“ project
- Open the “SampleScene“
- In the Hierarchy, toggle the visibility of the “Cube” (for reference). And observe that it does not disappear
- In the Hierarchy, toggle the visibility of the “Decal Projector” And observe the Game view
Expected result: The projected decal does not disappear
Actual result: The projected decal disappears
Reproducible in: 2022.3.68f1, 6000.0.61f1, 6000.2.8f1, 6000.3.0b8, 6000.4.0a3, 6000.5.0a3
Reproduced on: Windows 11 Pro (24H2)
Not reproduced on: No other environment tested
Notes:
- This reproduces in Play Mode as well, meaning this is more than just a cosmetic problem
- The decal changes visibility only after the Game view window is repainted
- The decal appears when the project is closed and reopened (until the visibility of any GameObject is toggled)
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
- [Tile Palette] Sprites not rendering when brush tool "Paint a filled box with active brush" is used for the first time
- Adding available Nodes with longer names in Fragment Context window overflow Fragment Context window in Shader Graph
- "Layer Palette Profile" Asset is automatically applied to the second Terrain but doesn't load any layers
- "Terrain Tools" shortcut conflicts with the Overlays shortcut by default
- Longer Shader Graph Property Reference names breaks VFX Graph Output Particle Node
Resolution Note (6000.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.
Resolution Note (6000.0.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.
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.