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

Expose mesh indices in intersection data #77

Closed
wants to merge 1 commit into from

Conversation

Dig-Doug
Copy link

@Dig-Doug Dig-Doug commented May 2, 2023

Note: I also ran cargo fmt, which reformatted src/primitives.rs since it used carriage returns.

@Dig-Doug
Copy link
Author

Hi @aevyrie, is this PR something you'd consider accepting?

@aevyrie
Copy link
Owner

aevyrie commented May 22, 2023

Yes, but I need some free time to review this. I'm not sure how much data we should stuff in this struct, or just return the indices and make the user look up things like vertex positions and normals.

@Dig-Doug
Copy link
Author

No problem. I'm using this data in tandem with bevy_mod_picking. I was looking at the other backends and saw that rapier exposes the data using a struct called feature id.

Maybe we could figure out the best way to expose the intersection data from rapier in the HitData and then work backwards for this backend?

@brookman
Copy link

Just saw this PR. I have opened a similar PR which exposes just the indices. See: #107

@aevyrie
Copy link
Owner

aevyrie commented Feb 18, 2024

Closed in favor of #103.

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

Successfully merging this pull request may close these issues.

3 participants