unity-physicscore2d-batching

Use world.CreateBodyBatch with a PhysicsBodyDefinition and count, or pass a NativeArray of definitions, instead of calling CreateBody in a loop. The returned NativeArray of PhysicsBody handles must be destroyed with PhysicsBody.DestroyBatch and disposed when finished.

Build a NativeArray of CastRayInput items and run them inside an IJobParallelFor job where each iteration calls World.CastRay. Collect the WorldCastResult hits into one results array, then convert them to batched actions such as SetBatchForce.

Compute new positions and velocities in a Burst-compiled IJobParallelFor flocking job, writing results into BatchTransform and BatchVelocity arrays. Push the entire state to the engine with single PhysicsBody.SetBatchTransform and SetBatchVelocity calls.

No, only body creation has a batch API currently. After CreateBodyBatch, shapes must still be attached per body by calling CreateShape on each PhysicsBody, though you can reuse the same geometry and shape definition across all bodies.

Bodies allocated through CreateBodyBatch share a batched allocation, so they must be released together via PhysicsBody.DestroyBatch rather than individual Destroy calls. The containing NativeArray must also be disposed to avoid native memory leaks.

Use batch creation whenever spawning more than about ten bodies, and batch transform or velocity updates when synchronizing many agents per frame. Individual calls remain fine for small counts where batching overhead outweighs the gains.