Search Issue Tracker
Fixed in 2017.1.X
Votes
0
Found in
2017.1.0a2
Issue ID
888688
Regression
Yes
Splashscreen resources fail to load on 2017.1.0a2, causing FatalErrorMsg to be called
Steps to reproduce:
1. Create a new project OR open any project
2. Build for any platform with splashscreen turned on
3. Run it
Expected result: player launches and runs
Actual result: FatalErrorMsg is called with message "The file 'D:/DOWNLOADS/new-project/new-stan/standalone_Data/Resources/unity default resources' is corrupted! Remove it and launch unity again!"
Reproducible with: 2017.1.0a2
Not reproducible with: 5.5.2f1, 5.6.0b11
Reproducible with: all configurations and platforms.
(output and callstack attached)
This is a serious issue because on some platforms FatalErrorMsg actually crashes intentionally.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- UI Overlay Image gets darker on each Camera when multiple Cameras are used
- Assertion failed on expression: 'scriptedImporterClass == SCRIPTING_NULL error when opening the standalone profiler window
- Disabled assets in Import Unity Package window aren't tracked but count as being selected by user
- [Windows] Crash on GetManagerFromContext when video is playing and creating High Definition 3D Projects after FMOD failed to switch back to normal output Error appeared
- GC Alloc produced when adding items to MultiColumnListView with Auto Assign Binding
Add comment