Skip to content
PORTSNATIVE.
HomeCatalog
Web GamesEmulatorsToolsNews
PORTSNATIVE.

A catalog for discovering ports and related projects. We link to official sources and do not host original game files.

ExploreCatalogMy list
InformationAbout usSuggest a portSupportDonationsLegal notice
© 2026 PortsNative
Back to catalog
Pilotwings 64
PORTSNATIVE

Pilotwings 64

NATIVE PORTPLATFORMERWINDOWSALPHA

Pilotwings 64

TechnologyDecompilation and reconstruction in C/C++

Available forWindows

View official project

About the project

Pilotwings 64 es un videojuego para la Nintendo 64 publicado en 1996, junto con el lanzamiento de la consola. Fue el único de los dos títulos lanzados conjuntamente con la consola junto con Super Mario 64. El juego es una secuela de Pilotwings, aparecido para la SNES, el cual fue también un título publicado con el lanzamiento de esta consola.

3 versions of Pilotwings 64

You're viewing: Pilotwings 64

Pilotwings 64github.com/n64decomp/pw64
Windows
Current
Birdman64 (Pilotwings 64)github.com/NoahVl/Birdman64
Windows
Linux
›
Pilotwings 64 Recompiledgithub.com/danielgomesvieira2000/pilotwings-64-recomp
Windows
Linux
›

Official project information

Author's original READMEOpen on GitHub ↗

Build Discord

Code Data Functions

Code Data Functions

Pilotwings64Decomp

This repo contains a work-in-progress matching decompilation of Pilotwings 64, currently supporting the following releases: North America (U).

The purpose of this project is to produce a reconstruction of the high-level source code through reverse engineering.

[!IMPORTANT] This repository does not contain any game assets, assembly code, or other copyrighted materials. You must provide your own legally-obtained copy of the game in order to extract the assets necessary to build this repository.

Quick Start

See the Development section below for full details on different systems. For Debian/Ubuntu, the following steps can be taken to quickly get going:

$ sudo xargs -a packages.txt apt-get install -y
$ git clone --recurse-submodules https://github.com/gcsmith/Pilotwings64Decomp.git
$ cd Pilotwings64Decomp
$ python3 -m venv .venv
$ source ./.venv/bin/activate
$ python3 -m pip install -r requirements.txt
$ cp <path-to-ROM> ./baserom.us.z64
$ make dependencies
$ make init

Development

Git

This repository uses Git submodules. Make sure to either clone the repository with the --recurse-submodules flag or to run git submodule update --init --recursive after the initial clone.

When pulling updates, you can update all submodules with git submodule update --recursive.

Note: If you intend on developing inside of the Windows Subsystem for Linux (WSL), consider placing the repository on the WSL Linux partition. Builds are considerably slower when done on the Windows partition through WSL.

Prerequisites

Windows

Install the Windows Subsystem for Linux (WSL) and a Linux distribution according to the Installation Guide.

The following Linux instructions assume Ubuntu or Debian as the distribution.

Debian/Ubuntu Linux (also under WSL)

The following packages are required for the build process:

  • binutils-mips-linux-gnu (or similar, e.g. mips64-elf-binutils)
  • build-essential
  • git
  • python3
  • python3-pip

The following packages are also recommended but not strictly required:

  • clang
  • clang-format
  • clang-tidy
  • python3-venv

macOS

First ensure that the following tools are installed:

  • Xcode Command Line Tools
  • Homebrew

The following homebrew packages are required for the build process:

  • coreutils
  • make
  • tehzz/n64-dev/mips64-elf-binutils

Python3 packages / venv

This project has python3 dependencies defined in the repo's requirements.txt. These can be managed through a python virtual environment and pip or through uv.

Example setup with python3 venv/pip

$ python3 -m venv .venv
$ source ./.venv/bin/activate
$ python3 -m pip install -r requirements.txt

Example setup with uv:

$ uv venv
$ uv pip install -r requirements.txt

Setup

  1. Place an unmodified Pilotwings 64 ROM into the root of the repository as baserom.us.z64 (SHA1SUM: ec771aedf54ee1b214c25404fb4ec51cfd43191a).
  2. Set up dependencies
    • make dependencies
  3. Init project
    • make init

Rebuilding

  1. If any symbols or the splat config were changed, re-extract the ROM and rebuild the linker script:
    • make extract
  2. Rebuild the ROM:
    • make -j

Docker

If you prefer to develop inside of a Docker container instead of installing everything in your local environment, use the provided Dockerfile in the root of the repository.

Example usage:

# Create image
docker build -t pw64decomp --build-arg login=$USER --build-arg uid=$UID .

# Enter a bash prompt
docker run --rm -it -v $(pwd):/pw64 pw64decomp bash

# Run a one-off command
docker run --rm -it -v $(pwd):/pw64 pw64decomp pw64 build

Contributing

Pull requests are welcome. You can help with decompilation, renaming, documentation, and tooling. PRs are subject to code formatting checks, so there is an additional dependency of clang-format (provided by clang). Run make format to format your changes prior to starting the PR.

Read official guide
CALIFICACIÓN
—
Loading votes…
Advertisement

PROJECT FILE

Project type
NATIVE PORT
Genre
Platformer
Status
alpha
Original platform
—
Technology
Decompilation and reconstruction in C/C++
Version
—
Updated
—

Target platforms 1

Windows
View on GitHub
Advertisement