wave5-physics-world-singleton-queries

To run spatial queries against Unity Physics collision data, use PhysicsWorldSingleton to access the CollisionWorld for raycasts, shape casts, distance queries, and overlap checks after the physics world is built each tick.

The best way to schedule raycasts safely is to complete dependencies before reading PhysicsWorldSingleton and allocate NativeList containers appropriately to store and dispose of query results without triggering job safety errors.

PhysicsWorldSingleton spatial queries return stale results if job dependencies are not completed before accessing the CollisionWorld, meaning you are querying the physics state before it is fully built for the current tick.

Yes, you can use CollisionFilter to narrow down overlap checks and distance queries by scheduling a job with PhysicsWorldSingleton.PhysicsWorld.CollisionWorld to target specific collision layers.

Implement ground detection by casting a ray downward every simulation tick and reacting when the closest hit intersects the desired collision layers, using PhysicsWorldSingleton to query the current CollisionWorld.

Yes, PhysicsWorldSingleton supports broad-phase AABB overlap detection for area effects by running OverlapAabb with a narrowed CollisionFilter against the current Unity Physics collision world.