Search Issue Tracker
Fixed
Fixed in 2022.3.70f1, 6000.0.63f1, 6000.2.14f1, 6000.3.1f1, 6000.4.0b1, 6000.5.0a2
Votes
0
Found in
2021.3.53f1
2022.3.64f1
6000.0.52f1
6000.1.9f1
6000.2.0b8
6000.3.0a1
6000.4.0a1
6000.5.0a1
Issue ID
UUM-110693
Regression
No
Console Message lacks information when Render Queue is changed out of bounds in the Inspector
How to reproduce:
1. Create and open a new project
2. Create a new Material
3. Click on the newly created Material and go to the Inspector window
4. Change “Render Queue” under Advanced Options from “2000” to “4000”
5. Observe the Console
6. Double-click on the Console message
Expected Result: The message specifies the Material responsible for triggering it and links to the corresponding Material
Actual Result: The message does not identify the Material causing it to appear, and clicking on the message does not link to the corresponding asset
Reproducible with: 2021.3.53f1, 2022.1.0a4, 2022.3.64f1, 6000.0.52f1, 6000.1.9f1, 6000.2.0b8, 6000.3.0a1
Reproducible on: MacOS 15.5 Silicon
Not reproducible on: Not tested in other environments
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment