bevy_picking release notes #1806
Conversation
...ontent/0.15/release-notes/15800_Add_mesh_picking_backend_and_MeshRayCast_system_parameter.md
Outdated
Show resolved
Hide resolved
...ontent/0.15/release-notes/15800_Add_mesh_picking_backend_and_MeshRayCast_system_parameter.md
Outdated
Show resolved
Hide resolved
Co-authored-by: Joona Aalto <jondolf.dev@gmail.com>
…e/bevy-website into bevy-picking-notes
...ontent/0.15/release-notes/15800_Add_mesh_picking_backend_and_MeshRayCast_system_parameter.md
Outdated
Show resolved
Hide resolved
...ontent/0.15/release-notes/15800_Add_mesh_picking_backend_and_MeshRayCast_system_parameter.md
Outdated
Show resolved
Hide resolved
...ontent/0.15/release-notes/15800_Add_mesh_picking_backend_and_MeshRayCast_system_parameter.md
Outdated
Show resolved
Hide resolved
...ontent/0.15/release-notes/15800_Add_mesh_picking_backend_and_MeshRayCast_system_parameter.md
Outdated
Show resolved
Hide resolved
...ontent/0.15/release-notes/15800_Add_mesh_picking_backend_and_MeshRayCast_system_parameter.md
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Well written! I have a suggestion around breaking up the example just to avoid having a single large block of code, but that's a stylistic choice and I understand wanting to keep it all together as a single "real" example, rather than just highlighting some snippets.
| @@ -1,4 +1,117 @@ | |||
| <!-- Add mesh picking backend and `MeshRayCast` system parameter --> | |||
| <!-- https://github.com/bevyengine/bevy/pull/15800 --> | |||
|
|
|||
| <!-- TODO --> | |||
|  | |||
There was a problem hiding this comment.
It's a shame that mesh picking is called out further down as being disabled by default and discouraged due to performance concerns, but then the title image for this feature is explicitly mesh picking. I don't think there's anything that can be done about it though. These are real concerns, and mesh picking is the best visual representation of the feature.
...ontent/0.15/release-notes/15800_Add_mesh_picking_backend_and_MeshRayCast_system_parameter.md
Outdated
Show resolved
Hide resolved
|
To be honest, I think the fears about perf on raycast picking are overblown. The way picking is designed, switching from the mesh raycast backend, to rapier, and then to avian, has no impact on the picking code, it is completely agnostic to the hit test provider. This means there is really no risk in encouraging people to use the raycasting backend - it is a great way to get started with 3d without needing to worry about a bunch of setup, and if the thing you make turns out to outlive the toy stage, switching over to a physics engine has no real impact on your picking code. Plus, let's be honest with ourselves, 99% of users have small scenes and low poly assets, and the raycast performance is never going to show up on a profile for these people. Considering I can use it on Caldera without issue, I am really not worried. |
Co-authored-by: Aevyrie <aevyrie@gmail.com>
Co-authored-by: Aevyrie <aevyrie@gmail.com>
...ontent/0.15/release-notes/15800_Add_mesh_picking_backend_and_MeshRayCast_system_parameter.md
Outdated
Show resolved
Hide resolved
|
Caldera is pretty impressive! I've swapped to a gentler framing @aevyrie, and also adopted your suggested example. I personally really like the UI applications, but since there's a bit of a footgun there still we shouldn't demo it so prominently yet. Also: shorter is better! |
...ontent/0.15/release-notes/15800_Add_mesh_picking_backend_and_MeshRayCast_system_parameter.md
Outdated
Show resolved
Hide resolved
Co-authored-by: Carter Anderson <mcanders1@gmail.com>
I still need to add an image and a usage section to this,
but thesimple_pickingexample is currently broken so I can't steal its approach.EDIT: seems fine, I just misread what it's supposed to do.