# Editor crashes and can't recover level after FBX import

**URL:** <https://forums.unrealengine.com/t/editor-crashes-and-cant-recover-level-after-fbx-import/380940>\
**Category:** Pipeline & Plugins\
**Tags:** fbx-import-crash, unreal-engine, crash, FBX, bug-report, UE4, question\
**Created:** [January 5, 2017, 2:35am UTC](https://forums.unrealengine.com/t/editor-crashes-and-cant-recover-level-after-fbx-import/380940 "2017-01-05T02:35:16Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![kingfish3r](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@kingfish3r](https://forums.unrealengine.com/u/kingfish3r)\
**Post date:** [January 5, 2017, 2:35am UTC](https://forums.unrealengine.com/t/editor-crashes-and-cant-recover-level-after-fbx-import/380940/1 "2017-01-05T02:35:16Z")

</div>

Hoi UE4 community,

Am working on a level which includes animated skeletal mesh FBX files imported from Modo 10.2  
Setting them up in the editor and level sequence works fine, and there is no hint of a problem on previewing or saving the level.

When I try to re-open the level, it crashes the editor and appears unrecoverable. Other levels and assets within the project still work fine, but trying to open, rename or delete any of the skeletal meshes or associated physics assets in the content browser crashes the editor.

This has now happened a couple of times. Any help greatly appreciated. Have attached FBX file and crash reports.

Unreal version 4.14.1  
Modo version 10.2v1

FBX file  
bug reports

---

<div class="post-metadata">

**Author:** ![Tim\_Hobson](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@Tim\_Hobson](https://forums.unrealengine.com/u/Tim_Hobson)\
**Post date:** [January 5, 2017, 7:37pm UTC](https://forums.unrealengine.com/t/editor-crashes-and-cant-recover-level-after-fbx-import/380940/2 "2017-01-05T19:37:28Z")

</div>

Hi kingfish3r,

Thank you for the steps. I’ve submitted a ticket for this issue here: [Unreal Engine Issues and Bug Tracker (UE-40249)](https://issues.unrealengine.com/issue/UE-40249)

Currently, I don’t have any workarounds other than using your projects saved folder and see if you have a more recent version of the map before the corruption happened and moving that to your content browser.

-Tim