Skip to content

perf: bypass matched OoT movie reconstruction in diagnostic mode - #7

Draft
baromas wants to merge 1 commit into
MD5Visual:feat/oot-bootfrom
baromas:review/oot-movie-reconstruction-md5
Draft

baromas wants to merge 1 commit into
MD5Visual:feat/oot-bootfrom
baromas:review/oot-movie-reconstruction-md5

Conversation

@baromas

@baromas baromas commented Nov 7, 2026

Copy link
Copy Markdown

What changed

Add TOTK_OOT_MOVIE_DIRECT=1 for a movie-only diagnostic. Match the conversion and complete sequence of 13 reconstruction dispatches in one list, then encode the bilinear result before skipping the sequence. The original reconstruction stays enabled by default. This port uses the writable-image helper already present in feat/oot-boot.

Validation

  • Built the macOS runtime on a2e9e756. The synthetic movie probe passed 72 Metal-validated checks, including sRGB, alpha, replay fallback and output ownership.
  • In my combined OoT v131072 development build, the diagnostic brought the opening from about 24 to 60 real FPS and aligned voice/subtitles with picture. Horizontal green bands on black remained visible. Those gameplay results are from the combined build. This isolated branch still needs a full movie run.
  • The substitution trades reconstruction quality for speed, so I am opening this as a draft for discussion.

Matching strategy adapted from MIT nxnative #1331.

Port the guarded bilinear movie path to the existing writable-image and direct dispatch interfaces of the MD5Visual branch. Preserve the original reconstruction by default. The synthetic probe passed 72 checks with Metal API validation.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant