This website requires JavaScript.
Explore
Help
Sign In
ReaperOfVeriod
0 Followers
·
0 Following
Joined on
2026-07-03
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues.
Learn more about blocking a user.
User to block:
Optional note:
The note is not visible to the blocked user.
Cancel
Block
Repositories
9
Projects
Packages
Public Activity
Starred Repositories
ReaperOfVeriod
pushed to
main
at
ReaperOfVeriod/Going-Commando
2026-10-13 05:50:51 +00:00
5f0396e3d7
Measure every chunk's record offsets; the cause is ambiguous, so no fix
ReaperOfVeriod
pushed to
main
at
ReaperOfVeriod/Going-Commando
2026-10-13 05:46:58 +00:00
b9e9835639
A parser defect: one chunk type is not fixed-stride, and over-reads
ReaperOfVeriod
pushed to
main
at
ReaperOfVeriod/Going-Commando
2026-10-13 05:43:45 +00:00
af62032ddc
Most of the chunk container is level-independent: 65 of 74 signatures
ReaperOfVeriod
pushed to
main
at
ReaperOfVeriod/Going-Commando
2026-10-13 05:39:37 +00:00
59dba3e58d
Chunk records: the stride table, and the exception pinned by name
ReaperOfVeriod
pushed to
main
at
ReaperOfVeriod/Going-Commando
2026-10-13 05:35:58 +00:00
040386c0fb
Volumes: the reference that did not generalise
ReaperOfVeriod
pushed to
main
at
ReaperOfVeriod/Going-Commando
2026-10-13 05:33:27 +00:00
ca277a0a01
Volumes: a candidate table found, explicitly not called volumes
ReaperOfVeriod
pushed to
main
at
ReaperOfVeriod/Going-Commando
2026-10-13 05:29:08 +00:00
28ab7e094b
SBlk head characterised: four constants and one word that is not a count
ReaperOfVeriod
pushed to
main
at
ReaperOfVeriod/Going-Commando
2026-10-13 05:24:30 +00:00
bc5ebe559f
Tie slots 3, 6, 7: two readings excluded, and why the LOD test stops working
ReaperOfVeriod
pushed to
main
at
ReaperOfVeriod/Going-Commando
2026-10-13 05:21:59 +00:00
e86de3c73e
Tie i16[0..2] are the vertex positions, with a control in the test
ReaperOfVeriod
pushed to
main
at
ReaperOfVeriod/Going-Commando
2026-10-13 05:18:14 +00:00
06cf2fd46d
Tie vertex slot 3 is a byte-sized index, not a coordinate
ReaperOfVeriod
pushed to
main
at
ReaperOfVeriod/Going-Commando
2026-10-13 05:13:47 +00:00
1fa1913e38
Reconcile the docs after the last three corrections
ReaperOfVeriod
pushed to
main
at
ReaperOfVeriod/Going-Commando
2026-10-13 05:10:18 +00:00
282e633a7c
Withdraw the collision anchor: it was a byte-order bug in my own search
ReaperOfVeriod
pushed to
main
at
ReaperOfVeriod/Going-Commando
2026-10-13 05:07:22 +00:00
1f903efe23
An external decomp turns two overlay constants from measured into named
ReaperOfVeriod
pushed to
main
at
ReaperOfVeriod/Going-Commando
2026-10-13 04:59:23 +00:00
26a0918178
Gate the PCSX2 claims as tests; two corrections fall out of writing them
ReaperOfVeriod
pushed to
main
at
ReaperOfVeriod/Going-Commando
2026-10-13 04:54:54 +00:00
9f938f47de
Assert the tie vertex layout finding in a test, and audit which claims are asserted
ReaperOfVeriod
pushed to
main
at
ReaperOfVeriod/Going-Commando
2026-10-13 04:53:23 +00:00
922248a4ec
Tie: the element layout differs by i16[3] high byte, and (6,7) is a real pair
ReaperOfVeriod
pushed to
main
at
ReaperOfVeriod/Going-Commando
2026-10-13 04:50:09 +00:00
ed3e85a0f2
Refine the tie texcoord finding: it is i16[3]'s HIGH byte that selects
ReaperOfVeriod
pushed to
main
at
ReaperOfVeriod/Going-Commando
2026-10-13 03:19:09 +00:00
e27c40e738
Explain the tie texcoord residual: i16[3] selects the encoding
ReaperOfVeriod
pushed to
main
at
ReaperOfVeriod/Going-Commando
2026-10-13 03:14:41 +00:00
3ee0b3d0dc
Disprove that morphing causes the tfrag byte changes: LOD selection does
ReaperOfVeriod
pushed to
main
at
ReaperOfVeriod/Going-Commando
2026-10-13 03:08:10 +00:00
aff977e8c5
Correct the tfrag pointer-field claim, and show morphing regenerates VU packets
Previous
10
Next
