patch · v1.0
Patch Retest — Version Diff
What changed between GameVersion A and B?
Published protocol — results that use it must reference protocol_id + protocol_version. Old results stay bound to the version they were tested under.
Method steps
1. Take published Result for GameVersion A (e.g., PS5 1.03). 2. Re-run same protocol (same method version) on GameVersion B (e.g., 1.04) with same platform. 3. Compute absolute and percent change: (new-old)/old*100. 4. Publish new Result for B + VersionChange row.
Equipment
Stock vehicle / controller vs KBM as stated; frame-counted video.
Controls
Same protocol version, same platform, same environment snapshot.
Variables
GameVersion only.
Environment
Identical to original Result’s environment_snapshot.
Sample size
Same as original Result (e.g., 10 runs)
Limitations
Diff is only valid when protocol version and platform match; otherwise note limitation.
Retest policy
Every new GameVersion triggers retest for critical families within 7 days.
No fabricated values
This page shows method only. Measured numbers live in Lab results and are bound to
TestRun + Measurement + GameVersion + Platform. When no shipping-build measurement exists, population is BLOCKED_EXTERNAL.Version history: protocol changes create a new row (new version), not an in-place edit. See test_protocols.version.