mirror of
https://github.com/izzy2lost/Diddy-Kong-Racing.git
synced 2026-06-19 01:16:26 -07:00
Ryan MyersandGitHub
e732cd2f58
* WIP func_800B7EB4 * Fix RNG funcs. They really don't accept arguments, and pretending they do breaks the only code that calls them. * Work on waves.c * Match obj_loop_door * Indentify flag * Match obj_loop_fish * Match obj_loop_weaponballoon * Match obj_loop_char_select * Match func_8003F2E8 * Update score
182 lines
7.0 KiB
Markdown
182 lines
7.0 KiB
Markdown
# Diddy Kong Racing
|
|
|
|
This repo contains a work-in-progress decompilation of Diddy Kong Racing for the N64. You will need to have a original copy of the ROM to extract the game's assets.
|
|
|
|
Currently, only the US 1.0 version of the game is supported. US 1.1, EU 1.0, EU 1.1, and JP are not supported at this time.
|
|
|
|
<!-- README_SCORE_SUMMARY_BEGIN -->
|
|
As of November 10, 2023, this is our current score:
|
|
|
|
    Decomp progress: 65.01%
|
|
|
|
    Documentation progress: 35.21%
|
|
<!-- README_SCORE_SUMMARY_END -->
|
|
|
|
---
|
|
|
|
## Dependencies
|
|
|
|
* `libcapstone-dev`
|
|
* `gcc`, Version 8.0 or higher
|
|
* `make`, Version 4.2 or higher
|
|
* `python3`
|
|
* `wget`
|
|
|
|
`sudo apt install build-essential pkg-config git python3 wget libcapstone-dev`
|
|
|
|
### binutils
|
|
|
|
You are not required to install a binutils package, but it does speed up the initial setup if you do have it installed.
|
|
|
|
* Ubuntu/Debian (x86): `sudo apt install binutils-mips-linux-gnu`
|
|
|
|
## Setup / Building
|
|
1. Install the dependencies
|
|
2. Place the ROM file within the `baseroms` directory.
|
|
**a.** The name of the ROM file does not matter, but it must end with one of these extensions: `.z64`, `.v64`, `.n64`, or `.rom`. It will be detected automatically from an md5 checksum.
|
|
**b.** If you use a byte-swapped or little-endian ROM, then it will automatically be converted to a big-endian (.z64) ROM file.
|
|
3. Run `make` in the main directory.
|
|
**a.** Use the `-jN` argument to use `N` number of threads to speed up building. For example, if you have a system with 4 cores / 4 threads, you should do `make -j4`.
|
|
|
|
### Building on MacOS
|
|
1. `brew install gcc capstone coreutils`
|
|
2. Put GNU-coreutils `bin` on path using by adding `PATH="/usr/local/opt/coreutils/libexec/gnubin:$PATH"` to your shell rcfile (or update any GNU-util usage in `Makefile` and `tools/Makefile` to use the `g`-prefixed versions).
|
|
3. Download latest `macos` build of `ido-static-recomp` from [here](https://github.com/decompals/ido-static-recomp/releases/), and add `cp` the binaries to `tools/ido-static-recomp/build5.3/out`.
|
|
4. Take a look at [this gist](https://gist.github.com/tonyspumoni/fc1b4c9217c5f2821a9fc4cbf69b51ef) to see what other updates are needed to get the build to pass, and apply them if they are relevant to your environment. You may need to add specific `-I` and `-L` flags to get things like `openssl` and `gcc-12` includes/libs included.
|
|
5. `make` from repository root should work now.
|
|
|
|
## Modding
|
|
If you are modifying the code in the repo, then you should add `NON_MATCHING=1` to the make command.
|
|
Example: `make NON_MATCHING=1 -j4`
|
|
|
|
The `NON_MATCHING` define will include the functions that don't exactly match one-to-one, but should be no different functionality-wise. If you do notice any bugs that occur in a `NON_MATCHING` build that are not in the vanilla game, then please file an issue describing the bug. It would be helpful if you can track down which function is causing the bug, but that is not required.
|
|
|
|
## Style Guide
|
|
|
|
The style guide for the project can be found here: https://docs.google.com/document/d/1euQf8nwynGcCZL1MfoMaLs-XRvx3ejjj8fIfykUZ-NQ
|
|
|
|
If you see variables/functions/structs/etc. that doesn't follow these rules, then file an issue and we'll try to fix them.
|
|
|
|
## Scripts
|
|
|
|
There are some useful scripts that should be kept in mind when working on this repo.
|
|
|
|
---
|
|
|
|
#### `./extract.sh <version>`
|
|
|
|
This script will extract all the assets from a DKR ROM and place them into `/assets/` folder according to the config file within the `/extract-ver/` folder. The version parameter should either be `us_1.0`, `us_1.1`, `eu_1.0`, `eu_1.1`, or `jp`.
|
|
|
|
Example: `./extract.sh us_1.0`
|
|
|
|
---
|
|
|
|
#### `./diff.sh <function_name>`
|
|
|
|
Compares the assembly output of a function from a built ROM to the base ROM. Useful for decompiling.
|
|
|
|
Example: `./diff.sh menu_init`
|
|
|
|
---
|
|
|
|
#### `./rename.sh <old_name> <new_name>`
|
|
|
|
This script will rename an existing symbol, file name, and/or folder name within the repo with a new one.
|
|
|
|
Example: `./rename.sh D_A4001000 SP_IMEM`
|
|
|
|
---
|
|
|
|
#### `./get_symbol.sh <ram_address>|<symbol>`
|
|
|
|
Given either a RAM address or symbol, returns its `(symbol, address)` pairing as defined in `/build/us_1.0/dkr.map`. If specified, the RAM address must be in base 16. The `0x` prefix is not required.
|
|
|
|
Example:
|
|
```
|
|
./get_symbol.sh 0xA4001000
|
|
0xA4001000 = SP_IMEM
|
|
|
|
./get_symbol.sh osCicId
|
|
0x80000310 = osCicId
|
|
```
|
|
|
|
---
|
|
|
|
#### `./score.sh`
|
|
|
|
Prints out the current completion percentage of the decomp. You do need to have an `OK` build for this to work properly.
|
|
|
|
The scoring is split into 2 sections:
|
|
1. Assembly to C Decompilation (Adventure One)
|
|
2. Cleanup and Documentation (Adventure Two)
|
|
|
|
Show scores for Adventure One & Adventure Two: `./score.sh`
|
|
Show score for Adventure One only: `./score.sh -a 1`
|
|
Show score for Adventure Two only: `./score.sh -a 2`
|
|
Show top 10 files remaining: `./score.sh -t 10`
|
|
|
|
To make progress in Adventure 2, a function must be properly named (must not start with `func_`) and also include a doxygen comment above it.
|
|
|
|
For example:
|
|
```c
|
|
/**
|
|
* Returns 1 if Drumstick is avaliable to use, or 0 if not.
|
|
*/
|
|
s32 is_drumstick_unlocked(void) {
|
|
return gActiveMagicCodes & 2;
|
|
}
|
|
```
|
|
|
|
<!-- README_SCORE_BEGIN -->
|
|
As of November 10, 2023, this is our current score:
|
|
```
|
|
====================================================================
|
|
ADVENTURE ONE (ASM -> C Decompilation)
|
|
-------------- 65.01% Complete (67.79% NON_MATCHING) ---------------
|
|
# Decompiled functions: 1670
|
|
# GLOBAL_ASM remaining: 175
|
|
# NON_MATCHING functions: 15
|
|
# NON_EQUIVALENT WIP functions: 51
|
|
--------------------------- Game Status ----------------------------
|
|
Balloons: 30/47, Keys: 3/4, Trophies: 3/5
|
|
T.T. Amulets: 3/4, Wizpig Amulets: 3/4
|
|
--------------------------------------------------------------------
|
|
We are racing Taj in the Plane Challenge. (Lap 3/3)
|
|
====================================================================
|
|
ADVENTURE TWO (Cleanup & Documentation)
|
|
------------------------- 35.21% Complete --------------------------
|
|
# Documented functions: 825
|
|
# Undocumented remaining: 743
|
|
--------------------------- Game Status ----------------------------
|
|
Balloons: 17/47, Keys: 2/4, Trophies: 1/5
|
|
T.T. Amulets: 2/4, Wizpig Amulets: 1/4
|
|
--------------------------------------------------------------------
|
|
We are collecting silver coins in Everfrost Peak. (2/8 silver coins)
|
|
====================================================================
|
|
```
|
|
<!-- README_SCORE_END -->
|
|
|
|
---
|
|
|
|
## TODO list
|
|
|
|
### Major
|
|
|
|
What should be focused on.
|
|
|
|
* Decompiling the non-matching asm files into matching C functions.
|
|
* Documenting variables & functions
|
|
|
|
### Minor
|
|
|
|
What can be done, but not essential.
|
|
|
|
* Figuring out the formats for the assets in the /assets/ folder.
|
|
* Creating tools to modify assets
|
|
|
|
### Future
|
|
|
|
These features won't be complete anytime soon.
|
|
|
|
* Add support for the other 4 versions.
|