Search Issue Tracker
Active
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
- [Android] AssetBundle loading performance degradation when loading from a local Assetbundle
- [iOS][Android] Reflection with Generic Class returns unexpected values
- Shader Variant Collection Asset UI is hard to read when multiple Shaders and keywords are added
- Regression for "WebGL build is missing "malloc" and "free" functions when passing "-sERROR_ON_UNDEFINED_SYMBOLS=0" to emscriptenArgs"
- Resetting Quality Levels in Project Settings adds new Quality Levels instead of restoring default ones
Add comment