Hookshot Guide
Independent community guide

Hookshot Compatibility: What Actually Runs

This page covers Hookshot compatibility at two levels: documented platform support and community-reported GPU results — these are two different things. A supported operating system can still have a GPU or driver that fails. A report from one card does not establish that every card in its family works. The table names specific models and labels the source of each report. “Known issues” describes a report, not a universal failure. Check both the platform requirements and the report for your model. These labels summarize published evidence at the time of writing. They are not tests performed by this site, and a later driver or release may change the result.

On this page

Hookshot Platform Support

Windows 64-bit

The README documents Windows 10 or 11 on a 64-bit PC, with a graphics card and current driver that support Vulkan 1.3 and mesh shaders. The Builder includes its compiler and tools. On Windows, a CPU without AVX2 can receive a build for its available features, with a speed cost. None of this establishes support for a particular GPU.

If the game shows a black screen, record the GPU, driver, and Hookshot release. Compare them with the reports below and the guide's troubleshooting section.

Linux 64-bit

The README documents 64-bit Linux with glibc 2.35 or newer. The official AppImage needs AVX2 and execute permission. The GPU driver must expose Vulkan 1.3 and mesh shaders; a distribution name alone cannot confirm that.

For faster GPU memory imports, the game user needs read and write access to /dev/udmabuf. Without it, Hookshot uses host-pointer imports, which can be slower on AMD/RADV. Proprietary NVIDIA driver users can ignore that specific warning. Follow the README's device-specific permission instructions; do not run as root or make the device world-writable.

Hookshot Compatibility: GPU and Platform Status

Hookshot compatibility reports are model-specific, not certification by this site. The status labels are Confirmed working, Reported working, Known issues, and Not supported. No model here has a universal guarantee that justifies Confirmed working. A reported problem can depend on driver, release, or where the player was in the game.

Scroll to see every column.

Hookshot GPU model reports
GPU familyStatusSource
NVIDIA GeForce RTX 4060 TiReported workingOfficial Releases
AMD Radeon RX 6600Known issuesCommunity report; link unavailable
AMD Radeon RX 6800 XTKnown issuesCommunity report; link unavailable
AMD Radeon RX 7800 XTKnown issuesCommunity report; link unavailable
AMD Radeon RX 7900 XTXKnown issuesCommunity report; link unavailable
AMD Radeon RX 9070 XTKnown issuesCommunity report; link unavailable
Intel Arc A750Known issuesCommunity report; link unavailable
Intel Arc B580Known issuesCommunity report; link unavailable
Intel Arc Pro B50Known issuesCommunity report; link unavailable
Intel Arc 140VKnown issuesCommunity report; link unavailable
Other GPUs without mesh shadersNot supportedOfficial README — Cards without mesh shaders are not supported

Common crashes for these cards →

Hookshot compatibility reports are model-specific; the NVIDIA row points to a project test, while the AMD and Intel rows summarize community issues. Some reports concern older releases. Compare their driver and version with yours before assuming the same outcome.

A report may describe only a title screen, a short gameplay session, or one repeatable failure. It cannot establish how the entire game behaves on that model. The original community issue links are currently unavailable, so treat these entries as historical reports rather than a current verdict.

If Your Hookshot GPU Isn't Listed

If your GPU is not in the table above, Hookshot compatibility depends on what your driver exposes, not on the model name. Start with the README's hardware requirements. Confirm that your GPU and driver expose Vulkan 1.3 and mesh shaders. Cards without mesh shaders are unsupported, though an incomplete compute fallback may show part of the picture. An opening window does not establish full support.

Compare your video memory with the README's recommendation of 8 GB or more. It is a recommendation, not a guarantee or an automatic cutoff. The README mentions lower quality presets for cards with less. Check the operating system and CPU too.

Before changing settings, identify the failure: rejected game input, stalled shader preparation, black screen after the title, or frozen picture with audio. Keep the GPU, driver, release, and hookshot_log.txt. Use the guide's troubleshooting section to match the symptom. Also note whether the problem happens every time or only after a particular action. That distinction helps separate a repeatable compatibility problem from an isolated interruption. Avoid changing several settings at once, because you may lose the ability to tell which change affected the result.

Open hookshot_log.txt in a plain-text editor after reproducing the problem, and keep an untouched copy before trying another launch. Read the final part of the file, then move upward to find the last normal activity and the first warning or error near the symptom. Look for your selected GPU and driver, a permission message, a shader-preparation failure, or a device-loss message, depending on what happened. A final error line may describe the consequence rather than the original cause, so include a little context before it. If the log stops suddenly, say that instead of guessing why. When the project's reporting channel is available, write a short report that names your operating system, exact GPU, graphics driver, Hookshot release, and the point in the game or build where the failure occurred. Explain how to reproduce it, what you expected, what actually happened, and whether it repeats. Include the relevant log excerpt or the complete log if requested, after removing personal paths or account names. Never attach your game copy, ROM, keys, saves, or generated game files. A clear report helps others compare the same symptom without treating one machine's result as a universal verdict.

If no matching model report exists, the outcome is Not documented here. Compare the official requirements and current issues, then report your result with the release, driver, symptom, and log. A successful launch alone is not confirmation of stable play. If the game reaches one scene but fails elsewhere, describe both outcomes rather than reducing them to a simple works-or-does-not-work label. If the official discussion is temporarily unavailable, keep your notes locally until it returns rather than posting an unsupported conclusion elsewhere.

When reading an issue, check whether the reporter used Windows or Linux and whether the symptom happened before or after entering gameplay. Those details help distinguish a build or permission problem from a rendering problem. They also make your own report more useful to the project. Pay attention to the report's release and driver context; a later software change can make an older observation less useful for your current setup.

FAQ

Does Hookshot work on AMD?

The README lists supported AMD hardware families, but community reports include black screens, driver timeouts, and device loss on specific cards. Check your exact GPU, driver, and Hookshot release before treating a report as relevant to your setup.

Do I need an RTX card?

No. The README also lists AMD Radeon RX and Intel Arc hardware that meets its Vulkan and mesh-shader requirements. NVIDIA is described as the most tested family, which does not guarantee that every RTX system works.

Can I run it on integrated graphics?

Some Intel Arc and AMD integrated GPUs appear in community reports, including failures. A model name alone is not enough: check Vulkan support, mesh shaders, available video memory, and reports for your exact device. Integrated graphics are not guaranteed to run Hookshot.