unity-physics-queries

Unity Raycast queries fail silently when the origin is inside a collider due to backface detection rules on non-convex MeshColliders. Correct physics query selection and configuring backface handling ensures accurate detection and prevents silent failures.

To optimize Unity physics queries and avoid garbage collection, use NonAlloc variants like RaycastNonAlloc with pre-allocated buffers. This performance tier strategy prevents memory allocation during ground checks and frequent collision detection loops.

Choosing between Unity SphereCast and OverlapSphere depends on motion: SphereCast sweeps a shape along a path to detect obstacles, while OverlapSphere checks a static volume. Correct query selection prevents subtle bugs like bullets passing through enemies.

Unity physics query hit ordering is not guaranteed by distance unless specified, and incorrect LayerMask construction can filter out valid targets. Constructing LayerMasks carefully and verifying hit ordering ensures accurate trigger interaction and detection.

Fix Unity ground check queries not detecting trigger colliders by adjusting the physics query interaction parameters. Unity's default trigger interaction settings often ignore trigger colliders, causing silent detection failures during Raycast or OverlapSphere checks.