Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MAXAR_collision_geometry #2087

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

erikdahlstrom
Copy link

A draft extension for being able to associate collision meshes with meshes inside a glTF.

Copy link
Contributor

@donmccurdy donmccurdy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Had two clarifying questions here for my own curiosity, but not meant as concerns with the extension! :)

@rsahlin
Copy link

rsahlin commented Jan 14, 2022

Hi @erikdahlstrom - great that you are looking into collisions :-)

We are also very interested in being able to use meshes for collision, for many usecases a decimated version (LOD) will suffice but for some cases these may not be convex hulls.

Our ideal usecase would be to convert to convex hulls on the client side at load-time, is this something you have looked into and considered?
For this we may use some version of HACD, however at the moment this seems to be somewhat too time consuming to do on the client side.

Just out of curiosity - have you considered simply adding the boundingbox reference as metadata (extras) to the visible mesh?

ps
Another way of doing boundingboxes could be to put the non visible collision meshes as a node hierarchy in a separate scene.
Ie, scene 0 contains all visible nodes and scene 1 contains collision meshes.
ds

Best regards
/Richard

@aaronfranke
Copy link
Contributor

OMI has been working on an extension called OMI_collider which allows glTF files to define collision geometry. It also includes primitive shapes such as boxes and convex hulls, so it's a superset of MAXAR_collision_geometry in terms of supported features. Also note MAXAR_collision_geometry has some weird limitations like being attached to meshes, OMI_collider has no such restriction.

OMI_collider is progressing nicely, it has been implemented in Godot Engine (both import and export), it has full schemas, example files, and a validator implementation. OMI_collider likely makes MAXAR_collision_geometry obsolete, though I'd love to hear your feedback if OMI_collider won't fork for a particular use case you have.

@erikdahlstrom
Copy link
Author

I'm going to refer to @bjornblissing for this, as I'm no longer with Maxar.

From memory, we shipped some content using this extension, so this is documenting that snapshot. However, I don't see why changes couldn't be made in the future (or now even), or that another suitable alternative for colliders is found that is acceptable to Maxar. However, I can't speak for Maxar.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants