Repository navigation
Match the engine-trail ribbon builder (func_0022F738) - #102
Merged
Merged
Conversation
The two engine rings sit in the trail state struct at +0xC0, the across/side normals share one workspace and the second vertex loop sets its position pointer in its own initializer: 1,188/1,188 bytes, no flags or barriers. Full build 1224/1224 exact; progress/report.json regenerated. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
xx255q
force-pushed
the
match/engine-trail
branch
from
October 19, 2026 15:16
e7d3c86 to
474c8c8
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.
func_0022F738insrc/game/space.c, the space flights' engine-trail ribbon builder (1,188 bytes), is now C and matches exactly: the 0x210-byte frame, every instruction, and the 4 alignment bytes after it. There are no new flags, inline assembly, register pins or barriers.What closed the last differences (from a 62-byte near miss):
D_0013E130, so they still live at 0x0013E1F0 / 0x0013E3F0. This changes which address expressions GCC shares, and gives retail's order of the cross-product calls.forinitializer, after the first draw, which gives retail's setup around that draw.Checks
tools/file_check.py src/game/space.c: 15 C functions, 0 not exact.bash tools/build_sn.sh: 1224/1224 audited exact, every function at its retail address, the image matches retail.progress/report.jsonregenerated (4,904 → 4,905 of 5,121 functions, 95.14% → 95.17% code);--checkpasses.The port-only C in
nonmatching/functional/func_0022F738.cis left as it is, as for func_0023C5E0 in #99 (ByteMatch leaves out matched functions).Origin: the candidate was prepared with ChatGPT against this main (
1db496d2). I applied it unchanged to a clean checkout and reran every check above here.🤖 Generated with Claude Code