ReaperOfVeriod
2a5307a157
The block header's float at +0x08 gives L and the switch distances are [D0, D1, D2] = [6L, 4L, 2L] world units -- 192/128/64 on every level measured. The distance test uses the patch's bounding sphere truncated to integers against trunc(D * 1024), not the sphere's centre, so a patch straddling a threshold takes the coarser mode. Six modes result: LOD 2, LOD 1 collapse, LOD 1 morph, LOD 0 collapse, LOD 0 morph, LOD 0. A morph weight runs 0 to 1 across its tier's band. Past the far edge an entry is not blended but replaced by its first parent -- a collapse. The tested property is that distance never moves back to a finer mode, swept across the whole range, because that is what keeps terrain from popping as the camera moves. The four V4_8 parent arrays are classified by VU address and an unrecognised address is now an error, which is a real check: all 18,102 patches still parse. Every recorded parent resolves to real vertex info and real positions, and no common entry claims a parent. That is as far as it goes, and the limit is a finding rather than a rounding error. The addresses are not unique: on level 0 patch 1, unk_indices_2_lod_01_addr == parent_indices_lod_0_addr == 291, with unk_06 and unk_0a both zero, so nothing but unpacking order separates them. Across all 27 levels 57,782 of 374,349 LOD entries resolve, and 316,548 unresolved LOD-0 entries against 28,739 resolved is far too lopsided to be genuine -- either the arrays are misassigned where addresses collide, or RAC2's positions_lod_0_count means something other than RAC1's. Only 3,274 of 18,102 patches carry enough V4_8 bytes to cover positions_lod_01_count + positions_lod_0_count + extras. The vertex-info tiers themselves are confirmed: the addresses at +9 and +11 match the observed V4_16 unpacks and the three tier counts sum to vert_count on every patch, so the header layout is right and it is specifically the parent arrays that are open. Ruled out so far: address-only classification (collides) and one-parent-per-position (fails on 15,000 patches). Not yet tried: ordering by VU address instead of by declaration, and using unk_06/unk_0a to suppress an empty tier before falling through. Written up in plan/level-assets.md.
Going Commando
A native PC reimplementation of Ratchet & Clank: Going Commando (PlayStation 2, 2003), written in Rust.
The game is reimplemented, not emulated. There is no MIPS interpreter here and no CPU emulator: the systems are ported to Rust so they run as ordinary native code.
Status: initial scaffold. The disc is identified and verified, the
workspace builds, and nothing else is implemented yet. See
docs/roadmap.md for where things stand and what comes next.
The target
| Game | Ratchet & Clank: Going Commando |
| Platform | PlayStation 2 |
| Disc | SCUS_972.68 v1.01, USA Black Label |
| Video | NTSC, 60 Hz |
| Boot ELF SHA-1 | bacda860cbd6723142e86db56f197e47e728970f |
Verified against a real disc — see docs/disc-identification.md.
This is the build the reference projects pin; Greatest Hits v2.00 is a
different binary and is not the target.
No game content
This repository contains no game assets, no disc images, no BIOS dumps and no proprietary toolchains. You supply your own legally obtained copy of the disc as an input, the way the upstream reference projects do.
A pre-commit hook enforces this, blocking disc images, asset directories, container signatures and files over 50 MiB. If you clone elsewhere, enable it:
git config core.hooksPath .githooks
Layout
crates/
gc-formats/ asset format parsers (pure, no I/O beyond the caller's buffer)
gc-extract/ disc pipeline: identify, unpack, verify
gc-game/ game logic: hero, weapons, moby classes, progression, saves
gc-video/ IPU / MPEG-2 decode
gc-engine/ Bevy app: Graphics Synthesizer, VU0/VU1, renderer, frame loop
docs/
disc-identification.md which disc we build against, verified
roadmap.md phases, gates, current status
plan/ one file per subsystem, written as work proceeds
formats/ format specs, written as formats are reversed
tools/
identify-disc.py identify any Going Commando disc image
vendor/
rerac/ pinned upstream reference checkout (not tracked)
Building
Requires a Rust toolchain via rustup.
cargo check --workspace
cargo test --workspace
The host audio backend is disabled in Cargo.toml (see the comment there) so
that the workspace builds without system ALSA development headers. Audio decode
is the last phase of the port and lives in gc-video; re-enable it and install
alsa-lib-devel when that work starts.
Identifying a disc
python3 tools/identify-disc.py <your-disc.iso>
Reports the serial, version and video mode from SYSTEM.CNF, hashes the boot
executable, and warns when the disc is not the supported build. Reads only a
few megabytes, so it is near-instant.
How it will be verified
Visual and behavioural comparison against PCSX2, replaying recorded input and
comparing frames, level by level. The PS2 float model is reproduced rather than
approximated — see AGENTS.md.
Credits and licensing
This project learns from and is built on the work of others. Licences are
recorded in PROVENANCE.md and notices must travel with any
code derived from them.
- ReRAC — a native Rust/Bevy port of Ratchet & Clank (2002), the first game. ISC. The architecture this project follows.
- OpenRAC / rac2-gc-decomp — matching decompilation research for this game. MIT. Source of verified struct layouts and engine documentation.
- Wrench — community documentation of Insomniac's container formats. GPL, used as a specification reference only; no code is copied.
Ratchet & Clank is a trademark of Sony Interactive Entertainment. This is an unofficial fan project, not affiliated with or endorsed by Sony Interactive Entertainment or Insomniac Games.