What is the naming convention for collisions with FBX for multiple meshes?

[sensei_lionheart]

I have an FBX file with 4 separate Static meshes and everything imports correctly except my UCX collision boxes. The first model imported receives all of the collision boxes for the other 3 models and I can't seem to correct it. I've tried some creative naming, grouping, parenting, etc, but it doesn't work.

I hear there is a specific naming convention for getting this to work but I can't seem to figure it out. The collision reference page on the UDN is all assuming we're importing one at a time with ASE, which is super inefficient.

Does anyone have suggestions?

[sensei_lionheart]

So the FBX Guide on UDN says you're supposed to use UCX_$(MESHNAME)_$(CollisionModelSuffix) but that doesn't seem to fix the collision problems. I have a model named SM_MessHall_CoffeeVender and I've tried every possible structure of naming I could:

UCX_$SM_MessHall_CoffeeVender_$Collision
UCX_$MessHall_CoffeeVender_$Collision
UCX_$(SM_MessHall_CoffeeVender)_$(Collision)
UCX_$(MessHall_CoffeeVender)_$(Collision)

There aren't any typos but it won't spread the collision to any models but the first one in the list. I'm really at a loss as to what I'm doing wrong. Ugh!

[mslaf]

What about UCX_SM_MessHall_CoffeeVender_Collision?

[sensei_lionheart]

It doesn't work either. Its really bizarre. Now I can't seem to get any collision meshes to show up in my models. It's really aggravating. I'm close to just using ASE instead of FBX, which is too bad because FBX seems like a superior option in theory.

[m4dcow]

Do
UCX_CoffeeVender_01
UCX_CoffeeVender_02 etc...
and the mesh name would be "CoffeeVender"

It is using the underscores as delimiters so in the example of "UCX_SM_MessHall_CoffeeVender_Collision" it's probably looking for a mesh named SM and can't find it.

[sensei_lionheart]

Thank you so much! That was it. Now that I know that, I can really take advantage of FBX. Its so amazing how efficient FBX is.