DepthImage backprojection doesn't set up correctly if the same entity is used for camera and image

[kpreid]

Possibly the same sort of thing as #3296, but I can reproduce this on the latest code b4768f3 .

Describe the bug
If a DepthImage and Pinhole are logged to the same entity, the backprojection will fail to render because the meter value is 0. Yet, it works fine if the value is manually changed.

To Reproduce
Steps to reproduce the behavior:

1. Modify code-examples/depth_image_3d.rs so that both log() operations use the same entity path.
2. cargo run --bin rerun
3. cargo run --bin depth_image_3d
4. Observe that no backprojected depth appears.
5. Select the 3D view of the entity and observe that "Backproject meter" is equal to 0.

Expected behavior
The logged meter value should be respected.

Screenshots

Desktop (please complete the following information):

• OS: macOS Sonoma 14.2.1 (23C71)

Rerun version
rerun-cli 0.12.0-alpha.3 [rustc 1.74.0 (79e9716c9 2023-11-13), LLVM 17.0.4] x86_64-apple-darwin

Also reproduces with released rerun 0.11

[kpreid]

Per discussion at #4627 (comment) , maybe this sort of thing (multiple non-transform archetypes on the same path) isn't even supposed to be supported. But if so, there aren't really signposts against it, and #2568 specifically added support for a related case.

[Wumpf]

maybe this sort of thing (multiple non-transform archetypes on the same path) isn't even supposed to be supported

Generally, logging anything where components don't overwrite each other is fine. But we don't have a nice way of communicating that yet

[Wumpf]

This is definitely not a case where components overlap, this should just work. But somehow the supplied meter is ignored. I'm investigating