Understand the original.
Rebuild its behavior.
An open research log documenting Mario Kart DS routines, fixed-point gameplay logic, and a faithful native Rust implementation.
Function classifications from the current export inventory. These are documentation counts, not a percentage of game completion. Recorded meanings include 1,872 reviewed annotations and 6,246 unverified sweep descriptions. Inferred and SDK labels also require review.
From evidence to a playable port
Game systems & roadmap
Kart physics, items, race flow, CPU drivers, rendering, audio and the remaining work.
Read the roadmap → 02 / CODE MAPPINGWhat each routine means
Address-based correlations, field layouts and connections to the Rust implementation.
Browse identified functions → 03 / ORIGINAL BEHAVIORFollow the game logic
Input paths, race state, structure offsets and discoveries supported by exported C and ARM instructions.
Read the research →A mapping is a claim.
A replay is evidence.
Read the exported routine, recover missing assembly behavior, capture the original game in BizHawk, then compare the Rust model. Coverage is reported per routine and recording. Parser tests and inferred labels are kept distinct from runtime verification.
Driver poses, expressions & playback
Joint and texture-pattern decoders plus the original animation clock are available. Their captured cases match the original; visible renderer integration and broader runtime coverage remain pending.
See source mappings and verification limits →