Search Issue Tracker
Fixed in 2023.1.0a25
Fixed in 2022.2.X, 2022.2.14f1, 2023.1.X
Votes
0
Found in
2022.2.7f1
Issue ID
UUM-26865
Regression
Yes
Material override is not applied to either GameObject or Entity depending on the value of the Queue property in the RenderObject filters
Reproduction steps:
1. Open the “Bug_URP-RenderObject-Entity-GameObject“ project
2. Open the “SampleScene” scene
3. Observe the colors of the two cubes in the Scene view
Expected result: Both cubes are green
Actual result: “CubeGameObject” is green, “CubeEntity” is grey
Reproduced in: 1.0.0-pre.15 (2022.2.7f1)
Not reproduced in: 0.17.0-preview.42 (2020.3.45f1), 0.51.1-preview.21 (2021.3.18f1)
Could not test in: 1.0.0-pre.15 (2023.1.0b4, 2023.2.0a2) (Entities is not compatible)
Reproduced using: macOS 13.0.1 (Intel), Windows 10 (by user)
Notes:
1. Also reproduced in a Standalone Player
2. Whether the GameObject or the Entity is green depends on whether the Queue property in “Assets/Settings/URP-HighFidelity-Renderer” is set to Opaque or Transparent respectively
3. This is costing extra GPU resources since now it is needed to override 2 times: once for GameObjects, and once for Entities
4. Related forum thread: https://forum.unity.com/threads/render-objects-material-override-with-entities-in-urp.1383141/
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
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
Resolution Note (fix version 2023.1):
Fixed in 2023.1.0a25
Resolution Note (fix version 2022.2):
Fixed in 2022.2.14f1