Fighting Game · Guides & deep dives

Aja Studio Mocap Cleanup And Retarget

V2 studio shoots continue to use Vicon / OptiTrack as physical capture hardware.

2sections1 minread
Markdown source
On this page

Scope#

V2 studio shoots continue to use Vicon / OptiTrack as physical capture hardware. The software path for cleanup and V2-skeleton retarget is Aja:

  • @aja/motion-pipeline-sdk for ingest, marker-solve import, gap fill, jitter cleanup, contact cleanup, and root-motion normalization.
  • @aja/neural-retargeting for V2 fighter-skeleton retarget and retarget quality evidence.

Contract#

Before shoot_ingest, the capture session must pass @v2/aja-consent-nil-ledger: every performer has active @aja/consent-management consent, the Themis @themis/likeness license ID is linked through consentChainRefs[], and rightsManifestSha256 matches V2/legal/rights-manifest.json. Any revocation blocks future Aja processing and Bellona cook for dependent clips.

@v2/aja-studio-mocap-pipeline emits a content-build-only plan with stages:

  • shoot_ingest
  • marker_solve_import
  • cleanup_gap_fill
  • contact_root_cleanup
  • neural_retarget_v2_skeleton
  • retarget_quality_gate

The hardware policy records Vicon / OptiTrack as recording-only and sets motionBuilderMayaFallbackAllowed: false for the default production path. Maya and MotionBuilder remain manual review tools after Aja output, not the primary cleanup or retarget owner.

The accepted retargeted clip then flows through @v2/aja-bellona-livelink-export, where @bellona/mocap performs 60 Hz frame-snap export and @bellona/unreal receives the editor-only Live Link handoff for cooked AnimSequence import. Runtime Live Link plugins remain disabled for V2.