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 helpFixed in newer versions
| Symptom | Fixed in | Detailed help |
|---|---|---|
| Older CPU without AVX2Use Alpha 3's automatic compatible mode. | Alpha 3 | Older CPU guide |
| Old movie or language crashesUpgrade Alpha 2 to Alpha 3. | Alpha 3 | Crashes 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
- For a FUSE startup error, use your distribution's
fuse3package or the--appimage-extract-and-runoption in Installation Guide → Linux.
ARM64 File Preparation
- 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
Game files aren't version 1.8.2 / 1.9.0It has no System/Version.txt.- Select the common parent containing
exefs/andromfs/. - Use Switch 1.9.0 base content merged with its matching update; match the executable build ID with
romfs/System/Version.txt. - 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
LibCStdLibHeaderNotFound- 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
could not copy libgcc_s_seh-1.dll: Permission denied- 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
- Black-launcher cache recovery: RX 9070 XT on 0.3.0-alpha.3 and ROG Ally Z1 Extreme, whose exact Alpha 3 version was unspecified.
- Intel: a Celeron 6305 report reached gameplay during the Alpha 3/hotfix discussion; the successful change was unspecified.
- BotW-Native: three startup reports, with a second confirmation and a third, succeeded after removing DLC; exact port versions and hardware were unspecified.
- Older CPUs: Alpha 1 and Alpha 2 required AVX2; Alpha 3 selects x86-64-v2 automatically for compatible processors. The i5-3470 report uses Alpha 3.
Graphics Glitches
FOV Shadow Faults
- 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
- 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
- On Savage Wind Linux, check that the system driver supports the controller; basic buttons use that driver.
- For vibration or motion, check
hidrawsensor access; Steam's udev rules supply Linux device permissions. - If Steam supplies a virtual controller without sensors, test Disable Steam Input and keep a new log.
- 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
- Savage Wind: match the main build ID and
System/Version.txtafter merging base and update; files must reach the version-specific 95% reference count. - BotW-Native: check the updated USA
U-King.rpxchecksum andBootup_USen.pack. - 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.logorruntime.log, and whether startup, setup or play failed.
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.logData folder, normally beside the program: . |
| Savage Wind / Linux | ~/ without a terminal; terminal output for a terminal launch. |
| BotW-Native / Windows | %APPDATA%/; 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.
Sources
Fact checks: October 29–31, 2026.
- BotW-Native v0.1.1 release notes github.com
- Savage Wind 0.3.0-alpha.3 release notes github.com
- Savage Wind 0.3.1-alpha.3 hotfix release notes github.com
- Savage Wind 0.3.0-alpha.3 README github.com
- BotW-Native v0.1.1 README github.com
Zelda PC Guide