Collider debug lines are rendered behind the model

[MatrixDev]

For some reason collider debug lines are always rendered behind geometry. This is especially bad when "ground" mesh is present because it completely covers debug lines.

Regular plugins init:

.add_plugin(RapierDebugRenderPlugin {
    enabled: true,
    always_on_top: true,
    ..default()
})

Adding rapier stuff when scene is loaded (in my case I need to add it only after snene is available):

commands.entity(entity)
            .insert(RigidBody::Fixed)
            .insert(Collider::cuboid(1.0, 0.5, 1.0))
            .insert(ColliderDebugColor(Color::CYAN))
            .insert(SceneBundle { scene: hull.default_scene.clone().unwrap(), ..default() })

And here is a result:

Screen.Recording.2023-03-17.at.13.40.09.mov

[MatrixDev]

Here is an example when terrain is present:

out.mp4

[devmitch]

Looks like this is already fixed as of #340 , so you could use the master branch until 0.22 is released.

[toolness]

As far as I can tell, @devmitch is right. #366 was filed as an attempt to fix this issue but I can't find any difference between the current master branch and that PR. For more details on my testing, see #366 (comment).

So my recommendation (unless my testing is missing some kind of edge case that #366 addresses) is to close both this issue and #366.

[toolness]

That said, always_on_top not working does seem like a fairly major bug, so maybe a new release should be made soon? Or perhaps #340 can be back-ported and a 0.21.1 bugfix release can be made?

[toolness]

Actually, wait... something dreadfully wrong is happening with 0.21.0, even when always_on_top is false.

I've borrowed from the "getting started" instructions and added a falling bouncing ball to my project, which already has some 3d scenery.

On the latest master branch, with always_on_top disabled, I can see the bouncing ball in full view as it falls to the ground:

Once it lands and stops bouncing, it's partially obscured by a barrel:

On 0.21.0, however, this physics object initially appears behind the wall as it falls to the ground, and once at rest, it seems to disappear entirely (even when I move my camera past the wall the ball was behind). Here's a screenshot as it's falling to the ground:

So it seems that more than just always_on_top has been fixed since 0.21.0. I imagine a new release would be much appreciated by rapier newcomers like me!

[Ynng]

So it seems that more than just always_on_top has been fixed since 0.21.0. I imagine a new release would be much appreciated by rapier newcomers like me!

You mean broken?

I'm getting the same behavior on 0.21.0, where the debug renders go behind everything else, even in cases where it is closer to the camera.

[toolness]

Update: since the release of bevy_rapier 0.22 (specifically #380), always_on_top is no longer available because Bevy 0.11's new Gizmos system is being used to draw the debug mode.

To achieve the same effect, it looks like we can use the depth_bias property of GizmoConfig, e.g.:

app.insert_resource(GizmoConfig {
    depth_bias: -1.0,
    ..Default::default()
})

That said, I'm experiencing some weird bugs, e.g. when a collider's gizmo line extends from off-camera to on-camera, it sometimes isn't drawn... Not sure if this is a bug in bevy_rapier or bevy's new gizmo system.

[Vrixyz]

I suspect that's fixed now ? Keeping open until verified.