Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.4.X
Votes
8
Found in
2019.3.15f1
2020.1
2020.2
Issue ID
1251734
Regression
Yes
Launching the Editor crashes on GetRenderPipelineScript when the project contains a Shader Variant Collection
How to reproduce:
1. Download the attached project named "Case_1251734"
2. Observe that the Library folder is deleted
3. Launch the project - it will start up normally
4. Close the project and try to re-open it
Expected result: Project launches without issues the second time
Actual result: Project silently crashes upon launch
Reproducible with: 2019.3.15f1(7.3.1), 2019.4.0f1(7.3.1), 2020.1.0b11(8.1.0), 2020.2.0a13(9.0.0-preview.14)
Not reproducible with: 2019.3.1f1(7.1.8), 2019.3.14f1(7.3.1)
Could not test with: 2018.4.23f1(Could not downgrade the project due to compilation errors)
Workaround: Deleting the SourceAssetDB file in the Library folder will allow the project to launch(Must be done every time before launching)
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (fix version 2020.1):
Fixed in - 2020.2.0a16
Resolution Note (fix version 2020.1):
Fixed in - 2020.1.0b15
Resolution Note (fix version 2019.4):
Fixed in - 2019.4.3f1