ryubing crash on startup fix

Ryubing is the active continuation of Ryujinx, and it inherits the same startup-crash behaviour: the emulator opens, you pick a game, and it dies before the first frame. The issue tracker calls it “crashes on booting up a game”, “crashes instantly when trying to open a game”, and “any game crashing upon startup”.

Because Ryubing tracks Ryujinx’s codebase, the fixes are the same — but Ryubing releases more often, so “update the build” is a stronger first move here than it was on the ended project.

1. Backend can’t see your GPU

Ryubing renders through Vulkan. If the device doesn’t initialise, the crash lands when a game starts drawing, not at launch.

1. Open Settings → Graphics and confirm Vulkan
   Vulkan is the tested default. If it's unset or your driver can't provide a Vulkan device, the renderer fails on game load. On macOS, make sure you're on a build that supports your Metal backend.
   The log shows a Vulkan (or Metal) device created successfully.
2. Update the GPU driver, or update Ryubing
   On Windows this is a driver update. On macOS it's often a Ryubing update — Apple's GPU stack changes between OS releases, and a current build tracks them. A "GPU not detected" log line means one of the two is stale.
   The crash stops at the same launch point.

2. Corrupted cache from a previous crash

1. Clear shader and PPTC caches
   Use Tools → Clear Cache for both Shader Cache and PPTC Cache. A cache written during a crash can make every subsequent boot crash at the same spot.
   The game recompiles shaders instead of loading a broken cache.

3. Controller or file-lock edge cases

1. Remove a controller profile if boot crashes only with a pad plugged in
   A configured gamepad has triggered boot-to-game crashes on specific builds (an NpadController motion regression). Remove the profile and retry; if it boots, update Ryubing.
   The game reaches its title screen with the pad removed.
2. Close File Explorer windows on the game folder
   Open Explorer windows can lock files Ryubing's filesystem layer needs to commit, which surfaces as a crash on open. Close them and relaunch.
   The game opens without a filesystem error in the log.

Still crashing?

Keys and firmware problems masquerade as startup crashes — see prod keys and firmware mismatch. If it crashes mid-session instead, that’s the mid-game crash fix.