Editor Lockup on FBX re-import after error

Development Pipeline & Plugins
, ,
1

Hey guys, I had the editor hard freeze which required a “EndProcess” from the taskmanager.

  1. Import new FBX file which errors out and fail import. I had a duplicate bone name on one of the fingers.

  2. Leave the editor open, re-export the fixed bone name FBX from Maya

  3. Repeat the import, but it asks you to overwrite the existing data, even though the asset isn’t in the content browser, must be still referenced in memory.

  4. I chose to overwrite anyways, it then pops up a window that says 100% Done!, but is locked up.

I always leave Maya and the Editor open while I make animation adjustments for a faster workflow and i usually don’t have any problems. It just seems if there was an error one time, it bugs out. I hope this helps.

Engine Version = Github 4.4.0

Thanks!

2

Hi Devero,

There are two issues I’m seeing here.

  1. You have a FBX issue with importing.
    and
  2. you have Maya open while UE4 is.

So my questions are:

If you have Maya closed are you still getting an issue with your FBX import since it says it imported successfully?

Are you able to reproduce this everytime, or even with different assets using the same repro?

Thank you!

Tim

3

Hi Tom,
Yes I verified with a different asset to reproduce the problem. The Maya being open is not a problem at all, i was merely stating that I work with Maya and UE4 open all of the time.

It is an easy problem to reproduce with a skeleton mesh.

1)Have a duplicate bone name for an error
2)Try importing the mesh, which errors out the editor (rightfully so)
3)Fix the file and try importing the fixed version.

This is where the problem occurs and hard freeze, if the editor was not shutdown before the re-import.

I hope that helps :slight_smile:

4

Thanks, Devero!

Using the duplicate bones I was able to get the crash and have submitted a bug report for this (TTP: 348347).

There is, however, no timeline for when this will be addressed. I will update this post once the fix has been implemented and verified.

Thank you!

Tim

5

Thanks! I’m glad I could help make the engine just a little better :slight_smile:

6

Hi Devero,

I wanted to update you on this. This has been resolved on our internal build now. I’m not sure if this will make it out with 4.5 but should be included with 4.6. Unfortunately, there is no timeline of exact release dates for these versions of the engine.

Thank you for you help in reporting this issue. It is appreciated. :slight_smile:

Tim