Anchor indicator is rendered for all cameras.

[ThierryBerger]

I was surprised to see the anchor indicator in the other cameras than the current being moved.

It's reproducible easily on the split screen example.

[aevyrie]

This is a limitation of bevy's gizmos. There is no way to specify render layers in the immediate mode API.

[aevyrie]

Another note - this is intentionally an extension, because you might want to make your own version of this. The provided one is a best-effort implementation for what bevy is capable of without adding dependencies. For example, at work, we have our own implementation that draws the indicator in the UI instead of in 3d.

[shanecelis]

In our app we were surprised by this but ended up actually liking that we could see the anchor in other cameras. So if it does become feasible to isolate, you may want to make it configurable.

[Calsign]

While there isn't a way to configure render layers per-gizmo, it seems that you can configure the render layer for gizmos globally. This works well for me:

fn configure_gizmos_render_layer(mut gizmo_config_store: ResMut<GizmoConfigStore>) {
    // render gizmos in render layer 1
    gizmo_config_store
        .config_mut::<DefaultGizmoConfigGroup>()
        .0
        .render_layers = RenderLayers::from_layers(&[1]);
}