Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.4.X, 2020.1.X
Votes
0
Found in
2019.3
2019.3.2f1
2020.1
2020.2
Issue ID
1244648
Regression
No
ShaderVariantCollection.Contains returns the wrong result for a variant after removing an unrelated variant from the collection
How to reproduce:
1. Open user-submitted project (ShaderVariantCollectionUPR813031.zip)
2. Open the SampleScene
3. Select Resources/NewShaderVariants
4. Remove the Normal_SUNDISK_SIMPLE by clicking the minus symbol button
5. Add the Normal_SUNDISK_SIMPLE again via the plus symbol button
6. Enter Play Mode - see the Console output for ShaderVariantCollection.Contains(true)
7. Add the Normal_SUNDISK_HIGH_QUALITY via the plus symbol button
8. Enter Play Mode - see the Console output for ShaderVariantCollection.Contains(true)
9. Remove the Normal_SUNDISK_HIGH_QUALITY via the minus symbol button
10. Enter Play Mode and see the Console output
Expected result: ShaderVariantCollection.Contains returns True
Actual result: ShaderVariantCollection.Contains returns False
Reproducible with: 2019.3.13f1, 2020.1.0b9, 2020.2.0a11
Not reproducible with: 2018.4.22f1
Could not test with: 2017.4.40f1(package unavailable)
Reproducible with package versions: 5.7.2, 9.0.0 - preview.14
Not reproducible with package versions: 4.10.0 - preview
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
- Errors are thrown after redoing Nested Prefab Variant creation
- Documentation Link does not work when the "VFX Condition" question mark button is clicked
- Documentation Link does not work when the "Spawn State" question mark button is clicked
- Darker lighting in Build when disabling SSAO at runtime
- Animation glitches when using animation layering with base layer transition interruption
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0a19
Resolution Note (fix version 2020.1):
Fixed in 2020.1.0f1
Resolution Note (fix version 2019.4):
Fixed in 2019.4.6f1