Search Issue Tracker
In Progress
Under Consideration for 2022.3.X, 6000.0.X, 6000.2.X, 6000.3.X, 6000.4.X
Votes
1
Found in
2022.3.68f1
6000.0.62f1
6000.2.12f1
6000.3.0b9
6000.4.0a4
Issue ID
UUM-126301
Regression
No
Shader Variant Collection Asset UI is hard to read when multiple Shaders and keywords are added
Reproduction steps:
1. Create a new project
2. Create > Shader > Shader Variant Collection
3. Click on newly created Asset
4. Add several Shaders in the Inspector
5. Add keywords to the Shaders by pressing “” button
6. Observe the Inspector
Actual result: It's difficult to distinguish which "" and "-" button belongs to which Shader or keyword due to unclear UI separation
Expected result: Each Shader is separated and it's easy to understand which button belongs to which Shader or keyword
Reproducible with: 2022.3.68f1, 6000.0.62f1, 6000.2.12f1, 6000.3.0b9, 6000.4.0a4
Reproduced on: Windows 11, macOS Sequoia 15.4 (M4)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- URP Realtime reflection probes do not update when RenderProbe() is being called once per second
- Addressable terrain shader variants are stripped from the Player
- [iOS] Debug.Log() appears as <private> in Console app
- UI stays in the background when it is disabled in simulator
- A wrong log file is attached when project is launched with a "-logFile" command line argument
Add comment