Search Issue Tracker
Won't Fix
Votes
0
Found in
2019.4.18f1
2019.4.19f1
Issue ID
1308374
Regression
No
Crash when project is reopened or upgraded
When reopening the attached project in Unity 2019.4.18f1or upgrading it to 2019.4.19f1 Unity will crash. This seems to be related to the metal API/Project Settings as if we use the automatic API option the crash does not happen. (Although the scene is rendered incorrectly)
Issue found while testing https://fogbugz.unity3d.com/f/cases/1305214/
Video Attached
Steps to reproduce
- Download project from https://bugs.unity3d.com/fogfiles/127xxxx/1277144_tmtcupo1qjtphtrb/case_1277144-Shapes.zip
- Open the project in 2019.4.18f1
- Open the shapes gallery scene.
- Save and close.
- Reopen with 2019.4.19f1, or 2019.4.18f1
Notice issue >> Crash! Bug reporter is fired.
Tested Platform: macOS 11.1 (20C69)
Reproducible: 2019.4.18f1, 2019.4.19f1
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
- "Shader warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
- AI Assistant breaks compilation of packages using System.Runtime.CompilerServices.Unsafe via auto-referencing
- Unity Hub checks the "Documentation" module by default on the 6.4 and 6.5 streams despite that it was unchecked with the previous installs
- Shortcut that toggles between Dopesheet and Curves Views in the Animation Window's Timeline is mislabed
- Property List Items Overlap onto the Property List's top edge when scrolling through a long Property List
Resolution Note:
so, if you first open with 2019.4.18f1 without the fix - it will generate bad shader code.
for these fixes we decided to NOT update shader importer version (they hit very specific edge cases and it doesnt sound important enough to force everybody to reimport their shaders).
so when you open in 2019.4.19f1 you STILL have bad shader code generated. You can solve this by clearing shader cache
either from menu "Assets->Clear Shader Cache" or manually killing Library/ShaderCache and Library/ShaderCache.db