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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Add comment