Search Issue Tracker
Fixed in 2020.2.X
Votes
0
Found in
2018.4
2019.4
2019.4.16f1
2020.1
2020.2
2021.1
2021.2
Issue ID
1304582
Regression
No
Some Shader Requirements don't have a C# enum representation
How to reproduce:
1. Open the attached '1304582.zip' project
2. Build the project (File > Build and Run)
3. In the Unity Editor open Window > Analysis > Project Auditor
4. In the Project Auditor window select 'Analyze'
5. Open the 'Shaders' tab
6. Expand the 'Actions' section and select 'Inspect Shader Variants'
7. Click on the 'Expand All' button located at the bottom of the Shader Variants window
8. Observe the 'Requirements' column
Expected result: All Shader Requirements are displayed as meaningful strings
Actual result: Some of the Shader Requirements are displayed as numerical values
Reproducible with: 2018.4.30f1, 2019.4.18f1, 2020.1.17f1, 2020.2.2f1, 2021.1.0b2, 2021.2.0a1
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
- Unnecessary modifications clutter the Scene when using a RectTransform driven by a LayoutGroup in a Prefab
- Files in the target folder are deleted without a proper warning when building an iOS project
- Character animation freezes when toggling animator on/off in a coroutine
- Certain textures are incorrectly marked in the render pass list when observed through Render Graph Viewer
- "Assertion failed on expression" error occurs when multiple Animation Components are instantiated after changing the Culling Type
Resolution Note (fix version 2020.2):
Fixed in 2021.2.0a4