Runtime Mesh Component

[a_prototype]

@;727295

Not quite sure what you’re getting vs trying to get. You should be able to turn collision on for any/all/none of the sections and it should just work. The caveat to that though is there’s no good way to tell which side you’re colliding with from a ray trace or whatever. That is something that’s coming, but not yet. Just to make sure you’re clear, the CreateCollision flag on CreateMeshSection creates a trimesh collision shape, that only works if UseComplexAsSimple is on for the RMC (most like it is since that’s default) and you don’t try to turn on “SimulatePhysics”. The only time you should have to manually tell it to CookCollisionNow is if you want to query it with something like a ray trace in the same frame as creating it, by default collision won’t update until the following frame.

Thank you for your explanation. It works now. Interestingly, i simply had to delete and recreate the ‘Add RMC’ node to get the collisions to work properly.

Is there a way to READ/FETCH the vertex/normal/uv etc data from a mesh section?

And is there a comfortable way to have multiple mesh sections share a set of triangles?