LONGSHOT / WINDOWS & LINUX

Longshot on PC: install, build and move saves

Use the stable Longshot Launcher on Windows or Linux to build your supported Switch 2 copy of Ocarina of Time. Import Hookshot progress after making a backup.

On an Apple silicon Mac, choose Ship of Harkinian for a supported N64 ROM or Ocarina ReTuned for a supported decrypted 3DS copy.

English Longshot Launcher welcome screen with a Build button and v3.0.0 marked stable.
Launcher v1.0.0 English welcome screen, rendered from source with sample data. Follow the build steps ↓

Guide checked 19 November 2026 · Launcher v1.0.0 · Game/Builder v3.0.0. On a Mac? Choose a Mac route ↓

Find the official Longshot source and player download

The official repository is MagicBeanDev/Longshot on Forgejo, linked from longshot.magicbean.dev. Its launcher has a separate repository. Use those sources when looking for “Longshot GitHub”; an old GitHub fork can have no current player downloads.

YOU OPENLongshotLauncherv1.0.0

Choose files, build, update and manage saves.

IT DOWNLOADSLongshot Builderv3.0.0

Checks and builds the supported game on your PC.

YOU PLAYYour local game

Press Play after the build and shader preparation finish.

Download the Launcher for normal setup. The core repository's Builder ZIP and AppImage are build tools used by the launcher, with advanced command-line uses. They are separate from the player-facing Launcher packages below.

Windows · installed

LongshotLauncher-v1.0.0-windows-x64-setup.exe

Choose Install on first start. The launcher installs for your Windows user.

Get the Windows launcher ↗

Windows · portable

LongshotLauncher-v1.0.0-windows-x64-portable.zip

Extract the whole ZIP, then open LongshotLauncher.exe. Keep its portable marker and data folder together.

Get the portable launcher ↗

Linux / Steam Deck

LongshotLauncher-v1.0.0-x86_64.AppImage

Make the AppImage executable, then open it. Build and play from the launcher.

Get the Linux launcher ↗

The buttons follow the official Stable channel. To get the exact packages listed here, open the Launcher v1.0.0 release. A fresh setup defaults to Stable and builds Longshot v3.0.0.

Match your game files before starting the build

Program
0400486024DEC000
Update
v131072
Build
e0f3ccfa

Supply your own .nup, or the extracted romfs and exefs folders for that supported game. An N64 ROM, a 3DS ROM or another update needs a different route. The launcher checks the input; changing the filename does not change its version.

  • System: 64-bit Windows 10/11, or x86-64 Linux with glibc 2.35 or newer.
  • CPU and graphics: the published requirements estimate a 6-core CPU and a Vulkan 1.3 GPU. Mesh shaders are recommended; a compute fallback exists for supported cards without them.
  • Memory: 16 GB RAM and 4 GB VRAM with the in-game Minimum (4GB) preset in the published estimates. The upstream guide recommends 32 GB RAM and 12 GB or more VRAM. Some scenes can need more memory.
  • Disk and network: about 60 GB free while building, preferably on an SSD, plus internet for the launcher and build tools.

Use the launcher's requirements panel to check the selected PC and GPU. These are upstream estimates, rather than a frame-rate target. See the system requirements and GPU notes if the panel reports a missing capability.

Install the launcher, then build your local game

Windows

Open the setup executable and choose Install, or extract the portable ZIP and run LongshotLauncher.exe. Installed and portable copies keep their data in different places; keep using the same copy for your library.

Linux / Steam Deck

In the file manager, allow the AppImage to run as a program, then open it. From its download directory, you can set that permission with:

