So an HDA gets the mesh data from Unreal 5.3, including collision. In Houdini 20 I separate the collision prims from the rest, process the rest then merge the collision prims back before the output node. When the mesh arrives back to Unreal it does have colliders but they are a bunch of unrecognizable triangles stretched to infinity.
As a debug step I instantly passed the input data to the output and the result is the same. The incoming mesh has proper UCX collisions.
Messy UCX collision output
1009 2 1-
- ZoltanE
- Member
- 18 posts
- Joined: July 2013
- Offline
-
- ZoltanE
- Member
- 18 posts
- Joined: July 2013
- Offline
-
- Flakked
- Member
- 11 posts
- Joined: Feb. 2020
- Offline
Just ran into this issue myself today. I found a workaround, and since this was one of the few posts about it that I could find online, I'll just share it here:
I found that if I renamed the collision group from "collision_geo_simple_ucx0" to "collision_geo_ucx0" it worked perfectly.![](/static/djangobb_forum/img/smilies/smile.png)
According to the Unreal Houdini Engine documentation page, this format invokes the "Complex_Collisions" convex collider geometry generation (invisible).
More info can be found here [www.sidefx.com].
I found that if I renamed the collision group from "collision_geo_simple_ucx0" to "collision_geo_ucx0" it worked perfectly.
![](/static/djangobb_forum/img/smilies/smile.png)
According to the Unreal Houdini Engine documentation page, this format invokes the "Complex_Collisions" convex collider geometry generation (invisible).
More info can be found here [www.sidefx.com].
Edited by Flakked - Jan. 19, 2024 15:28:28
-
- Quick Links