Repository navigation
Update XtfFile provenance: .xtf confirmed as the texture extension - #15
Merged
Merged
Conversation
The decomp recovered the .xtf extension string at .data 0x557554 (appended by PreloadTexture when opening <name>.xtf from graphics.xfs into the 256x256 texture atlas) — the earlier 'no .xtf string in the binary' note was a zeroed-data extraction artifact. PreloadTexture's header-read sequence corroborates the [w u32][h u32][fmt u8] layout.
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.
Summary
Doc-only follow-up to #14. The decomp just recovered the
.xtfextension string at.data0x557554 — it's whatPreloadTexture(0x4f43a0) appends when opening<name>.xtffromgraphics.xfsinto the 256×256 texture atlas. The earlierFILEFORMATS.mdnote that "no.xtfstring exists in the binary" (which #14's doc comment repeated) was a zeroed-data extraction artifact.PreloadTexture's header-read sequence — two int-sized fields, one byte, then the whole pixel body into the atlas upload — corroborates the[width u32][height u32][format u8]layout, though the decompiler dropped the exact per-read byte counts, so the layout stays pinned by the on-disk files (and the checked-inTornadoTexture.xtffixture).Test plan
swift test— no behavior change, doc comment only