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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment