Repository navigation
Conversation
mstan
changed the title
mstan
force-pushed
the
fix/mmx23-widescreen-presentation
branch
from
October 27, 2026 16:33
908346c to
0095609
Compare
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.
X2/X3 widescreen margins exposed stale map cells, duplicated doors and boss canvases, and left unused map strips at bounded room edges. This branch adds the shared source/door and bounded-canvas mechanisms used by the paired title fixes, retaining original native pixels and guest sequence state.
Current engine819e2e1 includes bounded presentation view anchoring adapted from the accepted parked X1 experiment. Its default is inert; X3 enables it only for the demonstrated final-stage entry chamber at internal widths up to512. HUD remains in screen space. Existing priority-buffer/OAM limits still apply;684 retains its previous presentation. The parked X1 worktrees are preserved.
Validation includes provider/PPU fixtures, matched native pixels/WRAM/VRAM/OAM, current save/load and Pause/Capture/restart, and built runtime checks recorded with exact package identities. The latest anchor adds25 movement samples,68 unchanged full-image/WRAM samples across Kaiser/escape/Byte/factory, native256 and684/interpreter default-policy checks, and seven PPU fixtures. One unsettled Byte image sample is retained as inconclusive; the independent settled replay passes.
X2 owner validation is complete and its title releasev0.1.5 is published. X3 Byte/doors/factory and absence of a duplicate Kaiser head and the actual charged-shot finishing hit are accepted individually. The original shaft pipe walls are confirmed. The new chamber camera visual, ordinary escape, alternate fresh-stage rescue, Bit and remaining content/audio gates stay separate. This remains a draft: broader engine consumer validation and final merge handoff are open. No engine merge/release is implied by the X2 title release.
Paired X3 PR: mstan/MegamanX3SNESRecomp#4
Evidence: G:/Temp/Codex/mmx23-trigger-audit-20261026/burndown/chamber-anchor-qualification.json and earlier package records; committed policy details in docs/WIDESCREEN_PATTERNS.md.