When updating a model with custom collision, UE4 (4.10.3) experiences weird buggy issues. Preface: I’m using Perforce source control in Unreal, the assets are checkout and writable even though using/not using source control doesn’t appear to make a difference. I’m using Maya 2016 and the 2014 FBX Exporter. I’ve also confirmed that using Max 2016 with FBX exporter does the same thing.
The model (when imported for the first time) appears correctly. The collision geometry is hidden and properly aligned:
However, if I updated the model in Maya 2016 and re-export it, UE4 updates the asset and does this to it:
The model now has a secondary element with the “WorldGridMaterial” applied to it. Attempting to remove this causes a fatal crash in editor. This only happens when reexporting the model once it’s been imported into UE4.
Another issue occurs when reexporting that causes the collision geo to scale by 0.1:
If I export the exact same model as a different name…UE4 imports it with all the correct settings. I’ve deleted the asset from within UE4, removed it from the file system, verified in Maya that the FBX export does in fact have all the properly named geometry and collision. However, it seems like UE4 has some sort of internal cache that’s remembering the original imported file and when updating the file and won’t accept the file changes and/or causes buggy issues.
