Search Issue Tracker
Fixed in 2020.1.X
Votes
0
Found in
2018.3.0a1
2018.3.6f1
2019.1.0a1
2019.2.0a1
Issue ID
1136315
Regression
No
Misleading error message about serialization when you open a project with a corrupted scene file
To reproduce:
1. Open attached project
2. See the error in the console: Failed to load 'path/SceneWithErrorOnYaml.unity' because it was serialized with a newer version of Unity. (Has a higher SerializedFile version)
3. If you look at the "Assets/Scenes/SceneWithErrorOnYaml.unity" now you'll see that Unity created a "new" version of the file.
Reproducible with: 2018.3.0a1, 2018.3.9f1, 2019.1.0b7, 2019.2.0a8
Not reproducible with: 2017.4.23f1
Actual results: errors about the content having a higher SerializedFile version
Expected results: an error message that pointed out the real problem (not misleadingly saying that file was saved with newer version)
Fixed: 2020.1.0a3
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
Add comment