Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Objective
Currently, our picking backends are inconsistent:
SpritePickingCamera
andPickable
for control, but mesh picking usesRayCastPickable
.MeshPickingPlugin
is not a part ofDefaultPlugins
.SpritePickingPlugin
andUiPickingPlugin
are.Solution
RayCastPickable
withMeshPickingCamera
andPickable
.SpritePickingPlugin
andUiPickingPlugin
fromDefaultPlugins
.Testing
Ran some examples.
Migration Guide
UiPickingPlugin
andSpritePickingPlugin
are no longer included inDefaultPlugins
. They must be explicitly added.RayCastPickable
has been replaced in favor of theMeshPickingCamera
andPickable
components. You should add them to cameras and entities, respectively, if you haveMeshPickingSettings::require_markers
set totrue
.