The First Wii Game Recompiled for PC Has an ARM64 Build. Its Spec Sheet Rules Out Every ARM Handheld.

2026-09-18 · News and analysis

Affiliate disclosure: This guide contains affiliate links. As an Amazon Associate, we earn from qualifying purchases at no extra cost to you. Learn more.

The recompilation scene has been stuck on three systems for a while. N64, Xbox 360, and one PlayStation 1 game. The Wii was not on the list.

It is now. Mario Kart Wiicompiled is the first static recompilation of a Wii game, and since 3 September it has been shipping an aarch64 AppImage alongside the x86 and Windows builds.

An ARM64 build of a Wii game sounds like exactly the news retro handheld owners have been waiting for. Then you open the requirements and find a GTX 1650 sitting at the bottom of the GPU list, and the story changes completely.

Both halves of that are worth understanding, because this project is going to get copied.

The Short Version

• What it is: the first static recompilation of a Wii game, converting PowerPC code to native binaries
• The game: Mario Kart Wii
• Announced: 15 July 2026
• Status: still in beta. Current version is 0.2.32, released 14 September 2026
• Windows only until: version 0.2.26 on 3 September 2026, which added the aarch64 AppImage
• Platforms: Windows 10/11, Linux x64 and ARM64, macOS 14+ on Apple Silicon only
• Minimum GPU: GTX 1650, RX 6400 or Arc A310
• Minimum CPU: Intel i5-8400 or Ryzen 5 2600
• Disc required: a clean, unmodified PAL disc image, region code RMCP01
• Disk space: around 20GB during setup, roughly 5GB afterwards
• AI disclosure: the project states AI coding tools were used during development

What Static Recompilation Does Here

The Wii runs on a PowerPC chip. Your PC does not. Normally bridging that gap is Dolphin's job, and Dolphin does it while you play, translating PowerPC instructions into x86 or ARM instructions on the fly, every frame, forever.

Static recompilation moves that work to before you play. The original PowerPC code is translated once, ahead of time, into code your machine runs directly. The project's own description is blunt about the result: no emulator in the loop, no interpreter, no JIT, no PowerPC anywhere at runtime.

That is a real architectural difference from emulation, and it is why the output can hit uncapped frame rates and 4K without the overhead Dolphin carries. Our decomp vs recomp explainer covers the wider technique.

It is also why the setup takes 20GB and a long wait. That translation has to happen somewhere, and here it happens on your machine, once.

The ARM64 Build, and Why It Does Not Help

Here is the part that needs spelling out, because the headline facts point in opposite directions.

The project ships WiiCompiled-Setup-aarch64.AppImage. That is a genuine ARM64 Linux build, and it arrived on 3 September after two weeks of Windows only releases. On paper, ARM handheld owners are in.

Now the requirements. The floor is a GTX 1650, an RX 6400 or an Arc A310, plus an i5-8400 or Ryzen 5 2600 class CPU.

No ARM handheld on the market clears that bar. Not a Retroid Pocket 5, not an AYN Odin, not any Anbernic. Those are desktop discrete GPUs, and the ARM devices that could run an aarch64 AppImage are using integrated mobile graphics an order of magnitude below them.

So the aarch64 build exists, and the hardware that would use it cannot meet the spec. It is almost certainly there for ARM Linux desktops and Apple Silicon adjacent setups rather than for handhelds.

This is the second time in a month we have had to write this exact correction. Suyu's recompiler mode targeted x86-64 and gave ARM handhelds nothing. This one ships the ARM build and then prices it out. Different mechanism, same outcome.

It Is Still a Beta, Whatever the Headlines Said

Version numbers matter here. This project is on 0.2.32, not 1.0.

The README describes the game as playable, with physics matching original hardware, while stating that compatibility, rendering, networking and performance are all still being actively worked on. That is a beta, and the release cadence backs it up. Twelve releases between 23 August and 14 September is a project moving fast and fixing things, not a finished port.

Known limitations the project lists directly:

• Wii Remote support has no IR pointer functionality
• Classic Controller triggers are digital only, with no analog range
• No battery level reporting for remotes
• Setup is slow, because of the one-time compile

None of that is damning for a beta. It is just a long way from the finished article some coverage implied.

PAL Only, and That Trips People Up

The project accepts one thing: a clean, unmodified PAL disc image with the region code RMCP01.

If you are in North America and own the game, your disc is the wrong region for this. That is an unusually specific requirement, and it is the single most common reason people bounce off the setup.

As with every project in this scene, you supply the disc image yourself from a copy you own. The project ships no Nintendo code, no assets and no game data.

The AI Disclosure

The README states plainly that AI coding tools were used during development, and adds that the translated output is verified against real hardware behaviour.

That disclosure is worth noticing, because it lands in the middle of an argument the recompilation scene is currently having with itself. Other projects have taken the opposite position and advertise that no AI was involved at all. A third group is getting quietly delisted from community trackers for using AI without saying so.

Wiicompiled chose the middle path: use the tools, say so, and point at hardware verification as the quality control. We cover how that split is playing out and what it means when you are deciding which port to trust.

What You Actually Need to Run It

This is a PC project. Treat it as one.

For handhelds, that means x86. A

If you want Mario Kart Wii on an ARM handheld, recompilation is not your route and will not be soon. Dolphin on a capable Android device is, and our GameCube and Wii emulation guide covers what that takes. A

Questions People Ask

Can I run Mario Kart Wiicompiled on a Retroid or Anbernic?

No. There is an ARM64 Linux build, but the project's minimum specs call for a discrete desktop GPU that no ARM handheld has. The build exists for ARM desktops, not handhelds.

Is this better than Dolphin?

For raw performance on capable hardware, the technique is inherently lighter, since nothing is being emulated at runtime. But Dolphin runs the entire Wii and GameCube library and is mature and stable, while this is one game in beta. They are not really competing.

Why does it only accept the PAL disc?

The recompilation was built against that specific version of the game. Static recompilation translates one exact binary, so another region's disc is a different binary and will not work.

Does it really need 20GB?

During setup, yes. That space is consumed by the one-time translation and compile step. The finished install settles at roughly 5GB.

Is the project finished?

No. It is at version 0.2.32 and the README lists compatibility, rendering, networking and performance as active work. It is playable, not complete.

Are more Wii games getting this treatment?

Nothing else has been announced. This is the first Wii game to get a static recompilation at all, and the toolchain it used is specific to this project rather than a general purpose Wii recompiler.

Related Reading

• The Recomp Scene's AI Problem
• Decomp vs Recomp: How Old Games Become PC Ports
• Suyu's Recompiler Gave ARM Handhelds Nothing
• Donkey Kong 64's Recomp Ships an ARM64 Build
• Recompiled Games List: Every Native PC Port by System
• Can Android Handhelds Run Recompiled Games?
• GameCube and Wii Emulation on Handhelds

Platform list, version history and hardware requirements come from the project's README and GitHub release data, retrieved 18 September 2026. No performance benchmarks are quoted because the project publishes none.