Closed LiamGallagher737 closed 11 months ago
This is happening because an entity is marked as a raycast target, but it does not have a supported mesh to raycast against. The solution would be to remove the raycast components (RaycastMesh::<MyRaycastSet>
) from entities that should not have them. Maybe this is an upstream issue with bevy_editor_pls?
The issue only happens when using bevy_rapier's debug lines which I highly doubt would have that component.
The filter here ensures that only entities with that component can be raycasted against: https://github.com/aevyrie/bevy_mod_raycast/blob/193cf2a58f594fa0ec5ff14ed5aa6d3af532967f/src/system_param.rs#L72
I am using the latest commit of the
bevy_editor_pls
crate. When I add bevy_rapier'sRapierDebugRenderPlugin
to my app my console gets spammed with the following error.I understand the bevy_rapier's debug lines aren't using triangle lists but why does it have to spam the console, can't it just skip it?