Send to Unreal - combine child mesh option bug with collisions

[Mebebonk]

• Send to Unreal
• So to be honest I do not realy understand what is happening right there but noneless. I've created basic blockout for level, added walls floor etc. with panels and added collision utilizing UBX prefix. Nothing appeared to be working. UE5 (to be exact) told that he did not find any node (or smth like that). I've tried renaming bouth object and data blocks and nothing helped. Long story short I've found solution: uncheck "combine child meshes". And I do not realy understand why. UBX and object itself had no parenting w/ each other. Well yeah, the question is rn: is it intended "feature" or just a bug? If it is intended so wouldn't it mean that I cant have multi-obj mesh, i.e nondistructive base, and at the same time have any collision (obv I'm talking about "in-Blender" collision, obv you can add collision later in ue but still)?

[james-baber]

Hey @Mebebonk can you make a basic example and post a picture of the Export collection hierarchy with combine child meshes on and the collision import not working and then with it working and combine child meshes off?

[Mebebonk]

@james-baber As easy as it is

and then

.blend file CollisionBug.zip

[iigindesign]

Hi @Mebebonk, this issue should now be addressed with the 2.1.3 release. When combine child meshes is turned on, meshes that are directly under the export collection should now be importing to UE as they normally should along with any meshes under an empty or armature type parent object that will be combined. Feel free to open this issue again if you experience further problems.