Optionaloptions: SweptCharacterSystemOptionsWhether SweptCharacterSystem.dispose has run. Disposal is terminal
(§83): a disposed system refuses its mutating entry points with
INVALID_APPLICATION_STATE (§89) rather than silently working.
Tracked nodes, in the order they will be advanced.
Number of tracked nodes.
Stops advancing every node. The system stays registered.
Drops every tracked node (§39 teardown).
Advances every tracked, enabled, active controller by fixedDeltaTime.
No per-registration setup is needed (§39).
Advances every tracked node's SweptCharacterController once per fixed step, under §42's
"kinematic"authority (§39 step 4).KinematicSystem's shape exactly — insertion-ordered tracking (§33), an idle component skipped before the authority check so a still character reports no conflict, and a refused write that leaves the node alone. What it adds is two once-per-node refusals of its own, both of which write nothing:CharacterControllerand aSweptCharacterController— two locomotion writers of one transform, which is the only way the two §39-step-4 systems can reach the same node;capabilities.queries.shapeCast: false(§30, §37) — presence is the capability, and a solver that cannot sweep cannot drive this controller. Reported rather than thrown, because a fixed step is not a place to throw (§61/§85) and because the answer would be the same sixty times a second.