Make the Linux launcher executable
chmod +x LongshotLauncher-*-x86_64.AppImage
  1. Press Build on the welcome screen

    A fresh setup shows Stable and Game/Builder v3.0.0. If an older launcher saved a different choice, use Change to pick Stable before building. See Track and Version if you already have a build.

  2. Select your game files

    In Game files, choose a detected file or use Browse…. For an extracted dump, choose romfs and exefs folders. Wait for both the input check and the builder-tools download; Next becomes available when the required inputs are ready.

  3. Choose the destination, language and options

    In Settings, check the drive's free space and choose your game language. The default games parent is Games\Longshot under your Windows user folder or ~/Games/Longshot on Linux. Optional DLSS, FSR 4 or XeSS choices depend on the build and hardware. Windows with Intel graphics also has Intel shader compiles; Auto is the default for a fresh setup. Existing saved choices carry over.

  4. Build, including shader preparation

    Press Build v3.0.0 and keep the window open through file processing, compilation and shader preparation. Time varies by PC, drive and driver. A failed stage needs its error or log checked; elapsed time alone does not tell you whether the build has stopped. Use the new reporting controls only after reviewing what they send.

  5. Press Play and check the expected progress

    When the ready screen appears, press Play. You can add shortcuts from that screen. If you brought a save, load the expected slot before continuing; for new progress, save and quit before making your first backup.

Detected sample NUP above the Browse option.

Select the detected file or use Browse.

The romfs and exefs folders input option.

Use both extracted folders for a folder input.

Find your input in Game files

Pick the detected file, use Browse, or choose the two extracted folders. Next waits for file selection and the builder tools. The source-rendered example uses a sample file and compatibility check.

Image source ↗
View the complete window Longshot v1.0.0 lists a sample supported NUP in the Game files step.Open full-size image ↗
How do I make the launcher use English?

Open the home screen's cog, then choose the launcher's language in Settings. That changes the launcher interface. The game's language is a separate choice in each build's settings.

Choose Intel shader mode and reporting options

The wizard's Build settings apply to that game build. The home-screen cog opens the launcher's Settings, including its language, update channels and reporting choices.

Windows with Intel graphics: start with Auto

In Build settings → Intel graphics → Intel shader compiles, Auto leaves the decision to the game and lets you change its own menu row. For a fresh setup, Auto is the default; an older saved preference can remain selected after an update.

Intel shader compiles is set to Auto.

Choose Auto to follow the game’s decision.

Shader time limit is set to Normal.

Keep the time limit on Normal for a first build.

Intel Auto leaves the game's setting available

Launcher v1.0.0 Build settings with an example Intel GPU. Auto and Normal are selected.

Image source ↗
View the complete window Longshot v1.0.0 Build settings shows Intel shader compiles and Shader time limit.Open full-size image ↗
Auto
The game chooses the shader mode. Its own setting remains changeable.
Side by side
Forces parallel shader compilation for the build and game. It can be faster, but can also crash or freeze Intel's driver.
One at a time
Forces serial shader compilation. It is slower and overrides the game's own row too.
My old Intel choice changed, or shader preparation times out

The old Side by side choice stays Side by side. The old One at a time choice maps to Auto: that older choice left the decision to the game. Choose the new One at a time explicitly to force serial compilation.

For the specific slow-driver wait, Shader time limit → Longer extends the preparation wait to 30 minutes instead of 5, and the final pipeline wait to 3 minutes instead of 30 seconds. It does not fix an unsupported GPU or a different crash. Return it to Normal to undo that change.

Choose what the launcher sends

Open the home-screen cog, then scroll down in Settings. Performance statistics and automatic crash reporting are separate choices; both start off. You can leave them off and still build and play.

Send performance statistics is unchecked.

Performance statistics starts off.

Send crash reports automatically is unchecked.

Automatic crash reporting has its own switch.

Statistics and automatic crash reports have separate switches

Launcher v1.0.0 Settings with an example profile. Keep a copy of what was sent is available when performance statistics is enabled.

Image source ↗
View the complete window Longshot v1.0.0 settings with separate performance and crash reporting checkboxes.Open full-size image ↗

Send performance statistics

Opt in to send frame and system summaries, plus how builds ended and how long their stages took. Keep a copy of what was sent keeps sent game-performance summaries in perf_sent in the game folder.

Untick statistics to stop it. The game-performance guide says this also clears its pending summaries and retained copies.

Send crash reports automatically

Opt in separately to let the game post its crash report publicly on Longshot's crash issue, including system details and the log's end. With it off, the game asks in its crash window. Untick it to return to that prompt.

