How to cast_ray with latest bevy_rapier (0.29.0)

[dsellers22]

Hello, I'm a bevy/rust newby trying to migrate a project I worked on last year from Bevy 0.13 to Bevy 0.15 with bevy_rapier3d 0.29.

Rapier has apparently removed RapierContext as a resource and split it into components.

In many functions in my code I was fetching the RapierContext as rapier_context: Res<RapierContext>, which is apparently no longer valid.

From the migration guides in this changelog and the rapier docs it seems like I should be able to replace to rapier_context: Res<RapierContext>, by rapier_context: ReadRapierContext and move on with my day.

When I try that I'm told I'm told rapier_context.cast_ray() method does not exist.

If I instead use rapier_context: RapierQueryPipeline (which the code comments seem to say is responsible for things like ray_casting) the compiler tells me that it expects two additional arguments ( rapier_colliders: &RapierContextColliders and rigidbody_set: &RapierRigidBodySet)

I'm terribly confused. Can anyone tell me how to properly fetch whichever component of rapier I need to perform ray casts? Do I need to add these components to some entity first? Any help is appreciated.

Edit: Sorry if any of the above are really dumb questions. I spent a few weeks learning Bevy and making a fun project last year and I'm trying to refamiliarize myself with it.

[dsellers22]

Update: I've made some progress here, by bothering to notice that the rapier repo I linked above has an example of raycasting!

It seems I was missing a simple let context = rapier_context.single() which is the object that contains the cast_ray() method.

However I'm not seeing an error on the max_toi parameter: Expected 'Real' but found 'f32'

I don't understand this at all and I can't find any documentation on it. The raycasting example simply feeds it f32::MAX but even with that same argument the error persists.

rapier_context_systemparams.rs does specify that argument as "Real" but I don't know how to convert to this type from f32 or why the example doesn't mention it at all.

Help?

[dsellers22]

Another Update:
The 'Real' vs 'f32' error might just a false positive from the IDE! It does not appear in the error list when trying to compile. So this might be solved!

[dsellers22]

Indeed there are no more compiler errors, apparently RustRover is flagging it as a problem but the compiler knows how to make the conversion. Now I just have to deal with the other 50 errors and 127 warnings popping from trying to migrate engine version.

If anyone knows how to get RustRover to stop objecting to the use of an f32 in that parameter I'd still love to know.

Marking this question as answered. Good talk, everyone, thanks!