Quick Answer: Super Odyssey PC Recomp is a native Windows and Linux Super Mario Odyssey PC port. It translates the game's ARM64 code to C ahead of time and compiles it into a regular program, so no emulator runs while you play. You supply your own extracted
exefsandromfsfolders from Super Mario Odyssey version 1.0.0 or 1.4.1.
Most people assume a PC port of a Switch game is an emulator with a nicer window. This one works differently. The project's GitHub page describes a preview build where the game's code is converted before you ever press Play. That changes what you need, what can go wrong, and which settings matter. Here's how it works in practice, what you need before installing, and the parts the README is upfront about.
What static recompilation actually does
The core technique is static recompilation. The game's ARM64 machine code is translated to C ahead of time, and the result is compiled into a Windows executable. An emulator translates instructions on the fly while the game runs. A static recompiler does that work once, up front.
The consequence is that the per-instruction translation cost moves out of your play session. What you pay instead is at install time: the installer recompiles the game code for your PC, which the project says takes a few minutes. The Switch's kernel, system services, the NVN graphics API, and audio are reimplemented natively, and graphics go through Vulkan.
This approach is not new. The project continues Power Moon Recomp, and it builds on LAS Recomp, which provides the static recompiler, runtime, and renderer. The README also credits OdysseyDecomp for the game's names and structure, which helps with reading and debugging the code.
So what does that buy you? Mainly predictable CPU behavior at runtime and the ability to use modern rendering features like higher internal resolution. The trade-off is that you're now running a rebuilt binary, not the original, and that trade-off shows up again in the mod section below.
Check your hardware and game files before you start
Most failed installs come from missing prerequisites, not from the installer itself. Check these before downloading anything:
- Operating system: Windows 10 or 11, x64. Linux and Steam Deck are supported only as an experimental AppImage.
- CPU: AVX2 support (Intel Haswell or AMD Zen or newer). Without it, the game code won't run.
- GPU: Vulkan 1.3 and an up-to-date driver.
- Memory and disk: 8 GB RAM minimum, 16 GB recommended, and about 12 GB of free disk space.
- Game files: the extracted
exefsandromfsfolders from your own copy of Super Mario Odyssey.
The game-file requirement has a detail many people miss. Version 1.4.1 works only if the update is already applied and you supply its full romfs folder, not just the update's files. The exefs folder should contain main, main.npdm, and sdk. If you point the installer at the wrong folder, it won't be able to build the game code.
The project states plainly that it contains no game files, code, assets, or keys, and that it won't help with obtaining them. Plan around the files you already own.
Installing it: the step-by-step path
The install is a single pass, but it has two long waits. Here's the sequence:
- Download the latest
...-windows.zipfrom the Releases page and extract it to a folder you control, such asD:\Games. Avoid Program Files. - Run
SuperOdysseyRecomp.exe. The program isn't code-signed, so SmartScreen may warn you. Choose More info, then Run anyway. - Point the installer at the folder containing your
exefsandromfsfolders. - Choose an install location for game data, saves, and shaders. Plan for about 12 GB.
- Press Install. The installer copies data, recompiles the game code (a few minutes), and compiles every shader (several minutes, once).
- Press Play. The game opens fullscreen, and later launches skip straight to the game.
That first long wait is the part worth planning around. Shader compilation happens at install time so effects don't stutter the first time they appear. If you install on a laptop that's on battery, you'll wait longer and may throttle. Plug in before you start.
Graphics options: what to set and what to avoid
The menu offers more graphics options than most ports, which makes it easy to over-configure. The table below summarizes the main options from the README.
| Setting | Hardware needed | What it changes | Known caveat |
|---|---|---|---|
| Internal resolution | Vulkan 1.3 GPU | Renders at up to 4x native resolution | Higher resolution costs GPU time, so test your frame rate |
| NVIDIA DLSS / DLAA | NVIDIA GPU | DLSS upscaling or DLAA anti-aliasing, with presets and sharpening | Only available on NVIDIA hardware |
| AMD FSR 1 | Vulkan GPU | Spatial upscaling with AMD's FidelityFX FSR 1 | Spatial upscaler, so it won't match DLSS temporal results |
| Native 90 or 120 FPS | Vulkan GPU | Runs the game at a higher native frame rate | Experimental; some objects or effects can move unevenly or look doubled |
| 120 interpolated | Vulkan GPU | Generates frames with interpolation | Pose smoothing is tuned on 1.0.0, so 1.4.1 may show more jitter |
Here's where most guides go wrong: they treat these as independent switches. In practice, pick your frame rate first, then your resolution, then your upscaler. Change one setting at a time. If a glitch appears, you can only identify its source if you changed one thing since the last working state.
That said, the 120 FPS and interpolated modes deserve the most suspicion. The README calls native 90 and 120 FPS experimental on both game versions. If you see doubled objects or uneven motion, switch frame rate back before blaming the resolution or upscaler.
Why code mods don't work here (and RomFS mods do)
This is the section that surprises people coming from other PC ports. You might expect mods to carry over, since the game is now a native program. The opposite is true for code.
Code mods, including exefs patches, IPS files, pchtxt patches, and online mods, can't be used. The reason is structural. Those patches are written against the original game binary. This port rebuilds the game code from that binary, so the addresses and instructions a patch expects aren't what the recompiled program contains. Applying the old patch would target the wrong bytes.
RomFS mods work, and they're the easier path. Place each mod in its own folder under mods\, using the structure mods\<Mod name>\romfs\.... The Atmosphere layout also works. You can switch RomFS mods on and off from the menu's Mods tab.
The practical rule: if a mod changes game assets like levels, models, or audio files, it may work. If it changes game logic in the executable, skip it.
Known issues and where stutter still comes from
The README is candid about what's unfinished, and you should read it before filing a complaint. Here are the main items:
- Version 1.4.1 is newer in this port and less tested. Native 90/120 FPS and frame interpolation are tuned on 1.0.0.
- Rare effects can still stutter once. The shaders are precompiled, but a rare effect whose pipeline state nobody has recorded yet gets prepared the first time it's drawn. It's kept for next time, so the hitch is a one-off per effect.
- Online features don't work. Anything that needs Nintendo's servers is unavailable.
- Windows Defender may flag the program. The unsigned binary decrypts a file, builds code, and starts helper programs, which can trigger a machine-learning (
!ml) detection. The project asks users to report false positives to Microsoft's submission portal at https://www.microsoft.com/wdsi/filesubmission.
Graphics glitches in untested places are also possible. The project asks for a screenshot and a press of F9 at the moment the glitch occurs. That writes the frame's details into the log, which is the most useful data a maintainer can get.
Updates, saves, and the file layout
Updates are handled inside the program. Open the menu with F1, go to Updates, and choose Download and install, then Restart now. The game checks GitHub in the background at start and contacts only GitHub, and you can turn that off. Your game files, saves, settings, and mods stay in place. If the update needs it, the game code is rebuilt and shaders are re-prepared once automatically.
The install folder has a clear layout. extracted\ holds your game data and the built odyssey_game.dll. save\ holds your saves, cache\ holds compiled shaders, powermoon.ini holds settings, and SuperOdysseyRecomp.log holds the log. Never share extracted\ or anything built from it, because it contains Nintendo's game.
Before a major version update, copy save\ somewhere safe. The README says saves survive updates, and a backup costs you nothing if something goes wrong.
Frequently Asked Questions
what is super odyssey pc recomp?
Super Odyssey PC Recomp is a preview native PC port of Super Mario Odyssey for Windows and Linux. It converts the game's ARM64 code to C ahead of time and compiles it into a regular program. It runs without an emulator, but you must supply your own extracted game folders to play.
how do i install the super mario odyssey pc port?
Download the Windows zip from the project's Releases page and extract it to a folder you own. Run SuperOdysseyRecomp.exe, point the installer at your extracted exefs and romfs folders, and press Install. Expect a few minutes for code recompilation and several more minutes for shader compilation, which happens once.
does super odyssey pc recomp need game files?
Yes. The project contains no game files, code, assets, or keys. You need the extracted exefs and romfs folders from your own copy of the game, version 1.0.0 or 1.4.1 with the update applied and its full romfs folder.
why does super odyssey pc recomp stutter sometimes?
Most shaders compile at install time, which prevents stutter when effects first appear. A rare effect whose pipeline state hasn't been recorded yet can still cause a short hitch the first time it's drawn. The program prepares it then and keeps it for future draws.
can i use mods with this pc port?
RomFS mods work. Place them in folders under the mods directory and toggle them in the menu. Code mods, including exefs patches, IPS files, and pchtxt patches, don't work, because the game code is rebuilt and those patches target the original binary.
Get your first session running this week
The most useful next step is simple. Install on a drive you own, set your internal resolution and upscaler, and play one level at your normal frame rate. Then switch to the experimental 90 or 120 FPS mode and note whether motion looks even. That single comparison tells you more than any benchmark chart. If it works, pass this guide to someone wrestling with the same Super Mario Odyssey PC port install, especially the exefs and romfs folder paths, which cause most early failures.