Review a failed build report before sending it

  1. On The build stopped, choose Show what is sent and review the diagnostic report.
  2. Choose Send to the team only when you want to post it publicly on Longshot's build-failures issue. The report can include the final 200 log lines, with the home folder shortened to ~; it excludes game files and saves.
  3. After a successful send, See it opens the resulting report. For a local copy instead, use Copy for a bug report.
Send to the team and Show what is sent actions.

Open Show what is sent before posting a report.

Read the report before choosing Send to the team

Launcher v1.0.0 failure page with a sample compiler error. Use Show what is sent to review the report.

Image source ↗
View the complete window Longshot failed-build page showing Send to the team and Show what is sent.Open full-size image ↗

Update the game and launcher separately

On home, use Track and Version for the game build you want to play, update or rebuild. In the home-screen cog, Channel for new builds sets the starting choice for new builds. Launcher updates sets the launcher’s own update channel.

Track and Version selectors on the launcher home screen.

Choose the Track, then the Version.

Update button beside Play.

Use Update when the launcher offers it.

Pick the game track and version on home

Update appears next to Play when a newer build is available on the selected track. The illustrated version labels are sample data.

Image source ↗
View the complete window Track, Version and Update in the v1.0.0 home view.Open full-size image ↗

Update a game build

  1. Quit the game and make a separate save backup.
  2. On home, choose Check for updates, select the installed build’s Track and Version, then read What's new.
  3. Choose Update beside Play, or select the newer version offered for that track. The launcher reuses local game files and compatible cached work.
  4. Wait for completion, press Play and check your settings and save. A normal update keeps the shared saves.

Update the launcher

Use the launcher update offered on home. It downloads and verifies its own application separately from the game, then replaces itself.

Installed Windows copies stay installed; portable copies update beside their portable marker. Keep the portable data folder in place.

Coming from an RC? Update the launcher first. On home, choose Stable and the offered stable version. If that track has no build yet, choose Build. Your existing RC build keeps its own track.

The launcher updates or rebuilds the selected instance. Its folder can be renamed to match the new version under the track. Use Open folder on the instance row to find it. Compatible shader caches are reused. Changed tools or graphics drivers can require preparation again.

A game update broke something: return to an older build
  1. Close the game and keep a separate copy of your current saves.
  2. On home, select the installed build’s Track, then choose an available older Version.
  3. Use the offered Go back action. The launcher rebuilds the existing instance on that track.
  4. Open the rebuilt game and load the expected slot. To try another track side by side, select it and build its version. Both builds share the active saves.

The available history depends on what the server still offers. Version-selection rules ↗

The launcher itself stopped working after an update

Close the launcher before restoring it. Its documented --rollback option puts back the previous launcher, when one is retained. For an installed Windows copy, run:

Restore the previous installed Windows launcher
& "$env:LOCALAPPDATA\Programs\LongshotLauncher\LongshotLauncher.exe" --rollback

For a portable copy, run the actual executable in that portable folder with the same option. If an interrupted Windows swap left the executable missing, the upstream recovery is to rename the adjacent LongshotLauncher.exe.old back to LongshotLauncher.exe. Leave game folders and saves in place.

Bring progress from Hookshot or an emulator

Close Longshot, Hookshot and any emulator before copying saves. Open Manage saves under the default version on home. You can import before the first game launch; an existing destination is backed up before it is replaced.

From Hookshot import card.

Choose From Hookshot to bring your Hookshot progress.

Restore from a backup option below sample save slots.

Return to Saves to restore a backup.

Choose the source on the Saves page

Launcher v1.0.0, shown with example slots. From Hookshot opens the dedicated importer. From an emulator also accepts a folder or supported ZIP.

Image source ↗
View the complete window Stable Longshot Launcher Saves page with sample slots, import, export and backup controls.Open full-size image ↗
FROM HOOKSHOT

Copy an existing Hookshot adventure

  1. Choose From Hookshot…, or use the one-time home-screen import offer.
  2. Check the detected folder, slots and saved time. Use Choose a folder… for a custom or portable location.
  3. Choose Import. If Longshot already has progress, review the replacement question and choose Back it up and replace it only for the intended destination.
  4. Keep the displayed backup location. Start Longshot and load your expected slot.

Hookshot keeps its original files. To cancel a replacement, choose Keep Longshot's save.

