Skip to content

Releases

v0.2.1

Choose a tag to compare

@MIXIDtheSilly MIXIDtheSilly released this 17 Nov 22:50

This release fixes the GPU crash ("device lost") on NVIDIA, uses about 2.5 GB less RAM in races, adds a Settings page to the launcher and fixes the Linux build on current distributions.

Important

This release contains no game code or data. You build the game yourself from your own dump. Don't use this with pirated copies: own the game and a Switch 2, and dump it from your own console.

Updating

From 0.2: the launcher offers 0.2.1 when it starts (or click Update to 0.2.1 at the top right). Then click Build: the shader translator changed, so the shaders are translated again and the game is linked again. The game's code isn't recompiled.

From 0.1.x: unzip 0.2.1 into a new folder, run its launcher, click Bring over an older version… on the first step, pick your old kart-recomp-… folder, then click Build.

Getting started

Windows: download kart-recomp-0.2.1-windows.zip, unzip it somewhere without spaces in the path, and run launcher\out\launcher.exe.

Linux: download kart-recomp-0.2.1-linux.tar.gz, unpack it, and run launcher/out/launcher (or ./kart.sh). You need a Vulkan 1.3 driver, SDL 3 (Fedora SDL3, Debian/Ubuntu libsdl3-0), g++ and Python 3.10+ with venv.

Then follow the launcher's four steps: pick your dump (folder or .nup), click Set up, build (about half an hour the first time), play.

What's new in 0.2.1

  • Fixed: GPU crash ("device lost") on NVIDIA, in races and on the loading screens. The NVIDIA driver mis-compiles one way of writing an integer absolute value in particle-effect shaders, and the GPU hung on those draws. The shader translator now writes it in a form the driver handles. This is probably also the crash in #26.
  • Less memory: races use about 9.5 GB of RAM instead of about 12 GB. Graphics memory imports stay lean on every PC, and the shaders' SPIR-V is no longer kept around after the pipelines are made.
  • Settings page in the launcher (the gear next to the game version): mode, 3D resolution, detail, texture size, frame rate, V-sync and the FPS overlay. They're used the next time the game starts.
  • Fixed: the Linux build stopped in gsv.cpp with "redefinition of 'sync'" on distributions with GCC 14's C++ library (Ubuntu 24.04, Fedora, Arch, CachyOS). Probably #37.
  • Fixed: game version 1.0.0 could crash at the end of the intro movie, or when a looping movie started over.

