Find your guide

Independent port guide.

Troubleshooting · Savage Wind Recomp / BotW-Native

Breath of the Wild PC Port Troubleshooting

For a black Savage Wind launcher on Windows, reset AMD's shader cache or use the Intel hotfix; for a crash after Play, use the matching startup guide.

On this page

Find Your Symptom

Symptom First thing to try Detailed help
StartupWhich program to open / long first setupTry first: Start the matching program and check the setup stage.Launch and setupStartup · LinuxLinux AppImage FUSE errorTry first: Use fuse3 or extract-and-run.AppImage startupStartup · Linux · ARM64Linux ARM64 file preparation stopsTry first: Keep the setup log; the fix is planned for Alpha 4.ARM64 preparationStartup · AVX2Older CPU without AVX2Try first: Use Alpha 3's automatic compatible mode.Older CPU guideStartup · AMD · Intel · WindowsBlack launcher / AMD or Intel WindowsTry first: AMD: reset shader cache; Intel: use the hotfix.Black-window guideStartup · NVIDIA · GTX 10-seriesGTX 10-series / address-write-invalid-0 crash after PlayTry first: Run the two commands in Command Prompt.NVIDIA startup guideStartup · BotW-NativeBotW-Native opens and closesTry first: Check merged USA files and keep DLC separate.Wii U startup guideStartupWrong version / missing game filesTry first: Select the updated base game's parent folder.File checksStartup · DeckDeck compilation errorTry first: Keep the failing build log.Deck build failureStartup · BotW-NativeBotW-Native DLL copy / missing sourceTry first: Use the complete build-fix release ZIP.Build errorsGraphics · RX 560 · LinuxRX 560 Linux black pause menuTry first: Use the temporary launch option and game fullscreen.Linux menu guideGraphics · AMD · WindowsAMD Windows colored terrain blocksTry first: Test Anisotropic filtering Off.AMD terrain guideGraphicsDark bands / moving cloud or edge shadowsTry first: Return above-100% FOV to 100%.FOV faultsGraphics · SteamOSSteamOS handheld transparency / fuzzy LinkTry first: Test Anisotropic filtering Off for fuzziness.Handheld graphicsAudioNo soundTry first: BotW-Native: check volume and mute; keep a log for persistent silence.AudioControllerNo controller input / motion / double inputTry first: Check the driver, sensor access and Steam Input.Controller checksUpdate or DLCUpdate or DLC missingTry first: Match base/update versions and check DLC support.Update and DLC checksGet HelpCrash after a longer session / another bugTry first: Keep the failing run's log and reproduction steps.Report checklist

Fixed in newer versions

SymptomFixed inDetailed help
Older CPU without AVX2Use Alpha 3's automatic compatible mode.Alpha 3Older CPU guide
Old movie or language crashesUpgrade Alpha 2 to Alpha 3.Alpha 3Crashes during play

Game Won't Start, Crashes or Shows a Black Screen

Start the Correct Program

Run savagewind.exe on Windows or the Linux AppImage for Savage Wind; Configuration or --config reopens setup. For BotW-Native, open BotW-Native-Setup.exe or BotWLauncher.exe and select Play; the manual game executable is BotWRecomp.exe.

First setup builds game code for the processor and prepares shaders, the small graphics programs used by your device. Later launches reuse shader and pipeline caches; clearing them or changing an incompatible Vulkan/application build can trigger preparation again. Preparation on first use can still pause play.

First-Setup Timing

The desktop release estimates about 6 minutes for code on 12 threads, plus copying and shaders. The Steam Deck maintainer test, using 0.3.0-alpha.3, SteamOS 3.8 and Mesa 26.2, took about 16 minutes for code and 7 minutes for shaders.

Linux AppImage Won't Open

LinuxWorkaround
  1. For a FUSE startup error, use your distribution's fuse3 package or the --appimage-extract-and-run option in Installation Guide → Linux.

ARM64 File Preparation

LinuxARM64Fix planned
  1. For the experimental Linux ARM64 package's preparation failure, keep the setup log and follow the ARM64 preparation report; its fix is planned for Alpha 4.

Game Files Cannot Be Found

Error message
Game files aren't version 1.8.2 / 1.9.0
Error message
It has no System/Version.txt.
Switch
  1. Select the common parent containing exefs/ and romfs/.
  2. Use Switch 1.9.0 base content merged with its matching update; match the executable build ID with romfs/System/Version.txt.
  3. Check the complete layout with Game Files.

For BotW-Native, check the updated USA code/U-King.rpx checksum and content/Pack/Bootup_USen.pack using the Wii U startup guide.

Steam Deck Build Failure

Error message
LibCStdLibHeaderNotFound
Steam DeckFix planned
  1. Keep the failing setup log and use Steam Deck setup problems.
Report conditions

One SteamOS 3.9.5 player completed Alpha 3 setup after changing system headers; the maintainer completed a separate test build. Bundled-glibc handling is planned for Alpha 4.

BotW-Native Build Errors

