Install & troubleshooting / v2.3.2 checkedLast checked: 16 Nov 2026 · 15:31 UTC

Install Hookshot. Keep your saves. Know the limits.

Build locally from your own supported game files. Start with the current project documentation, then check the exact stage, version and hardware when something fails.

01

Check before you build

Current README requirements; eligibility is not a stability guarantee
ItemDocumented requirement
WindowsWindows 10/11, x64. Use the current Windows Builder.
Linuxx64; AppImage requires glibc 2.35+ and AVX2. Keep the AppImage for updates.
GPUVulkan 1.3 with mesh shaders. README lists RTX 20+, Radeon RX 6000+ and Intel Arc. 8 GB VRAM recommended.
Memory / storage16 GB RAM minimum; roughly 60 GB free space for building.
Game inputYour own supported .nup. Current README also accepts .nx or extracted romfs/exefs. The Builder validates the game build.

No game files are available here. We do not host or accept .nup dumps, ROMs, keys or ready-made game executables. We do not provide instructions for acquiring unauthorized copies.

02

Windows x64: current Builder steps

01

Open the verified release page

Follow NotRexed’s Forgejo release page and read the notes for your version. Obtain the Builder from the project itself; this guide links to the release page rather than redistributing it.

02

Let setup prepare its own tools

Run the current Builder and allow its normal dependency setup to complete. It supplies its compiler and libraries. If downloads fail, use the official manual-dependency instructions linked below.

03

Choose your input and output folder

Select your own supported .nup, output directory and language. Keep enough free space and let validation finish. A file from the wrong game build may be rejected.

04

Build, prepare shaders, then play

Wait for the local build and initial shader preparation. If Play immediately exits, collect the log and your GPU/driver details before trying unrelated workarounds.

About Visual Studio Desktop C++ and MFC: these appear in older setup guides. The current v2.3.2 README says no Visual Studio, Python or Git needs to be installed first. Developing the Builder from source is a separate workflow.

03

Common errors, with context

Builder is stuck looking for game files

v2.3.1 release notes fix an indefinite wait involving unresponsive USB, cloud or network drives. If you use an older Builder, update it first. For a current build, report the exact stalled stage and log; waiting is not a universal fix.

Dependency downloads fail

v2.3.2 documents a manual fallback: obtain the named dependency parts through the project’s manual page, place them in Downloads and rerun setup for validation. Avoid third-party bundles. For optional DLSS connection errors, the common-issues guide suggests retrying later or omitting optional DLSS.

Play exits immediately

Record the Hookshot version, OS, GPU, driver and hookshot_log.txt. Follow the migrated crash tracker #2507. Older issue #1288 was closed into that tracker; its closed status does not establish a fix for your system.

“Incomplete compressed frame” or input validation errors

The common-issues document associates an incomplete compressed frame with an incomplete game copy. Recheck or recopy your own local input and confirm the supported game build. Do not obtain a replacement game package from an unknown download site.

Low FPS, stutter or instability

Let shader preparation finish. Compare the same scene with the same resolution, upscaler and frame cap; turn off frame generation when comparing underlying game FPS. Record memory usage, GPU/driver and a slow-run log. Check the hardware tracker instead of assuming a preset fixes every device.

The common-issues page was compiled from November 10 reports, mostly v2.0.14. Some links still point to the old GitHub. Use current release notes and the migrated Forgejo trackers alongside that historical advice.

04

Linux, Steam Deck & GPU notes

Cards without mesh shaders have incomplete fallback paths. Some workarounds can remove geometry or important models; do not apply them blindly. v2.3.2 reports Linux memory and GPU improvements, but this site has not performed independent hardware benchmarks.

Linux and Steam Deck

The Linux AppImage requires glibc 2.35+ and AVX2. Make it executable, then follow the local-input build flow. Tracker #1000 remains open for GPU resets, crashes, low FPS and build problems. This is not a promise of smooth Steam Deck play.

AMD on Windows

Tracker #996 remains open with device-lost, driver and freeze reports. Minimum GPU support does not eliminate these issues. Compare your exact GPU and driver with current reports before changing a working configuration.

05

Update without losing your place

01

Close the game and back up

Windows: <game folder>\user\save\<user id>\ Linux: ~/.local/share/hookshot/save/<user id>/ XDG_DATA_HOME may change the Linux base. With --user <folder>, look under <folder>/save/<user id>/. Copy your saves to a separate location.

02

Use Update in your current launcher

The current README documents reusing the same game directory while retaining saves, settings and mods. The original local input is retained, so normal updates do not need the .nup again. Read release notes first and keep the old backup until the new build loads it.

03

Know where automatic backups live

v2.3.2 adds external backups and keeps the newest 20. Windows: %LOCALAPPDATA%\Hookshot\save-backups Linux: ~/.local/share/hookshot/save-backups Keep a manual backup too, especially before changing projects.