Start with PhiMotion
Understand the architecture, implementation and evidence behind the movement.
From movement to game input
PhiMotion interprets camera-observed joint positions through body geometry and temporal change, then maps explicit motion intents into game inputs. This documentation helps teammates understand the current implementation and its evidence boundaries.
CAPTURE
POSE
MOTION
BRIDGE
GAME
Understand the current state
Distinguish the legacy MotionIntentEngine, the V3 research implementation inside the historically named GameplayMotionRecognizerV2, and DemoAssistMotionRecognizer, the Runner’s default experimental profile. Sharing an action name does not make their input conditions or rearm rules equivalent.
Suggested reading path
- Start with system architecture and layer ownership.
- Read pose capture and calibration for input boundaries.
- Choose the relevant path in the motion intent engine.
- Connect notation to source variables in mathematics and signals.
- Read game integration, validation and known limitations together.
How to read status
| Label | Meaning |
|---|---|
| IMPLEMENTED | The corresponding code or documented architecture was inspected. |
| EXPERIMENTAL | A research or experimental integration path. |
| PARTIAL | Documentation is bounded or additional evidence is still needed. |
These labels are not accuracy or quality scores. Numeric values identify their configuration, units and applicable path. Test records that were not rerun during this website task are not presented as fresh validation.