4.13 imported UCX collision broken
Build Type: 'Binary' build from the Unreal Launcher
Build version: 4.13
Detailed description of the issue: Testing collisions in the UE4 first person shooter sample project, the same .fbx with appropriately named UCX collision mesh (ie MyMesh and UCX_MyMesh exported as MyMesh.fbx) that works in 4.12.5 imports into 4.13 with a random number and configuration of missing or stretched collision geometry. Happening 100% of the time, although consecutive fresh imports and reimports of the same file results in a different set of missing or warped geometry. Collisions are simple sub-object cubes stacked end to end, normals are all facing outward, collision cubes are fully enclosed, no concave areas, geometry is not intersecting, and again, the same collision objects import correctly and function correctly in 4.12.5.
ETA: Uploaded .fbx as per Tim's instructions (thank you!)
Thanks for posting the FBX, Laurie! This appears to be an issue with 4.13 but not in the latest 4.14 internal build that I have. Looks like this has been fixed internally even though I couldn't find a ticket that referenced it in our system.
This should be fixed in the next major release. If you need these collision boxes it may be worth importing into an older release like 4.12 and migrating or sticking with 4.12 until this is resolved.
answered Sep 23 '16 at 03:27 PM
Tim Hobson ♦♦ STAFF
Follow this question
Once you sign in you will be able to subscribe for any updates here