-
-
Notifications
You must be signed in to change notification settings - Fork 251
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
Add optional bevy feature for reflection #467
Comments
Could |
There is no plan to add a |
Thanks for the update! I can understand that you don't want to propagate the feature everywhere :) |
Thank you for the info! We’ll keep an eye on this. Hopefully we can work something out at the |
Currently,
bevy_rapier
can (de facto) not be used in tandem with bevy dynamic scenes, since colliders cannot be serialized due to not beingReflect
. This means that save systems that would like to use the built-in bevy scene format need to clutter the graph with marker traits for which colliders were spawned how, which defeats the purpose of the dynamic scene as "just dump the entire world into a file and don't worry about it". Additionally, colliders cannot be inspected at runtime in editors, which is a pity if generating them dynamically.I propose adding an optional
bevy_reflect
feature to rapier that only derivesReflect
andFromReflect
for the types that aren't inbevy_rapier
and then add them to the type registry throughbevy_rapier
.If I get your okay @sebcrozet, I'll do this myself.
The text was updated successfully, but these errors were encountered: