Repository navigation
Keep gameplay recording compatible with normal play - #13
Merged
Merged
Conversation
mstan
marked this pull request as ready for review
November 18, 2026 05:16
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The launcher needs automatic replay diagnostics that preserve normal play. Add a recording mode that keeps inputs and clock callbacks with sampled state checkpoints. It avoids picture and audio hashing and leaves normal video delivery active.
Interactive recording now seals before a player save or load. A recording failure leaves the game running. Full captures and playback retain their existing checks.
Windows runner route and recovery checks passed. A Mario Kart 64 sample saved and loaded in the same session, then replayed the sealed 138-field segment in sync.