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
- APV data is sometimes incorrectly loaded from multiple baking sets when loading a scene
- GC Alloc spikes occur when calling UnityEngine.Resolution and UnityEngine.RefreshRate with Equals() and GetHashCode()
- Type error is thrown when a new ComputeShader is instantiated after destroying previous ComputeShader
- APV data becomes incorrect when reselecting the currently active Baking Set
- Launch screen image exceeds the screen bounds on IPad when building for iOS
Resolution Note (fix version 2020.2):
Fixed in 2021.2.0a4