👽 tresjs-rapier: models handling improvement

[alvarosabu]

Migrated from Tresjs/rapier#127 - Originally created by @JaimeTorrealba

---

Description

The current implementation is different from R3F, as you can see, the model is treat as a group (I personally prefer this approach) is best performance and cover most of the cases, BUT, not all for some specific cases maybe this is not a viable solution.

R3F handling the models in which each geometry has a different RigidBody/Collider:

I don't know if this will create future problems for uses cases or the people can workaround them. I don't know if this makes joints cases when models more difficult.

Suggested solution

Proper discussion and research

Alternative

Just by the record, I like the current approach (but maybe I'm thinking in just low poly games)

Additional context

No response

Validations

• I agree to follow this project's Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.

[tresjs-cube-bot[bot]]

Hey @alvarosabu! 🧊

This looks like a feature request — awesome ideas belong in
Discussions
where the community can upvote and discuss!

Please consider opening a discussion there instead.

🤖 I'm an AI assistant and can make mistakes.

[JaimeTorrealba]

Maybe we can have a props to handle both cases? @Neosoulink

[Neosoulink]

Hm... I think it might be a good alternative, yes!

Something like:

<RigidBody collider="cuboid" :individual="true">
	<BallCollider :args="[1, 1, 1]" :position="[0, 15, 0]" />

	<TresMesh :position="[0, 15, 0]">
		<TresTorusGeometry />
		<TresMeshNormalMaterial />
	</TresMesh>
</RigidBody>

Note the :individual="true" is just a name I shared, we can find a better one 💡