bevy_picking sometimes misses hits before objects are moved

[StefanSalewski]

I just shipped the Bevy 3D chess, updated from Bevy 0.14 to latest Bevy 0.16.1, see

https://github.com/StefanSalewski/Bevy-3D-Chess

Was same work, as a lot has changed, most importantly due to the deprecated bevy_mod_picking. Setting meshes, colors, and materials has changed also -- for some hours I just got a blank window, which makes debugging a bit difficulty.

Now it seems to mostly work, but there is a tiny spurious strange issue. For the initial setup that I am currently shipping, hovering over pieces works, with the exception for the topmost bishop. For that one it works not at all, or at least not for the upper halve of the figure. This seems to be only an issue for the startup of the program, when I have moved a piece, or done some other actions, it seems to work -- but I have not tested a lot. As this is a random, spurious issue, I assume a bug in Bevy -- but of course it might be a problem in my code as well, I don't know much about bevy, and are typically not able to follow all of the recent changes. A guess would be that there might be some interaction with the text fields, even when the are fare from overlapping?

This is for Linux with wayland on an x86 system.

Note: You would currently have to press 0 on numerical keypad to start a new game -- I ship this initial position only to demonstrate the issue.

I would be also interested in a way to get rid off the messages

2025-08-15T09:42:54.814978Z WARN bevy_gltf::loader: Unknown vertex attribute TEXCOORD_3

This issue was discussed already years ago. I have currently not the resources to fix the Blender files, when this would be the only way for fixing.

[alice-i-cecile]

This needs a minimal reproduction before we can help, sorry.

[StefanSalewski]

Thanks for your kind reply.

Would ~/bevy/examples/picking/mesh_picking.rs be minimal enough, or would I have to further strip the code. I just tested that example. When replacing the original text

    commands.spawn((
        Text::new("Hover over the shapes to pick them\nDrag to rotate"),
        Node {

with some more text like

    commands.spawn((
        Text::new("Hover over the shapes to pick them if you can really select them here and selecting works\n
        Hover over the shapes to pick them if you can really select them here and selecting works\n
        Hover over the shapes to pick them if you can really select them here and selecting works\n
        Hover over the shapes to pick them if you can really select them here and selecting works\n
        Hover over the shapes to pick them if you can really select them here and selecting works\n
        Hover over the shapes to pick them if you can really select them here\n
        Hover over the shapes to pick them if you can really select them here\n
        Hover over the shapes to pick them if you can really select them here\n
        Drag to rotate"),
        Node {

we get the same issue. When we run the program, we can select none of the objects. Increasing the window size allows to select a few objects. The strange thing is, that even some objects that are not covered by text can not be selected. Well, at least I am now quite sure that the text is the problem, but I have no idea why the texts interacts with the 3D objects at all, and why the text blocks more area than it actually covers, and of course I have no idea how to fix it.

Let me know if it would help to remove some lines of code from file mesh_picking.rs, I think I will be able to do that.

Best regards,

Dr. Stefan Salewski

[alice-i-cecile]

That's perfectly adequate, thanks!