github JackandBeans/Snap64Recomp v1.1.8
Snap64 Recomp 1.1.8

49 minutes ago

The title screen

The Snap Station's printer, three stars

Snap64 Recomp is a native port of Pokémon Snap (Nintendo 64, US release) made by static recompilation: the game's own code runs on your PC, the port only hosts it, and everything about how it looks is off unless you turn it on. 1.1.8 fixes the Android app closing on an AYN Thor, stops a graphics setting from ending every start the same way, as it did on a phone with an Exynos 2400, has the Android app write down why it closed, asks before a third start that would end like the last two, and lets Pikachu and the Zero-One leave the title screen whole under Cutscene Fix.

Note

Snap64 Recomp is released only on this repository's
Releases page.

Copies posted anywhere else are not the project's. On Windows the port is
a ZIP holding a folder with Snap64Recomp.exe, and nothing has to be
installed. It opens no network connection and asks for no account or
password. Each file has a .sha256 beside it, and SECURITY.md says how to check a download.

Downloads

File For
Snap64Recomp-1.1.8-win64.zip Windows 10 (version 1809 or newer) or 11, 64-bit, with a GPU driver that provides Direct3D 12 and Shader Model 6.3: any driver since late 2018. Nothing else to install.
Snap64Recomp-1.1.8-linux-x86_64.tar.gz Linux, experimental: needs the system's SDL2, GTK 3 and a Vulkan 1.2 driver. This file ran a scripted ride on a Steam Deck in Desktop Mode.
Snap64Recomp-1.1.8-linux-x86_64.flatpak The same Linux build with its own SDL2, GTK 3 and Vulkan loader; installs with one command on a Steam Deck or any desktop with Flatpak. This file was built and started on GitHub's machine and ran a scripted ride on a Steam Deck in Desktop Mode.
Snap64Recomp-1.1.8-linux-arm64.tar.gz Linux on ARM64 (a Raspberry Pi 5, an ARM laptop, a Linux virtual machine on a Mac). Built on GitHub's ARM machine, not yet played on real hardware.
Snap64Recomp-1.1.8-macos-universal.zip macOS 14 or newer, Apple Silicon and Intel in one app. Built and run on GitHub's virtual Mac, not yet on a physical one.
Snap64Recomp-1.1.8-android.apk Android 10 or newer on a 64-bit (arm64) phone or handheld, with a Vulkan 1.2 driver. A beta: 1.1.6 has run on a player's AYN Odin 3 Pro and on a Galaxy S25 Ultra, a test build with this release's fixes on a player's AYN Thor, and this release on Android's emulator; no real pad has been tried yet. ANDROID.md has the steps.

You need your own cartridge dump. No game data is included. Start the program and choose your pokemonsnap.z64 when it asks (US, SHA-1 edc7c49cc568c045fe48be0d18011c30f393cbaf), or put the file next to the executable yourself. START HERE.txt in each archive says the rest, in one page. On Android the file goes in Internal storage > Snap64, or the app asks for it with the system's file picker.

What's new

