Search Issue Tracker
Fixed in Unity 2018.2
Votes
21
Found in
2017.3.0p1
Issue ID
984070
Regression
Yes
Editor crashes when loading a mesh asset with 'Mesh Compression' from an assetbundle
The crash happens if there's both an asset with 'Mesh Compression' enabled, and any other asset
Steps to reproduce:
1. Download and open the project
2. Click `Crash Repro->Build Bundles`
3. Click `Crash Repro->Load Assets` or `Crash Repro->Load All Assets`
Expected result: assets are loaded normally
Actual result: editor crashes
Reproduced on 2017.3.0a5, 2017.3.0p1, 2018.1.0b3
Not reproduced on 2017.2.1p1, 2017.3.0a1, 2017.3.0a4
Regression introduced in 2017.3.0a5
Verified FIXED 2018.1.0b5, 2018.2.0a3
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
- [Block] Position (Cone) block doesn't work when Radius 0 and Radius 1 are set to the same value
- [Blackboard] Range slider doesn't update value to click position
- [Inspector] Can't multi-select change the Asset template or the seed when different effects are selected in the hierarchy
- Tracked pose driver - Lost tracking bug
- [Terrain][LWRP] LOD popping of Terrain quad nodes with instancing enabled
rryanSC
Nov 01, 2018 19:09
We just ran into this same issue in 2018.3.0b8. After exhausting a bunch of other theories, I tried checking for this "fixed" bug and it resolved the issue. The game (or editor) would crash whenever we loaded a mesh from an asset bundle that had medium mesh compression enabled. We were also getting loads of assertion failures in the logs (Assertion failed on expression: 'meshVD.GetDataPtr() == NULL'). Disabling mesh compression, while not ideal, got rid of the assertions and the crash.
Colin49
Jan 24, 2018 15:54
We have also run into this issue. In the editor we crash with a [Position out of bounds!] error. But when we run the code on an iOS device we still get the same error message/stack trace but we don't crash. Instead, meshes simply don't render on the device. We did some digging around and the meshes are empty (no verts). Crossing our fingers for a timely fix as we are trying to move our project to 2017.3.
Reproduced on 2017.3.0f3.
MikeHergaarden
Jan 17, 2018 10:53
Top prio and completely breaking 2017.3+for us.
Every (Steam) PC game should use asset bundles and mesh compression, so this must affect all PC games?
Please double check how this has passed unit testing since this is really basic.