Error message
could not copy libgcc_s_seh-1.dll: Permission denied
BotW-NativeWindows
  1. Close the game and launcher, then use the complete Windows release ZIP for the DLL-copy failure or missing CMakeLists.txt; follow Updates.

NVIDIA Startup Workaround

Run the two commands in Command Prompt using the NVIDIA startup guide.

Startup Report Conditions

Graphics Glitches

FOV Shadow Faults

Fix planned
  1. For dark bands, fast cloud shadows or edge shadows above 100% FOV, set Field of view to 100%. The shadow-cascade fix is planned for Alpha 4; one edge-shadow case uses 90%. Use Settings for the FOV controls.

SteamOS Handheld Graphics

SteamOSAlly XOneXPlayer Apex
  1. Test Anisotropic filtering Off for fuzzy Link on Ally X; that helped one report, while OneXPlayer Apex's transparent-terrain issue remains open. Use Steam Deck's handheld reports for those devices.

Full Graphics Report Conditions

  • Linux pause-menu fault: RX 560 on 0.3.0-alpha.3, involving the feedback-loop graphics path; the workaround restored the menu at about a 20 FPS cost.
  • AMD terrain: RX 570 and RX 580 reports use 0.3.1-alpha.3; AF Off reduced artifacts on the RX 580 but left some blocks. A fix for an unnecessary cube-map compatibility flag is on the Alpha 4 test branch.
  • FOV reports: RTX 2070 SUPER on a reported Linux 0.3.1-alpha.3 build, RX 6950 XT on 0.3.0-alpha.3, and RTX 3060 on Windows 0.3.1-alpha.3.
  • Handhelds: OneXPlayer Apex names Linux 0.3.1-alpha.3; Ally X omits its version. The published Linux asset is 0.3.0-alpha.3; the two reported Linux 0.3.1 build identities were unspecified.

Crashes During Play

Symptom First action Report
Great Plateau Tower movie crash on Alpha 2 Update to Alpha 3 for the movie-crash fix. Movie report
Alpha 2 title-screen crash with mixed text/voices Update to Alpha 3; Same as text was the old workaround. Language report
Toto Sah apparatus blocks progress on Deck OLED Test Disable Steam Input and keep a new log. Motion report

The Toto Sah report uses 0.3.0-alpha.3. For a longer-session crash, keep the failing run's savagewind.log or runtime.log, the scene, reproduction steps and graphics settings.

Audio Problems

Symptom First action Report
Savage Wind silent opening on Deck Keep the log and report the silent scene. 0.3.0-alpha.3 report
BotW-Native silence Check PC/game volume and the --mute option. Author's demo

The BotW-Native author corrected the untagged Windows demo's silence after finding PC audio muted. For persistent silence, attach the runtime log and exact reproduction steps.

Controller Not Working

Savage WindLinux
  1. On Savage Wind Linux, check that the system driver supports the controller; basic buttons use that driver.
  2. For vibration or motion, check hidraw sensor access; Steam's udev rules supply Linux device permissions.
  3. If Steam supplies a virtual controller without sensors, test Disable Steam Input and keep a new log.
  4. For double input, check whether Steam's Desktop Mode layout also sends keyboard/mouse events.

The sensor diagnostic comes from the Deck OLED 0.3.0-alpha.3 report. For motion drift, hold the controller still while Savage Wind adjusts its resting gyro offset; stick deadzone controls stick input separately.

Savage Wind supports connecting controllers while running. If input stops after reconnecting or waking the PC, include that exact sequence and the failing log in your report.

Update or DLC Not Working

  1. Savage Wind: match the main build ID and System/Version.txt after merging base and update; files must reach the version-specific 95% reference count.
  2. BotW-Native: check the updated USA U-King.rpx checksum and Bootup_USen.pack.
  3. DLC: neither native project has an available installation method; Savage Wind Alpha 3 has no support and BotW-Native has no DLC test results.

Savage Wind Configuration can rebuild code or delete prepared data; BotW-Native can rerun its local build after selecting the correct merged USA folder. Use the updated base-game requirements on Game Files.

Is It a Bug? How to Get Help

Match the project, release, operating system and failure stage in Savage Wind Issues or BotW-Native Issues. Read why a ticket closed: it may be a duplicate, an unexplained closure or a fix waiting for release; use the version named in the fix.

  • Project, exact release or development commit, and game version.
  • OS, CPU, GPU, driver version and selected graphics device.
  • Resolution, frame-rate cap, VSync, upscaling, shadows and custom overrides.
  • Scene, reproduction steps, expected/actual result and a useful screenshot.
  • Failing run's savagewind.log or runtime.log, and whether startup, setup or play failed.
Project / system Log location
Savage Wind / Windows
savagewind.log
Data folder, normally beside the program: .
Savage Wind / Linux
~/.local/share/savagewind/savagewind.log
without a terminal; terminal output for a terminal launch.
BotW-Native / Windows
%APPDATA%/BotWRecomp/runtime.log
; BOTW_USER_ROOT or the launcher's user-folder setting can override it.

Review personal paths in logs before posting; keep error messages, versions and device details useful for diagnosis.