Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2018.4.X, 2019.4.X, 2020.1.X
Votes
0
Found in
2018.4
2018.4.20f1
2019.1
2019.2.0a1
Issue ID
1239074
Regression
Yes
Crash on VertexDeclarationD3D11::GetInputLayout when importing a broken FBX file
Reproduction steps:
1. Import the FBX file attached by the user to any project
Reproducible with: 2018.4.0f1, 2018.4.22f1, 2019.1.14f1, 2019.2.0a1
Not reproducible with: 2017.4.40f1, 2019.2.0a2, 2019.2.21f1, 2019.3.11f1, 2020.1.0b6, 2020.2.0a8
First lines of the stacktrace:
VertexDeclarationD3D11::GetInputLayout
GetMemExShader
GfxDeviceD3D11Base::SkinOnGPU
GfxDeviceWorker::RunCommand
GfxDeviceWorker::RunExt
Notes:
- Spams a lot of "Invalid AABB aabb" errors and "Assertion failed on expression: 'IsFinite(outDistanceAlongView)'"
- In cases where it didn't crash, it pops out a lot of errors like in case 1063880
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0a21, now the Editor produces proper errors instead of crashing
Resolution Note (fix version 2020.1):
Fixed in 2020.1.5f1
Resolution Note (fix version 2019.4):
Fixed in 2019.4.10f1
Resolution Note (fix version 2018.4):
Fixed in 2018.4.27f1