Android

  • The app no longer closes on an AYN Thor (#36). Shiniphil reported it, and the log of each test build named the next step. Two faults lay one behind the other. The Thor's Adreno 740 driver refused the renderer's texture table: Qualcomm's driver counts a table's declared size against its pool, whatever size is asked for, and the pool was made for the size asked. sergiomanzur had found that cause for cvlod_recomp on a Retroid Pocket 6. On a Qualcomm driver the pool now holds the declared size from the start, and on any other driver a refused table is asked for once more from such a pool. Then the driver crashed as the first frame's first render pass closed, because the frame's query reset sat inside that pass, where Vulkan does not allow it. The pass is now closed before the reset. On the reporter's Thor, on a test build with both fixes, the game ran and the first course was played.
  • The app writes down why it closed (#36). A phone shows a player neither a crash nor its reason. A crash now writes itself into snap64.log as the app closes: the signal, the thread, the Vulkan call that thread began last, and the addresses in the port's code. On Android 11 or newer, the next start's log opens with Android's own record of how the app last ended. On the reporter's Thor the two records named the same thread, the same call and the same addresses.

Graphics settings

  • A setting the card cannot carry can no longer end every start the same way (#39, reported by doctoroftardis on a phone with an Exynos 2400). With the graphics settings at their highest, the Android app ended at every start with a message that it had set Super Sampling to 1x, where it already was, and a reinstall did not help, because the settings outlive the app. The catch for a picture buffer the card cannot make, added in 1.1.5, lowered Super Sampling alone. It now lowers one setting at every failure, the first that has anything left to give: Super Sampling, then Anti-Aliasing, then Color Depth, then Render Scale. Its message names the setting it changed. An Anti-Aliasing level the card does not offer is no longer asked for, a level that failed is remembered for that card, and the log names the levels the card offers. This is the same on every system. On Android's emulator a released 1.1.7 put in the report's state gave the report's message at every start, and the APK on this page, installed over it, lowered Anti-Aliasing to 4x by itself at the next start and reached the title, the save untouched. It has not run on an Exynos phone.
  • A question after two starts that end before their first frames. A setting that takes the driver down at the start shows no message and changes nothing, so every start would end the same way. Nobody reported it; it was found on reading every way a saved setting can end a start, after #39. The port now counts the starts that end before their first frames and not by themselves. After two in a row, with Super Sampling, Anti-Aliasing, Color Depth or Buffering raised, the next start asks whether to put those four back to their defaults, as the mods question does for mods. It only asks.

The title screen

  • Cutscene Fix lets Pikachu and the Zero-One leave the title whole. On the title screen the Zero-One vanished at the left edge with its back still in view, and Pikachu did the same. That is the cartridge's own rule: each is hidden once it reaches the same spot, whatever its width, so part of each went in one frame. Overscan Crop hides most of it. Cutscene Fix, Off as shipped, now also runs each one on until it is fully past the edge. Off, the title is the cartridge's. Found in play, with Overscan Crop off.

Fixed

  • Three things Vulkan does not allow are no longer passed to the driver: a clear that reaches past its target, a scissor that starts at a negative offset, and a write into a table the driver refused. Each was found on an Adreno by another RT64 port on Android (JetForceGemini-Recompiled, automobililamborghini-recomp). A valid frame is drawn as before.
  • The advice after a start that cannot make its graphics device told Windows to try Vulkan also when the file already asked for Vulkan, and said the same on Linux and Android, where there is no other backend. On Windows it now names the backend the file does not, and elsewhere the driver alone. Read from the code; not run.
  • The Flatpak's log names its commit. 1.1.7's said "built from commit unknown", where every other build named its commit. Found on a Steam Deck. On GitHub's machine the bundle on this page, installed and started, named the commit it was built from; the job now fails without that line.

The release checks

  • The checks make a render target fail on purpose at every step of the catch. Eight new checks: a card played as offering less Anti-Aliasing than asked, a failed target at each setting with the start after it, the floor where nothing is left to lower, and two starts ended early with the question answered. On Android's emulator, three new tools check the Thor's pool fix, the crash record and the catch.

Nothing else changed since 1.1.7; its page says what 1.1.7 brought.

Every change, with its cause, is in CHANGELOG.md.

Note

Upgrading from 1.1.7 or any earlier release: unpack the new archive over the old folder or beside it. Your save is in saves/ and your settings in snapsettings.json, both untouched by the upgrade and both read by 1.1.8 as they are. If you keep the old folder, copy those two across, and pokemonsnap.z64 with them, or let the new one ask you for it. On Android, install the new APK over the app you have; your saves stay.

Warning

The Windows executable is not signed, and the Mac app is signed by nobody. SmartScreen may say "Windows protected your PC" on the first start, macOS refuses a plain double-click, and an antivirus may flag a program it has never seen; the builds on this page are what the source produces, GitHub's provenance says so, and the .sha256 beside each archive lets you check what you downloaded. The APK is the exception to the provenance: it is signed with the project's key on the release machine, so it carries no GitHub build record, and its .sha256 is the check. The Android app is installed from the file, not from a store: Android asks once to let your browser or file manager install apps.

First start

  • On Windows, past SmartScreen: choose More info, then Run anyway, once.
  • On a Mac: right-click the app and choose Open, or on macOS 15 double-click, dismiss the message, and click Open Anyway in System Settings > Privacy & Security, once.
  • On Android: open the APK, turn on "Install unknown apps" for the app you downloaded it with when Android asks, and install. The first start asks for "All files access" for the Snap64 folder; Not now asks again at the next start, and Don't ask again keeps everything in the app's own folder.
  • The box asks for your ROM; choose the file and the game starts. The first start also compiles the shipped shader list during the boot logos and takes longer.
  • The Snap Station's Print restarts the program twice, on purpose. It is not on Android.
  • On a Deck, add the executable as a non-Steam game and run it in either mode, or install the Flatpak; the Deck page under docs/ has the shortcut and gyro settings.

Known limitations

  • The Android app is a beta. 1.1.6 has run on a player's handheld and on one phone, and a test build with this release's two Thor fixes on a player's AYN Thor; this release has run on Android's emulator. No real pad has been tried, and the touch controls' rows have run on the emulator only.
  • The catch for a graphics setting a device cannot carry (#39) has run on Windows and on Android's emulator, not on a phone with an Exynos 2400, where the fault was reported. A snap64.log from one is welcome.
  • The Mac build has not run on a physical Mac, and the ARM64 build has not run on real hardware. Their sounds, pads and speed are unheard and unmeasured.
  • A few 2D pictures still move at the game's rate when the frame rate is raised: one that slides past the side of a menu in a wide window, and one that jumps a long way in a single frame. Outside Oak's check, a slide that slows to a stop can still end a pixel at a time.
  • A mod installed during play loads at the next start; the page says so.
  • On an N64-shaped pad with neither a ZR nor a spare right trigger, such as the Mayflash N64 Adapter, fast forward has only its key until the file names another button.
  • A Pokémon pops out of the picture before it has fully left it: the cartridge draws a Pokémon only while its collision point projects within 1.5 times the half-screen of the center. The port keeps the rule as the cartridge has it.
  • Gyro has been confirmed on a Steam Deck, in both modes, and on no other pad yet. In Gaming Mode it felt too slow on two rides of four; on the measured ones its scale is right, and the cause is still open.
  • Some changes were made without the hardware they are for, from the drivers and the code: Steam's virtual pad keeping Steam's layout, the clear red N64 USB pad, and the Steam art on Windows and on a Linux desktop. A report from any of them is welcome.

How this release was checked

  • The release suite (tools/release_check.py) on the Windows executable GitHub built: 47 of 47 checks in 1490 s, and the Snap Station's 5 of 5 in 488 s.
  • The same suite on the build made here: 47 of 47 in 1489 s, and the Snap Station's 5 of 5 in 488 s. It now makes a render target fail at every step of the catch, and ends two starts early for the question. VERIFICATION.md says what each check does.
  • The title fix in the game: a scripted run of the idle title with Overscan Crop off, captured reading by reading. With Cutscene Fix off, Pikachu and the Zero-One were drawn where 1.1.7 draws them at every captured reading and vanished at the same spot. With it on, each went on until it was fully past the edge, and the rest of the title was drawn as with the fix off.
  • The question after two failed starts, on Windows: started on a folder with the mark of two such starts, its box was photographed from the screen, and its text and both buttons show whole. The suite's two checks answer it through a switch.
  • On a Steam Deck OLED in Desktop Mode, the tarball and the Flatpak on this page, each: a scripted Beach ride with MSAA 8x and Widescreen on scored its 37 photos exactly as the Windows build does, and the Mods page drew whole with Island Skies on. Each log shows the Thor's second fix at work on the Deck's own driver: the frame's query reset found a render pass open, and the pass was ended first.
  • The APK on this page on Android's emulator (x86_64, Android 15): every stage of tools/android_check.py, 114 of 114 checks in 1287 s; the Android-only paths, 11 of 11; the check of the Thor's pool fix, 23 of 23; the crash record's check, 42 of 42; and the catch's check, 16 of 16. It is GitHub's own build, signed here with the project's key: its contents are those of the unsigned build, whose provenance verifies.
  • On a player's AYN Thor (Adreno 740): a signed test build with both of this release's Thor fixes ran, and the first course was played (#36). The APK on this page has not run on a Thor.
  • The Mac workflow's checks on GitHub's virtual Mac: 15 of 15 natively and 10 of 10 through Rosetta 2, with no crash reports. On the first run the Rosetta mod check ended with a segmentation fault after the mod's hooks had run, as it did once in September; the cause is not known, and it passed when that job was run again. The package checks passed on all six archives, and the build provenance of the five archives and of the unsigned APK the signed one was made from verifies.

Don't miss a new Snap64Recomp release

NewReleases is sending notifications on new releases.