Search Issue Tracker
Won't Fix
Won't Fix in 2022.2.X
Votes
0
Found in
2022.2.4f1
Issue ID
UUM-27814
Regression
No
Decal layers are rendered differently in Build than in Game window
Reproduction steps:
1. Open the attached “Webgl Decal Projectors.zip“ project
2. Open “SampleScene” scene
3. Build and Run the project
4. Observe the screen
Expected result: GameObjects in Build and Game window are rendered the same
Actual result: GameObjects in Build and Game window are rendered differently
Reproducible with: 14.0.5 (2022.2.4f1)
Not reproducible with: 12.1.10 (2021.3.19f1), 14.0.6 (2022.2.7f1), 15.0.4 (2023.1.0b4), 16.0.0 (2023.2.0a2)
Could not test with: 2020.3.45f1 (Due to “URP-HighFidelity-Renderer is missing RendererFeatures” error in Console window)
Fixed in: 14.0.6 (2022.2.5f1)
Reproduced on: macOS Monterey 12.6 (Intel), Windows 11
Note: In WebGL Build every GameObject is rendered differently than in the Game window but in Standalone Build only one of the GameObjects is rendered differently
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
- 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
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note:
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 because the bug is resolved in a newer version of Unity.
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.
Resolution Note (2022.2.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 because the bug is resolved in a newer version of Unity.
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.