I have a skeletal mesh of a bus. To use custom physics assets I imported the mesh as static mesh too. The Static Mesh imported the convex physics objects successfully (The “UCX_*” meshes). Then I tried the “Copy Collision from Static Mesh” Button in PhAT. The convex objects copies successfully but with some issues:
The imported Convex Meshes are too large. The reason could be: We’ve modeled the bus in 3ds Max im meter and exported it with unit conversion to cm. In most cases all is fine but here it seems that the scaling is applied a second time when copying from Static Mesh to PhAT.
(Feature Request) The scaling of physics Meshes in PhAT is very painful and inaccurate with the scaling tool. Please give us a text field to type the Scaling (…and Location… and Rotation)
After scaling the physics mesh (painfully) all works fine but every time I open the Bus in the Editor (skeletal mesh or Blueprint) the camera is miles away fromt the Bus. It seams that the Bounds of the mesh doesn’t uses the scaling of the physics mesh.
When showing the Collision Meshes in Editor with Alt+C then the shown Mesh is very tiny.
I included a link and notes regarding the scaling applied twice when copying from Static Mesh to PhAT and the bounds not using the scale of the physics mesh.
This is a multi part issue that may or may not be related. Our developers will look into this and determine how and why this could be happening.
I have having exactly the same issue. The issue of the oversized custom UCX asset when imported into the PHAT Editor was not there in UE4 Version 4.5.
The custom UCX collison object is of the correct scale when viewed in the static mesh editor, but when imported into PHAT it is 100x too big - and it is impossible to scale it down with the tools provided - as the original poster desribed. Hope this gets fixed in 4.12. Cheers!
Hi again. I have found a work around for this issue that may be helpful. Only thing is I am using Blender 3D, not Max.
I was having exactly the problem that User37337 was having - that of a massively upscaled custom UCX when brought into the PHAT editor - experienced all the symptoms he described.
I was able to solve this issue by changing the Export Scale of the Target Skeletal Mesh from 1 to 0.01 and scaling the actual skeletal mesh up 100x inside Blender 3D. After then reimporting the Skeletal Mesh, creating a new Physics Asset for it and copying the custom UCX collision from a static mesh, the UCX collision was brought into PHAT at the correct scale, solving the issue.
I suspect the original problem was caused by PHAT reading the bones in my Skeletal Mesh as 100x too big. Scaling down the skeletal mesh in the FBX exporter (while scaling up in Blender) I was able to correct the bone size, while maintaining the correct skeletal mesh size.
I have found a work around for this issue that may be helpful. Only thing is I am using Blender 3D, not Max.