Repository navigation
Conversation
Simplify console texture code and comments, move the PS5 resource workaround beside the swizzler, and support padded PS4 mip chains.
mandel99
marked this pull request as draft
October 1, 2026 20:21
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
1 participant
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.
Adds experimental PS4 Morton 8x8 and PS5 GFX10 standard texture swizzle/deswizzle through the existing ISwizzler API. Includes complete mip chains, PS5 mip tails, RGB24 storage handling, additional fixed-size pixel/block formats and preservation of original padding during image replacement. Unsupported image imports are rejected before modifying texture data.
Synced with upstream main. Validation: Windows UABEANext Release build, 191 format checks and 115 PS4/PS5/Switch regression checks. Real console assets were also used during development; additional formats use synthetic fixtures. Display/XOR modes, arrays, cubemaps and streaming mip chains remain outside the supported scope. No in-game validation; game data and local test harnesses are not included.
Companion UABEANext integration: nesrak1/UABEANext#19