Fighting Game · Guides & deep dives

V2 QA, Automation, Performance, And Cert Gates

Every PR runs the V2 automation suite.

6sections2 minread
Markdown source
On this page

FV2QAReleaseGateFeatureSet is the source-of-truth contract for §56. It binds UE automation coverage, Gauntlet scenarios, golden replay regression, performance budgets, cert gates, beta/dogfood gates, latency, frame pacing, reliability detection, and CI matrix requirements.

Automation#

Every PR runs the V2 automation suite. Required coverage tags are:

  • GASAbilities
  • MotionInputParser
  • HitboxHurtboxEngine
  • RollbackDeterminism
  • SaveLoadRoundTrip
  • DataTableIntegrity

Gauntlet PR scenarios cover launch, tutorial, arcade ladder, and online headless 1v1. A weekly four-hour long-run covers online ranked matchmaking, Battle Hub, World Tour traversal, and training-mode lab sessions.

Golden Replays#

The release gate requires 200 golden replay fixtures. Each build compares frame-by-frame hashes, and nightly cooked builds must replay the full set across all cooked platforms. Any divergent frame fails the gate.

Performance#

Launch performance targets are:

  • PS5 and Xbox Series X: 4K/60 in fighter modes.
  • Switch2 docked: 1080p/60 with quality-tier drop.
  • PC baseline: 1440p Medium at 60+ fps on RTX 3060 / RTX 4060 class hardware.

Per-system frame budgets are gameplay 4ms, animation 3ms, render 8ms, audio 1ms, network 0.5ms, and incremental GC at 1ms or less. Loading budgets are PS5 cold boot to main menu within 30 seconds and mid-session match load within 8 seconds.

Cert And Beta#

Platform gates cover PlayStation TRC, Xbox XR, Nintendo lotcheck, Steam Deck Verified, and Microsoft Store cert. Anti-cheat compatibility cert runs per platform. Trophy and achievement plans must avoid forced grind for basic completion.

The beta plan requires at least 30 days of internal closed beta, a pre-launch network test weekend, and a press playable build feature freeze.

Latency, Smoothness, Reliability#

Input-to-render budgets are 35ms at 60fps and 25ms at 120fps, measured with a controller camera rig plus frame-stamping. Stage budgets are controller poll 2ms, input buffer 2ms, sim tick 16.6ms, and render submission 8ms. NVIDIA Reflex and AMD Anti-Lag 2 are enabled by default on PC. Auto-tune latency mode recommends VRR, 120fps, or 60fps on first launch.

Shipping builds ingest frame-time histograms. The release gate requires 95th percentile frame time at or below 18ms for a 60fps target and flags hitches when two consecutive frames exceed 33ms. Dev overlays diagnose GPU/CPU bound scenes, and console/handheld builds warn on sustained thermal throttling.

Reliability gates include a 5-second ANR watchdog, GPU hang render-driver event detection, render-thread restart with Restore Match prompt, dev-build memory leak tracking, crash deduplication by stack-similarity hash, and a cooked driver-known-issues library.

CI Matrix#

V2/ue/Build/QA/v2-ci-matrix.json declares the section 56 matrix consumed by CI and Horde. Every PR gates editor compile, V2 automation, and Win64/Linux/PS5 cook coverage. The nightly full-platform cook runs 200 golden replays across cooked builds. Weekly runs execute the four-hour Gauntlet soak, and the pre-cert dry-run requires a 14-day platform rehearsal before submission.