Search Issue Tracker
Not Reproducible
Votes
0
Found in
5.6.0f3
Issue ID
909038
Regression
No
Overwriting ShaderVariant Collection destroys its AssetBundle reference
Steps to reproduce:
1. Open QA attached project
2. Select "NewShaderVariants" file in Project view
3. Set "AssetBundle" to shaders or tescene or anything you create
4. Open Project settings -> Graphics and at the bottom of the window press "Save to assets..."
5. Overwrite "NewShaderVariants" file when saving
6. Select new "NewShaderVariants" file and observe the "AssetBundle" being set to "None"
Expected Result: When overwriting the ShaderVariant collection the AssetBundle reference would be preserved
Actual Result: The AssetBundle reference is destroyed, leaving "None" in its stead
Reproduced on 5.4.5p1, 5.5.3p1, 5.6.0f3, 5.6.0p4, 2017.1.0b4, 2018.4.27f1, 2019.2.21f1
Not reproducible: 2019.3.0a1, 2019.4.12f1, 2020.1.9f1, 2020.2.0b6
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Linux] Touch freezes in Player when any mouse button is clicked
- UnityEngine.Rendering.Volume.OnEnable() is called twice before OnDisable() creating multiple copies of the same volume when a volume is enabled right after Domain Reload when entering Play Mode
- Hinge Joint transforms are reset when toggling the "useMotor" property
- Motion Vector texture reports incorrect Mesh data when Mesh is coming from off-screen
- [macOS] Display flickers with bright colors when built Player uses 2 or more Displays
Add comment