we are testing the flow from Revit to Unity and there seems to be some kind of grouping logic on Revit’s end? And it is affecting the importing result in Unity.
I have disabled grouping with all available options:
As you notice from the bounding boxes, these are treated as 1 object, and this is an issue for us. Is there any setting that prevents such groupings? Ideally they would be individual parts. The first one is a small stair, and the second is a large area, and they seemed to be grouped by type rather than proximity. I am not sure how to go about this.
If you take a look at the structure of the converted elements. You can see that stair railings are separate child objects. (Revit calls this hosted elements)
So, I’m not really seeing the “grouping” behaviour you’re describing.
I’m able to apply the MeshColliderComponents to the child objects independently from the stair its self. And (while you may need to uncheck Convex under the Mesh Collider inspector properties) I’m getting good collider results this way.
Thanks Jedd, it seems a lot of it was due to marking convex as true somehow. We will do more testing but i think we can consider it resolved right now.
