Search Issue Tracker
Fixed
Fixed in 2021.3.14f1, 2022.1.23f1, 2022.2.0b15, 2023.1.0a11
Votes
0
Found in
2021.3.8f1
2022.1.13f1
2022.2.0b4
2023.1.0a6
Issue ID
UUM-12220
Regression
No
Some shader variants don't show up when "_vertex" is added to shader code
How to reproduce:
1. Open the attached user project
2. Click on the “NewShaderVariants“ shader (“Assets/NewShaderVariants“)
3. In the Inspector, click on the plus below the “Unit/Good“ shader
4. In the Inspector, click on the plus below the “Unit/Bad“ shader
Expected result: All shader variants show up
Actual result: Certain shader variants don’t show up
Reproducible with: 2021.3.8f1, 2022.1.13f1, 2022.2.0b4, 2023.1.0a6
Can’t test with: 2020.3.38f1 (Errors in Console)
Reproduced on: macOS (12.5)
Note: Differences between shaders “Good“ and “Bad“ is that in their code, line 14 is coded to "shader_feature_local" instead of "shader_feature_local_vertex"
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- NullReferenceExceptions are being thrown when saving a ScriptableObject with an array of a type with a CustomPropertyDrawer that uses TrackPropertyValue
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
- "Object.FindObjectsOfType<T>() is obsolete" warning is thrown when using "Transitions Plus" asset
Add comment