FIND YOUR NEXT MOVE
Browse documentation
ENGINEERING DOCUMENTATION

Move left

Translate coherent horizontal body movement into a lateral game input.

EXPERIMENTALSOURCE REVIEW / 2026.09.09

Purpose and current status

This action exists in the legacy engine and V3 research path, with a corresponding Runner movement command. The current Runner default is the separate Demo Assist profile. The three paths do not share interchangeable thresholds.

Inputs and required joints

The legacy path uses a tracked pose, monotonic capture time, both shoulders and hips, and a valid calibration profile. PoseNormalizer derives calibration-relative hip and shoulder displacement and torso lean. Distances are normalized by calibrated shoulder width.

Legacy default thresholds

VariableDefaultMeaning
LateralTriggerDisplacement0.55Hip displacement / shoulder width
LateralShoulderTriggerDisplacement0.40Co-moving shoulder displacement / shoulder width
LateralMaximumTorsoLeanDegrees12°Excessive-lean limit
LateralCandidateDurationSeconds0.08 sSame-direction candidate duration
LateralCenterRearmDisplacement0.22Both centers must return within this range

The direction sign is −1. A direction change or failed geometry clears the old candidate. These are default legacy values, not FastGameplay or V3 settings.

Temporal rules and rearm

READYCANDIDATECOMMITRECOVER
Simplified lifecycle. Failed candidates cancel; a new action requires rearm conditions. Consult each implementation for exact state names.

After the same-direction candidate lasts long enough, the legacy engine emits one Triggered event and clears lateralArmed. Both hip and shoulder must return to the centered range before rearming. Duplicate frames do not add temporal evidence.

V3 research path

LateralLocalFeatureExtractor and local references evaluate coherent body, hip and shoulder direction as a horizontal pulse. EntrySpeed = 0.18 and EntryDisplacement = 0.008 are candidate-entry floors, in shoulder widths per second and shoulder-width ratios respectively. Adaptive noise floors and separate commit and rearm conditions also apply; these two values alone do not define the action.

Confidence and false-positive risks

Lean-only motion, vertical-action bob, relocation and capture intervals without valid derivatives must be distinguished. V3 additionally requires compatible references and available derivatives. See mathematics for legacy frame-rejection rules.

Validation and known limitations

Legacy engine and LateralV3DetectorTests sources were inspected. No motion test or human physical validation was rerun for this website. Lateral readiness after vertical motion remains an open issue in the current-state record.