Hello babylon crew! Hope you are all well!
I believe I’ve found an issue with the order of the scene.multipick function. For all objects created during “runtime” (meaning after an initial scene setup), they seem to be put in the very “back” of the pick order. The normal scene.pick returns the correct first mesh hit regardless.
0, sphere2 (first hit)
2, ground (last hit)
0, sphere (should be second hit)
2, sphere2 (should be first hit)