-
Notifications
You must be signed in to change notification settings - Fork 3
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
support xpbd collider gen #11
Conversation
@CrockAgile if you're able to take a look at the cfg feature stuff i'm trying to work out, I'd be glad! 😄 🙏 |
@Jondolf if you have any opinions on any of this goes down, i'd be glad to hear. would also be glad for pointers on using xpbd heightfeilds 😅 |
…rs downstream if nothing's enabled
okay all, I'm going to pull the trigger. I'll make some help wanted issues for helping me make the examples a little more engine-centric once things have been renamed and published |
context
approach
#[cfg(feature(...))]
or multiple files with some duplication and minimal need for#[cfg(feature(...))]
. at the moment i'm favoring the latter, it feels like it'll be easier to work with a specific engine in mind if you don't have to worry about bumping something for another one. It will change the API but I think it'll be basically a new crate so I'm not so worried about breaking changes, just don't want it too feel to tangled to use this stuff, it's supposed to make life a bit easier.remaining questions/issues to resolve before merging
i haven't figured out how to do native heightfields in xpbdi didn't spot convex polyline colliders in xpbd, are they known as something else or are they just not supportedi fumbled using polyline colliders in the xpbd example so switched to convex hullCollider::from(parry::SharedShape)
to support convex polyline colliders and heightfields with xpbd_2d