Known issues

  • AMD (#11, #23, #29, #34, #35): still untested on AMD here. Please attach your host.log to your issue.
  • svcBreak when entering Crown City (#36) is still being looked into.
  • The first races can stutter while pipelines and textures are prepared (Bake textures in the launcher helps).

v0.2

Choose a tag to compare

@MIXIDtheSilly MIXIDtheSilly released this 16 Nov 13:11

The launcher now updates itself, there's a Linux version, pads vibrate, and several GPU crashes and black screens are fixed. AMD users: this is the first release with the AMD crash changes, so please try it and report back.

Important

This release contains no game code or data. You build the game yourself from your own dump. Don't use this with pirated copies: own the game and a Switch 2, and dump it from your own console.

Getting started

Windows: download kart-recomp-0.2-windows.zip, unzip it somewhere without spaces in the path, and run launcher\out\launcher.exe.

Linux: download kart-recomp-0.2-linux.tar.gz, unpack it, and run launcher/out/launcher (or ./kart.sh). You need a Vulkan 1.3 driver, SDL 3 (Fedora SDL3, Debian/Ubuntu libsdl3-0), g++ and Python 3.10+ with venv. See the README for the commands without a window.

Then follow the launcher's four steps: pick your dump (folder or .nup), click Set up, build (about half an hour the first time), play. Set up installs everything else into the folder, without admin rights or Visual Studio.

Updating

From 0.1.x (once): unzip 0.2 into a new folder, run its launcher, click Bring over an older version… on the first step, pick your old kart-recomp-… folder, then click Build. The shader translator changed, so the shader step runs again; the game's code is not recompiled.

From 0.2 on: the launcher checks GitHub when it starts and offers each new release once (Update to … at the top right if you said no). It downloads it, checks it, replaces only the files that changed, and starts again. Your build, saves and settings stay as they are. UPDATE_CHECK=0 in local.cfg turns the check off.

What's new in 0.2

  • The launcher updates itself from GitHub releases (see above). Scripted: launcher.exe --update.
  • Linux port: SDL 3 window, input and audio, the same launcher, and ./kart.sh setup | game | build | play | bake.
  • Controller vibration for Xbox, PlayStation and Pro Controller pads (thanks to Rafacasari, #27).
  • Fixed: sky and ambient lighting could freeze after a while in a race (thanks to Rafacasari, #28, closes #24).
  • Fixed: a GPU crash ("device lost") on NVIDIA from an effect shader on Koopa Troopa Beach and probably other courses (thanks to Rafacasari, #33).
  • Fixed: black screens. Videos in the menus and before the start stopped after one loop, and the screen could stay black before a race (thanks to Rafacasari, #33). A looping movie can no longer deadlock the decoder.
  • AMD GPUs: the game's shaders are written for 32-wide subgroups, and AMD GPUs can run 64 wide. Pipelines now ask for 32 where the GPU supports both. This is the suspected cause of the crash a few seconds in (#11, #23, #29, #34), but it's untested on AMD so far.
  • Crashes are logged: a crash inside the graphics driver or another module now writes a [RED] crash: line with a stack to host.log. The freeze report can no longer hang.
  • The shader step works without the lz4 package (Python 3.15, #30).
  • A program that can't be started is now named instead of a bare "[WinError 2]" (#22).
  • Bake textures shows progress in the launcher, and its worker processes stop when it ends.

Known issues

  • AMD: please try 0.2 and attach your host.log to your issue, even if it still crashes. Look for the nvk: subgroups and [RED] crash: lines.
  • A GPU crash ("device lost") can still happen now and then. A host.log from such a run helps.
  • A silent crash on some NVIDIA PCs (#26) is still being looked into.
  • The first races can stutter while pipelines and textures are prepared (Bake textures in the launcher helps).

v0.1.3

Choose a tag to compare

@MIXIDtheSilly MIXIDtheSilly released this 15 Nov 01:50

Updating no longer means building the whole game again: bring your older install over and Build only redoes what changed. This release also fixes the movie crash and makes the startup GPU crash much rarer.

Important

This release contains no game code or data. You build the game yourself from your own dump. Don't use this with pirated copies: own the game and a Switch 2, and dump it from your own console.

Getting started

  1. Download kart-recomp-0.1.3-windows.zip and unzip it somewhere without spaces in the path.
  2. Run launcher\out\launcher.exe.
  3. Follow its four steps: pick your dump (folder or .nup), click Set up, build (about half an hour the first time), play.

You need Windows 10/11 and a Vulkan 1.3 GPU. Set up installs everything else into the folder: Python, the .NET 10 SDK, the C++ compiler (LLVM MinGW) and the Python packages. It needs no admin rights and no Visual Studio.

Updating from an older version

  1. Unzip 0.1.3 into a new folder and run its launcher.
  2. On the first step, click Bring over an older version… and pick your old kart-recomp-… folder.
  3. Click Build.

This moves your build, the tools Set up installed, your saves, the pipeline and texture caches and your settings into the new folder (instantly, if both folders are on the same drive; from another drive they're copied). The old folder won't run afterwards.

Coming from 0.1.1 or 0.1.2, the update takes about 15 minutes instead of a full build. Installs from before 0.1.3 get each build step checked once, and the shaders are translated again. Future updates will skip everything that didn't change.

What's new in 0.1.3

  • Updates build only what changed. Each build step remembers which tools made it. Build reruns a step only when its output is missing or its tools changed, and then only the steps that depend on it.
  • Bring over an older version… on the launcher's first step (see above).
  • Fixed: the game could abort with an error when a movie was skipped or stopped, for example pressing a button during the intro movie or leaving a menu that plays a preview.
  • Fewer GPU crashes at startup. The title screen loads a random course behind the loading screen, and some of them could freeze the GPU a few seconds in ("device lost"). The renderer left a render pass open at the end of almost every frame; that is fixed, and in testing these crashes went from about 1 in 5 starts to about 1 in 30.
  • Movies that were hidden now show (thanks to Rafacasari, #21), and compressed textures no longer share images across incompatible formats.
  • The shader step works with Python 3.14 (thanks to EPScorp, #20).
  • The shader step no longer prints red "failed" lines for the one shader that can't be translated. That is expected: the game runs without it.
  • Scripted launcher runs: launcher.exe --bring-over <old folder> --build --quit --log build.log. The exit code is 0 when everything finished.
  • Files unzipped with older dates than your build are no longer missed when compiling. A change to the runtime headers now recompiles the game, and a change to the shader translator rebuilds it.
  • The launcher runs host\build.bat by its full path. On PCs where Windows doesn't run programs from the current folder (NoDefaultCurrentDirectoryInExePath), the last build step failed with "'build.bat' is not recognized".

Known issues

  • A GPU crash ("device lost") a few seconds after starting is rarer but can still happen, in some particle effects. Restarting the game picks another course for the title screen. A host.log from such a run helps.
  • Black screen with only the 2D elements drawn on some PCs (#18), and a crash a few seconds in on AMD GPUs (#11). Both are still being looked into.
  • One particle shader the GPU faults on in free roam is skipped, so an effect may be missing there.
  • The first races can stutter while pipelines and textures are prepared (Bake textures in the launcher helps).

v0.1.2

Choose a tag to compare

@MIXIDtheSilly MIXIDtheSilly released this 14 Nov 20:08

Local co-op with up to 4 controllers, Switch Pro Controller support, borderless fullscreen, and fixes for setup and for PCs with 16 GB of RAM. Versions 1.0.0 and 1.8.0 of the game are supported.

Important

This release contains no game code or data. You build the game yourself from your own dump. Don't use this with pirated copies: own the game and a Switch 2, and dump it from your own console.

Getting started

  1. Download kart-recomp-0.1.2-windows.zip and unzip it somewhere without spaces in the path.
  2. Run launcher\out\launcher.exe.
  3. Follow its four steps: pick your dump (folder or .nup), click Set up, build (about half an hour the first time), play.

You need Windows 10/11 and a Vulkan 1.3 GPU. Set up installs everything else into the folder: Python, the .NET 10 SDK, the C++ compiler (LLVM MinGW) and the Python packages. It needs no admin rights and no Visual Studio.

Coming from 0.1.1: unzip into a new folder and point it at the same dump.

What's new in 0.1.2

  • Local multiplayer for up to 4 players, one controller each (thanks @Rafacasari, #14). A controller joins as the next player on its first button press, and one that shows up twice is only counted once. HOST_PLAYERS=<1-4> caps the number of players (1 makes every controller drive player 1), and HOST_KEYBOARD_JOINS=1 lets the keyboard join as a player of its own.
  • Switch Pro Controller support over USB and Bluetooth (#14).
  • F11 toggles borderless fullscreen (thanks @Rafacasari, #15).
  • LAN Play (experimental): the game's LAN mode now works and is on by default. Allow the game through Windows Firewall when it asks. So far it has only been tested up to creating a room on one PC, not yet between two PCs. Online Play now goes back to the menu instead of hanging.
  • Fewer missing textures and less device loss on 16 GB PCs (#4): when the GPU can't map more host memory, memory that hasn't been used for a while is given back, and refused memory is tried again later.
  • Open .nup works before Set up: it installs the Python packages it needs first, instead of failing with No module named 'zstandard' (#16), and asks you to run Set up when Python isn't installed yet (#19).
  • The shader step no longer fails with "file does not exist" on two shaders some builds don't have (#17). Pipelines for shaders a build lacks are left out of the warm-up list.
  • The VC++ runtime now comes with the SPIR-V tools, so PCs without it can translate shaders.
  • The shader split shows progress in the launcher's bar, and reads file headers on several threads.
  • Movies: images that no frame will fill get their values when a movie is flushed or stopped.

Known issues

  • Black screen with only the 2D elements drawn on some PCs (#18), and a crash a few seconds in on AMD GPUs (#11). Both are still being looked into. A host.log from your run helps.
  • A GPU device loss can still happen, though rarely.
  • One shader the GPU faults on in free roam is skipped, so something may be missing from that scene.
  • The first races can stutter while pipelines and textures are prepared (Bake textures in the launcher helps).

v0.1.1

Choose a tag to compare

@MIXIDtheSilly MIXIDtheSilly released this 14 Nov 12:52

You no longer need to install anything to build, and the game runs about 50% faster. Versions 1.0.0 and 1.8.0 of the game are supported.

Important

This release contains no game code or data. You build the game yourself from your own dump. Don't use this with pirated copies: own the game and a Switch 2, and dump it from your own console.

Getting started

  1. Download kart-recomp-0.1.1-windows.zip and unzip it somewhere without spaces in the path.
  2. Run launcher\out\launcher.exe.
  3. Follow its four steps: pick your dump (folder or .nup), click Set up, build (about half an hour the first time), play.

You need Windows 10/11 and a Vulkan 1.3 GPU. Set up installs everything else into the folder: Python, the .NET 10 SDK, the C++ compiler (LLVM MinGW) and the Python packages. It needs no admin rights and no Visual Studio. Anything the PC already has (Python 3.13+, the .NET 10 SDK) is used instead.

Coming from 0.1: unzip into a new folder and point it at the same dump. The first build there compiles everything again with the new compiler.

What's new in 0.1.1

  • No Visual Studio, Python or .NET to install. The default compiler is now LLVM MinGW (clang). Set up downloads it and checks its SHA-256. Visual Studio is still an option on the Dependencies step.
  • About 50% faster. The clang build is much faster than the Visual Studio one: in a 1.8.0 race, uncapped, ~150 fps against ~97 on an RTX 3080.
  • The build brings its own tools: the SPIR-V tools and the shader translator's packages come with the repository (#6, #8), and Set up installs the Python packages (#3).
  • Clearer builds: a progress bar with time estimates for every stage, now also while the shaders are found in the game files, and the compiler's full output when a file fails (#2). That shader search also starts minutes sooner. An interrupted compile no longer leaves a broken object behind (#12). The huge main-module files that kept Visual Studio busy for a long time now compile in seconds to a minute (#10). The tools now run in UTF-8, whatever the system code page (#7).
  • Builds use every CPU core. Set BUILD_MP in local.cfg to use fewer.
  • Lean memory imports on PCs where the GPU can map little host memory, such as 16 GB RAM systems (#4).
  • Runs on Intel integrated GPUs (handheld PCs).
  • Fewer texture hitches: sparse textures are cheaper, and textures are read ahead.
  • Movie fixes for the end of a movie and for a movie that is stopped.
  • The pipeline cache is never saved from a lost device, and it is checked when it loads.

Known issues

  • A GPU device loss can still happen, though rarely.
  • One shader the GPU faults on in free roam is skipped, so something may be missing from that scene.
  • The first races can stutter while pipelines and textures are prepared (Bake textures in the launcher helps).
  • A crash on an AMD RX 6700 XT (#11) is still being looked into.

v0.1

Choose a tag to compare

@MIXIDtheSilly MIXIDtheSilly released this 12 Nov 20:51

The first release of kart-recomp: a native Windows port of the Switch 2 kart game, made by static recompilation. Versions 1.0.0 and 1.8.0 of the game are supported.

Important

This release contains no game code or data. You build the game yourself from your own dump. Don't use this with pirated copies: own the game and a Switch 2, and dump it from your own console.

Getting started

  1. Download kart-recomp-0.1-windows.zip and unzip it somewhere without spaces in the path.
  2. Run launcher\out\launcher.exe.
  3. Follow its four steps: pick your dump (folder or .nup), check dependencies, build (about half an hour the first time), play.

You need Windows 10/11, a Vulkan 1.3 GPU, Visual Studio 2026 with C++, Python 3.13+ and the .NET 10 SDK.

What's in 0.1

  • Native NVN-on-Vulkan renderer: races at a steady 60 fps, with ~140 fps of headroom uncapped on an RTX 3080
  • Unified-memory mode for integrated GPUs and handheld PCs (turns on by itself)
  • Xbox, DualShock 4 and DualSense controllers, plus keyboard
  • Movies (with Microsoft's VP9 Video Extensions), audio, saves
  • Launcher with .nup unpacking and side-by-side 1.0.0 / 1.8.0 builds

Known issues

  • A GPU device loss can still happen, though rarely
  • One shader the GPU faults on in free roam is skipped, so something may be missing from that scene
  • The first races can stutter while pipelines and textures are prepared (Bake textures in the launcher helps)