Tears of the Kingdom PC Port Troubleshooting
For TotK Recomp, the tool that builds your Switch files into a PC game, choose won't start, black screen or crashes during play to get the next action. UltraTears and Weeping symptoms have separate groups below.
On this page
Find Your Symptom
Symptom First thing to try Detailed helpFixed in newer versions
| Symptom | Fixed in | Detailed help |
|---|---|---|
TotK Recomp old 0xc0000409 crashUpdate the older build. | v0.3.1 | Startup |
| TotK Recomp old high-refresh crashUpdate the older build. | v0.3.1 | Startup |
| TotK Recomp old non-AVX startup crashUpdate for the runtime correction. | v0.3.4 | Startup |
| TotK Recomp sound stops in older buildsUpdate for audio pacing. | v0.3.4 | Older audio |
| TotK Recomp old black ground squaresUpdate the older build. | v0.3.1 | Ground squares |
| TotK Recomp old Intel black flicker/device lossUpdate for Intel memory handling. | v0.3.4 | Older graphics fixes |
| TotK Recomp old camera recognition faultUpdate the older build. | v0.2.8 | Camera |
| TotK Recomp old level-change crashUpdate for nvnQueueSubmitCommands correction. | v0.3.4 | In-game crashes |
| TotK Recomp old save fails after first startUpdate and keep the failing path. | v0.3.4 | Old save loading |
UltraTears Symptoms
Symptom First thing to try Detailed helpFixed in newer versions
| Symptom | Fixed in | Detailed help |
|---|---|---|
| UltraTears old missing Depths groundUpdate for AMD/Deck terrain. | v0.3.0 | Depths and cloth |
Weeping of the Empire Symptoms
Symptom First thing to try Detailed helpFixed in newer versions
| Symptom | Fixed in | Detailed help |
|---|---|---|
| Weeping old Visual C++ startup crashUpdate the older build. | v0.1.6.1 | Setup |
Weeping old No module named cryptographyUpdate the older build. | v0.1.6.1 | Setup |
| Weeping old optional-font failureUpdate; right-click clears the input. | v0.1.8 | Fonts |
| Weeping old red grass with positive LOD biasUpdate the older build. | v0.1.8 | Red grass |
| Weeping old opening movie too fastUpdate for movie timing. | v0.1.7 | Older movies |
| Weeping old cutscene loading without VP9Update for the built-in decoder. | v0.1.7 | Older movies |
| Weeping old fast-travel crash with 8 GB RAMUpdate for memory handling. | v0.1.8.2 | Older movies and crashes |
| Weeping old high-FPS shrine-entry hangUpdate the older build. | v0.1.8.1 | Older movies and crashes |
| Weeping old audio cracklesUpdate for reverb correction. | v0.1.8 | Older audio |
Game Won't Start, Crashes or Shows a Black Screen
Start the Correct Program
Open totk.exe on Windows or totk on Linux for TotK Recomp; F1 opens its settings. UltraTears starts through Play in the launcher, while Weeping uses TotK Launcher.exe. Full preparation and first-launch steps are on Installation Guide.
Let Graphics Preparation Finish
Let Setup prepare shaders, the small programs that draw graphics, before opening TotK Recomp. If you stop Setup, reopen it on the same folder to continue from its last completed stage; use installation step 4 for the timing example and preparation steps.
UltraTears can repeat graphics preparation after a driver change; Weeping reuses its graphics cache, while new uncached areas can still stutter.
TotK Recomp Startup
- Use the current Setup for older
0xc0000409, high-refresh and Intel UHD upload crashes. - Keep the advanced CPU option at its default (
free_cores = 0); enabling that experimental option can crash or hang. - Older non-AVX startup crashes were Fixed in v0.3.4; update an older build.
- Remove old workaround overrides before comparing the current defaults; use the report checklist for a remaining failure.
Startup report hardware and versions
An old Windows crash report uses v0.1.1, RX 6900 XT, AMD 26.10.1, Windows 11 26H2 and game 1.4.3. A separate Ally X report uses v0.2.8, Bazzite, RADV PHOENIX and game 1.4.3, closing after Nintendo Presents. Match the platform before choosing an old workaround.
UltraTears GPU and Memory
- Run the current launcher's GPU check and read any incompatibility message.
- Compare the GPU's required extensions and the 16 GB RAM / 4 GB VRAM thresholds on System Requirements. For a continuing loading failure, preserve the log and use UltraTears Issues.
Memory-failure report
One v0.1.0-beta loading report runs on an ASUS Vivobook Go15, Ryzen 5 7520U, Radeon 610M, 8 GB shared RAM, Windows 11 Pro 25H2 and driver 32.0.21045.16010 with game 1.4.3. Loading fails with an out-of-device-memory graphics error.
Weeping Setup Failures
Older Visual C++ startup and Python package failures were Fixed in v0.1.6.1; use current Weeping Setup for an older installation. A stopped Setup failing at step 5 on non-English Windows was Fixed in v0.1.8.2.
Weeping Optional Font Input
Report hardware and version
The v0.1.6.1 report uses Ryzen 5 5500, RX 6650 XT 8 GB, 32 GB RAM, Windows 11 25H2 and 1920×1080 output.
Older optional-font verification failures were fixed in v0.1.8; update Setup, and right-click the Firmware row to clear an unwanted selection.
Graphics Glitches
TotK Recomp Black Screen on Windows
- Update an older package using the current Setup.
- Return graphics options changed for old workarounds to their defaults before comparing the current version.
- Check the GPU and driver against System Requirements.
For a continuing black screen, keep the failing run’s log and the GPU/driver details for the report checklist.
TotK Recomp Black Ground Squares
Intel black flicker/device loss, Depths terrain shimmer and ultrawide world-marker errors in older builds were Fixed in v0.3.4.
Update through Setup for the old 64-pixel ground-square fault; the current package replaces the old shader translator responsible for that symptom.
TotK Recomp Black World
Graphics report conditions
The report uses Xeon E5-2666 v3, RX 470 4 GB, Windows, AMD 26.5.2, game 1.4.3, a 144 FPS cap, render scale 100 and GPL 0. The port tag was omitted from the report.
A black world with the interface still visible has a separate RX 470 report. If it persists after updating, preserve the new log and match the original hardware and settings when reporting it.
UltraTears Depths and Cloth
Missing Depths ground, cave walls and dark Link lighting on AMD/Deck were Fixed in v0.3.0; update the older build. Cloth tearing was reported in v0.2.0; if it remains after updating, keep a current log with UltraTears Issues. Rare distant white/red circles remain open in v0.3.0; include the scene and log with a report.
Weeping Red Grass
Report hardware and version
The v0.1.6.1 report uses Ryzen 5800X3D, RTX 5070, NVIDIA 617.14, 32 GB RAM, Windows 11, 2560×1440 output and Texture LOD bias +2.
Red grass with positive Texture LOD bias was fixed in v0.1.8; update an older installation.
Crashes During Play
For an old Weeping installation, movie timing, opening-movie crashes and cutscene loading without VP9 were Fixed in v0.1.7 with a built-in decoder; update the program. The high-frame-rate shrine-entry hang was Fixed in v0.1.8.1, and fast-travel crashes on affected 8 GB RAM PCs were Fixed in v0.1.8.2.
Weeping Current Graphics and Camera
Camera object recognition, Intel Arc shader crashes/white patches and several keyboard actions still need fixes; keep the current log, GPU/driver and scene with Weeping Issues. Use Enter to add each material while the keyboard fix is pending. If generated frames drop to half rate on a fixed-refresh display, leave frame generation Off; the correction is planned for v0.1.9. Above 30 FPS, cutscenes can briefly show loading objects after the shrine-hang correction.
TotK Recomp Crashes During Play
Older level-change crashes in nvnQueueSubmitCommands and failures loading an old save after the first start were Fixed in v0.3.4; update the older program.
Use the current program package before comparing an older crash report; early development still includes visual bugs and crashes. If the failure repeats, preserve the scene, changed settings and the failing log using the report checklist.
Movie Report Conditions
- Opening movie: Ryzen 5800X3D, RX 9070 XT, 32 GB RAM, Windows 11, game 1.0.0 and a high-frame-rate opening; port tag omitted.
- Missing decoder: v0.1.6.1, Ryzen 5 4500, RX 6600, AMD 26.10.1, Windows 10 IoT LTSC 21H2 and 1920×1080.
TotK Recomp Camera Recognition
Camera object-recognition failure was fixed in v0.2.8; update the program if using an older build.
Camera report hardware and version
The original report uses v0.1.1+701bd62, Windows 11, RTX 5070 Ti and game 1.2.1.
Audio Problems
TotK Recomp Audio in Older Builds
Audio report and version history
The sound-loss report began on v0.1.1+701bd62 with an RTX 4060, driver 610.88 and 48 kHz stereo, with a v0.2.8 follow-up. Earlier community patch attempts were withdrawn or failed in follow-up tests; the later official release includes the audio-pacing correction and the issue is now closed.
Sound dropout, seam clicks and grainy reverb in older builds, including v0.3.1, were fixed in v0.3.4; update the old installation after making a save backup.
Weeping Audio
Weeping report conditions
The report uses Ryzen 7 9800X3D, RTX 3080 and 32 GB RAM on v0.1.6.1.
Reverb static, buzz and crackle in older Weeping builds were fixed in v0.1.8; update an older installation. If you added env.TOTK_AUX=bypass to player.txt for that fault, remove the old override after updating.
Controller Not Working
- Check
totk.logforinput: no gamepadand compare detection with your selected layout and bindings. - For Switch 2 Pro on Windows, check which controller the bridge exposes; the emulated DualSense route can expose gyro tilt/rotation controls.
- Run one bridge at a time and check whether Steam Input, Steam’s controller remapping system, has claimed the device.
A later-connected gamepad is detected in about a second. For UltraTears mouse-camera input, use the camera keys or a controller; for its older stick or resting-gyro drift, use the release's updated dead zone, the small stick movement ignored near its centre, and gyro drift handling.
Update or Game Files Not Working
- 1Check the actual supported game version on Game Files, or use the older installation route if Setup used the old “1.1.1” label.
- 2For another preparation attempt, run Setup on the existing folder; it reuses verified steps and retains saved progress.
Use the separate update routes on Updates for that old label.
Is It a Bug? How to Get Help
Match the project, system, game version and failing stage in TotK Recomp Issues, UltraTears Issues or Weeping Issues. Keep the log from the failing run before opening the game again.
- Project release or exact development build, plus game version.
- Operating system, CPU, GPU, RAM and graphics-driver version.
- Changed settings and the failing scene.
- Steps to reproduce the failure and what happened.
- The log from that failing run.
Project release or exact development build, plus game version: Operating system, CPU, GPU, RAM and graphics-driver version: Changed settings and the failing scene: Steps to reproduce the failure and what happened: The log from that failing run:
| Project / system | Log location |
|---|---|
| TotK Recomp / Windows, Linux, Deck | <install>/totk.1.logtotk.4.log; previous four: through . |
| UltraTears / Windows, Linux, Deck | ultratears.logultratears-previous.logBeside the game: ; previous run: . |
| Weeping / Windows | %LOCALAPPDATA%\launcher.log; launcher: . |
Review personal paths before sharing logs; keep game files, keys and firmware out of the report.
Sources
Checked November 3, 2026.
- TotK Recomp project github.com
- TotK Recomp v0.3.4 release github.com
- Project feedback github.com
- TotK Recomp tester guide github.com
- Weeping launcher and logs github.com
Zelda PC Guide