FROM AN EMULATOR OR FOLDER

Choose the game and profile you used

  1. Choose From an emulator…. Select a detected emulator and the correct profile.
  2. For another location, choose Another folder… → Continue, then select the same game's save folder or a folder holding it.
  3. Check FROM, TO, the slots to be replaced and the backup location. Choose whether to keep Longshot's game options.
  4. Press Import, then load the expected progress in Longshot.

The picker detects several emulators and NX2navi. For a Fritchii export, extract its archive and select the save folder; Longshot expects save files, not the ZIP itself.

Hookshot save importer with source path, slot count, Import, Choose a folder and Close.

Read the source row, or choose the folder yourself.

Check the Hookshot source before choosing Import

The source row identifies the folder and slots. A custom folder can be selected below it. This earlier upstream Linux example shows the source choice. The current importer has a separate Import graphics and controls action.

Image source ↗
View the complete window Complete upstream Hookshot import dialog over the Longshot home screen.Open full-size image ↗
Import confirmation showing FROM, TO, replacement of one slot and Keep Longshot game settings.

The destination is replaced with the source; slots are not merged.

Confirm the direction and replacement

Check FROM and TO before Import. Keep Longshot’s game settings preserves option.sav. This nightly-52 UI example shows an older backup path; use the stable launcher paths below and the location your operation displays.

Image source ↗
View the complete window Complete upstream import confirmation example with source, destination and backup preview.Open full-size image ↗
I also want Hookshot's graphics, controls and language

In the Hookshot importer, choose Import graphics and controls…. Choose Hookshot's game folder and an installed Longshot version, review the listed settings and destination, then confirm. If no Longshot build exists yet, import saves first and return for settings after building.

Compatible hookshot_options.ini settings and recognized language.txt content are handled separately from the save copy. Unsupported keys are skipped; launcher preferences, shader caches and unrelated files stay outside this import.

Hookshot settings import target version, files to import and backup-and-replacement message.

Choose the target build and read the replacement summary.

Settings have their own destination and confirmation

This upstream Windows sample shows the chosen game version and backup. Existing destination settings are backed up before the listed values replace them.

Image source ↗
View the complete window Upstream Windows Hookshot graphics-and-controls import example.Open full-size image ↗
NX2navi says a save operation is still pending

Start NX2navi once, let its pending save or menu import finish, then quit it before retrying. Longshot refuses a transfer while a completed save is waiting in NX2navi's profile/save-tx or profile/save-import. Do not delete those folders to force the import.

Take progress back to an emulator

Start the destination emulator and save once to create its folders, then close it. In Longshot's Saves page choose Export saves…, pick the emulator/profile or Another folder…, and review the source, destination and backup before Export. The destination is backed up first; this launcher does not export directly to Hookshot.

Find the active saves and the backup for your setup

Choose Open saves folder on the Saves page to find the active save. The Launcher v1.0.0 defaults are below. Each active save sits in a player-ID folder under save. Keep the save files private and use the exact destination and backup paths displayed by your transfer when storage has been customized.

Windows · started through the installed launcher
Saves%APPDATA%\Longshot\save\<player id>\Backups%LOCALAPPDATA%\Longshot\oot-save-backups\
Windows · portable launcher
Saves, beside the launcherLongshotLauncher-data\user\save\<player id>\Backups, beside the launcherLongshotLauncher-data\save-backups\
Linux / Steam Deck · default data home
Saves~/.local/share/longshot/save/<player id>/Backups~/.local/share/longshot/save-backup/
Windows · older launcher or game started directly
Old per-build saves<game folder>\user\save\<player id>\

Launcher v1.0.0 links an eligible NTFS build’s user\save to the shared save. An older unlinked build or a drive without junction support can still use its own folder. Check the active folder before backing up.

Open the installed Windows save root

Press Windows–R and paste:

Default installed Windows save root
%APPDATA%\Longshot\save

For a portable launcher, open its adjacent LongshotLauncher-data folder instead. The launcher's own installed data, %LOCALAPPDATA%\LongshotLauncher, is separate from the active game saves.

What about XDG_DATA_HOME and a portable Linux AppImage?

