Skip to content
This repository was archived by the owner on Nov 18, 2026. It is now read-only.

Metroid Prime Remastered for Windows 0.1.0

Choose a tag to compare

@drakolordx7 drakolordx7 released this 24 Oct 22:48
· 24 commits to main since this release

First public release of the Metroid Prime Remastered PC port. Released 2026-10-24.

This is an early version. The game runs and is playable from the title screen through the Frigate Orpheon and into the first part of Tallon IV, but most of the game has never been played through. Expect bugs and please report them.

Install

  1. Download mpr-0.1.0-windows-x64.zip below, unzip it into a folder with a short path (for example D:\Games\MPR), and run mpr_launcher.exe.
  2. Press "Set up game files...", pick your own dump of Metroid Prime Remastered version 1.0.0 (.nsp, .xci, .nsz or .xcz) and your prod.keys, and press Start setup. It takes about 5 minutes on a 16-core PC.
  3. Let the launcher prepare shaders (a few minutes), then press Play.

You need Windows 10 (1903 or later) or Windows 11 (64-bit), a GPU with Vulkan 1.3 and about 14 GB of free disk space. No game files are included. HELP.txt in the zip lists the controls, the settings and the fixes for common problems.

SHA-256 of the zip: c3e8969bc88ea25c7004f883ca66fb1b72f062841ef5bcea540f1e275e33d53a

What works

  • Title screen, New Game, the opening cutscene, the Frigate Orpheon and the landing on Tallon IV, with the HUD, lighting, fog, bloom, movies and sound. The route from New Game through the first Frigate force fields to the Chozo Ruins' Main Plaza has been played by hand.
  • An automated check loads all 275 areas of the game. All of them load and draw without the colour noise that earlier builds had.
  • Saving, loading, pause, map, morph ball, charge shots and missiles were checked on keyboard and mouse and with controller input.
  • Launcher with display, mouse, keyboard, controller and button icon settings. Any resolution and aspect ratio, including ultrawide, with the HUD kept in a 16:9 frame on narrow screens. Frame rate limits up to 240 and uncapped. Physics at 120, 144 and 240 fps match 60 fps within about half a percent in tests.
  • Mouse and keyboard play with raw mouse aim, mouse control in the menus, the pause screen and the map, and button icons that follow the device you use.
  • HDR10, a low latency mode (NVIDIA Reflex) and an FPS counter (F2) are in the launcher. FSR 1 upscaling can be turned on in controls.ini ([upscale] mode = fsr1).
  • Two optional settings, both off by default and both on the Controls tab: a free lock-on that lets you move the view while the target stays on screen, and a setting that stops the gun's idle and walking motion from moving the camera.

Known issues

  • Only the start of the game has been played by hand. Later areas load but nobody has played them through, so a story blocker could be hiding in them.
  • Some wall monitors on the Frigate show static instead of their screen graphics. Report other visual problems with a screenshot.
  • With a controller, looking up and down with the right stick does not work yet (left and right does). This is being fixed.
  • Tested on one PC: an NVIDIA GeForce RTX 3080 (driver 617.42) on Windows 11. AMD and Intel GPUs have not been tried, and a few GPU tests differ from the reference on an Intel UHD 770. Reports are welcome.
  • Not tested with a physical controller (only through SDL's virtual gamepad), on a real HDR display, in exclusive fullscreen on a real display (Windows refused it in the test setup, so the game falls back to borderless), or with Alt+Tab and mouse capture on a real display.
  • The first minutes after a driver update can stutter until shaders are prepared again (Extras tab, "Prepare shaders").
  • Rare crashes were seen twice in room-loading sweeps (a Magmoor Caverns area and the Frigate air lock) and did not repeat.
  • XCI, NSZ and XCZ support is tested on built test files only, not on a real cartridge dump. Only the original version 1.0.0 base game works; updates are not supported.
  • Windows limits a file's full path to 260 characters. Keep the game folder path under about 180 characters.
  • There is no FSR 3, DLSS or XeSS yet (FSR 1 only). AMD Anti-Lag 2 has never been run.

Reporting bugs

Open an issue and attach mpr.log from the run where the problem happened. Never attach game files, your dump or your keys. The README has the details.