You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Sep 24, 2026. It is now read-only.
RapierContext has various methods that can be used to query the simulated world. Problem is - you never actually get a value (or even reference) of the type RapierContext. Bevy queries don't return the item itself - instead they return its QueryData::Item. In our case - it's RapierContextItem, which is generated automatically by the #[derive(query::QueryData)] and does not have any of these methods, making them unusable.
If these methods were implemented on RapierContextItem instead of RapierContext (which should be doable even if RapierContextItem itself is generated by a macro) then Query<&RapierContext> would be usable (currently it isn't)
RapierContexthas various methods that can be used to query the simulated world. Problem is - you never actually get a value (or even reference) of the typeRapierContext. Bevy queries don't return the item itself - instead they return itsQueryData::Item. In our case - it'sRapierContextItem, which is generated automatically by the#[derive(query::QueryData)]and does not have any of these methods, making them unusable.If these methods were implemented on
RapierContextIteminstead ofRapierContext(which should be doable even ifRapierContextItemitself is generated by a macro) thenQuery<&RapierContext>would be usable (currently it isn't)