If XDG_DATA_HOME is set, replace ~/.local/share with that directory. Linux AppImage portable mode uses an adjacent <AppImage filename>.home folder, which also changes the home seen by programs it starts. Follow the displayed paths instead of copying into the normal home by assumption.

What happens to older Windows build saves?

The launcher backs up older per-build saves before gathering them. It keeps existing shared slots and brings in older slots without overwriting them. Progress that cannot fit stays in a backup. Read the home notice before touching an old build or its save.moved-<timestamp> folder.

Undo an import with its complete backup

EXAMPLE · SLOT REPLACEMENT

Importing is a copy, followed by replacement

  1. Before: Hookshot has two slots; Longshot has one different slot.
  2. After a confirmed import: Hookshot still has its two slots. Longshot receives that source save; its previous one-slot save is in the backup.
  3. To undo: restore the complete pre-import Longshot backup to the same destination player folder. That returns its original one-slot save.

Progress from the two adventures is not combined. This example describes the documented copy rule.

Quit the game and open Manage saves → Restore from a backup…. Match the reason, time and slots, then choose Restore… and read the confirmation. The launcher makes a backup of the progress it replaces. To recover other profiles from a whole-folder ZIP backup, open the backup folder and follow the manual steps below.

Backup rows with operation and slot details.

Match the backup reason before choosing Restore.

Select the backup that matches the operation

Launcher v1.0.0 with example backups. Each row shows what made it, when and which slots it contains.

Image source ↗
View the complete window Longshot Restore from a backup view with sample entries and Restore buttons.Open full-size image ↗

Restore a separate manual backup

  1. Close every program using the saves

    Quit Longshot, Hookshot and any emulator. Find the backup path from the completed operation, or the matching timestamp folder under your backup parent.

  2. Keep the current destination before restoring

    Copy the current complete destination player folder somewhere outside the active save tree. Confirm which player folder the earlier import replaced; restoring to a different player ID can leave the game showing no progress.

  3. Restore the whole backed-up save

    Open the selected backup until you see account.sav, option.sav and its slot_NN folders. Move the current destination contents aside, then put the complete backed-up set into that same player folder. Avoid merging selected slot files from different backups.

  4. Start through the same launcher and check the slot

    Load the expected name and progress before playing further. If it is wrong, close the game and recheck the source, timestamp and destination; preserve both your safety copy and the original backup.

Match the problem to the stage that failed

The input is unsupported or Next stays disabled

Compare the exact program, update and build against the supported input. Wait for the builder-tools download as well as validation. If using extracted files, select both the correct romfs and exefs folders; a different game's data or an incomplete dump needs the original files corrected.

Tools will not download or an update check fails

Keep the error message and use the launcher's Copy for a bug report action when offered. Check network access to the official host and retry after correcting the connection. A signature or checksum failure calls for a fresh official download, rather than bypassing verification.

The build runs out of space or fails during shaders

Check the actual game destination and build-files drive. Free space in the relevant location and preserve the error stage before retrying. For a GPU-driver failure, keep its exact message and driver version; the upstream GPU-specific notes distinguish rendering issues from input and disk problems.

My progress disappeared after changing versions
  1. Confirm you opened the same installed or portable launcher, rather than a different data root.
  2. Check whether you launched the game directly instead of through the launcher.
  3. Read any notice about older Windows saves being gathered.
  4. Confirm the destination player folder and use the complete backup recovery if the wrong save was imported.
The importer cannot find or accept a save

Use the custom-folder choice for a portable or moved installation. The folder must contain the supported game's save files: account.sav, option.sav and complete slot_NN folders, including progress.sav. Close running programs, extract archives first and read the validation message before copying again.

A moved portable launcher says “not built: its game is missing”
  1. Close the game and keep a separate copy of your saves and portable data.
  2. Use Launcher v1.0.0 or later and keep LongshotLauncher.exe, its portable marker and LongshotLauncher-data together.
  3. Reopen it from the moved folder. The launcher can rebase paths inside that launcher folder when the old location is gone and the corresponding new files exist.

An external game folder is a separate location. If the row is still missing, preserve the folders and check where the game executable actually is; deleting a row is not a recovery step. Portable relocation rules ↗

A working update is in another folder, but Play is missing

Update the launcher to v1.0.0 or later, then reopen it. It can find a newer, working update left unlisted in the builds folder, return it to the appropriate row and keep it out of the old-version deletion offer. This fixes a specific older-update case; keep your working folder and save backup until the correct version appears and plays. The missing-update fix ↗

The Windows launcher reports that fonts could not be loaded

Use the complete official stable package first. The launcher includes a fallback font and more specific DirectWrite diagnostics. Keep the full message if it still fails, including any dwrite.dll from System32, Restrictions or Other modules lines. Do not replace Windows DLLs with downloads from another site; share the diagnostic through the project's support route. What the font diagnostic checks ↗

The compiler cannot list a folder, such as Cookies

Read the folder named by the error. A Windows compatibility junction such as C:\Users\<name>\Cookies can refuse directory listing before the compiler starts. For a portable launcher, close it and move its complete launcher/data set to a normal folder you can list. Keep the existing game folder and save backup.

For an installed copy, use its normal per-user location. If a custom build-files location sits under the blocked parent, choose a normal writable folder in launcher Settings → Build files → Change, then retry the check. The launcher names this problem instead of treating it as a generic antivirus failure. Folder-permission fix ↗

Build and troubleshoot on Steam Deck

  1. In Desktop mode, download the Linux AppImage and enable Allow executing file as program in its Properties. Build from your own supported files.
  2. Keep the Deck plugged in and awake while building. Allow about 60 GB free for the build; handheld compilation can take much longer than a desktop's. Prefer the internal drive when available: an SD card adds load-in and cache stutter.
  3. For the initial game setup, keep Auto (this PC). In v3.0.0, Auto starts with Minimum quality, the game’s own upscaler, a 60 FPS cap and frame pacing. The upstream Deck test recommends keeping FSR 4 and Threaded rendering off. Let the first shader-preparation progress finish before judging a later launch.

The Steam Deck guide for v3.0.0 also covers storage, first-launch preparation and optional tuning.

gfx_0.0.0 timeout in the starting area or first dungeon

Use this branch when the kernel log contains that exact GPU timeout. In Desktop mode, inspect it with:

Read the Deck kernel log
journalctl -k
  1. Close Longshot and back up any existing longshot_env.txt in the game folder.
  2. Add this one NAME=value line to that file, keeping its other settings. It is a configuration line, not a Terminal command.
Add only for the matching Deck timeout
RX_VK_MESH_NOCULL=2c56dc1006942f74

Restart and check the same location. The upstream workaround skips the affected culling pass while keeping models drawn. To undo it, close the game and remove only that line, or restore the earlier file. If the log names a different error, keep it and use the matching upstream symptom.

Choose the project that matches your platform and files

The stable Launcher provides Windows x64 and Linux x86-64 packages. The macOS port remains a paused draft. Choose the Mac route that matches your edition of Ocarina of Time. Each route has its own save format.

You want to…ChooseWhat changes
Use Longshot on Windows or LinuxLongshotLauncherYour supported Switch 2 game, local build, shared saves and Hookshot import.
Use another PC recompilation workflowNX2naviIts own installer/build kit, version requirements, launcher and Mods tools.
Use a Windows emulator libraryFritchiiGame/system files and an emulator setup; its own data migration and Saves manager.
Set up a Mac emulator with Eden dataLichiiA separate emulator app, your game/system files and its Keep Old Data import workflow. Follow its own installation and profile paths.
Play N64 Ocarina on a MacShip of HarkinianA supported N64 ROM and the SoH Mac app.
Play Ocarina of Time 3D on a MacOcarina ReTunedA supported decrypted 3DS ROM and first-run preparation in the Mac app.

For Switch 2 emulation on Mac, follow the separate Eglantine setup and compatibility guide. Browse all project routes →

Official sources and interface versions

The English welcome, build, update and save views are rendered from Launcher v1.0.0 with sample files, slots and version labels. The earlier Hookshot and import confirmation examples keep their original captions. Use the paths and version shown by your own launcher.

Original source links accompany the figures. Longshot and its launcher are distributed under GPL-3.0-or-later.