Skip to content

Releases

Longshot PS5 Builder v0.1.4 (prerelease)

Choose a tag to compare

@heydemoura heydemoura released this 20 Nov 02:25
dc9969c

Prerelease: the base PS5 memory work for the Castle Town crash, for testing. Please report how the first start and Castle Town go on your console (issues #4, #24).

Highlights

  • The first start prepares the game's graphics. The builder now puts the game's shader list (made from your own game) and a pipeline list in the title folder. The first start builds every pipeline before play, with a progress screen that explains what is going on, then restarts the game by itself. Play then no longer compiles them, which on a base PS5 used up the memory that ran out entering a new area like Castle Town. It takes about 20 minutes once, and about 2.7 GB of the console's storage. You can close it at any time: the next start goes on from where it stopped.
  • The game closes safely when the console runs out of memory, with a notice, instead of letting the console power off.
  • The renderer's texture budget counts all free memory, so textures in use are no longer thrown out while memory is free.
  • Frame generation steps down when memory is short, and turning it off gives its memory back.
  • The intro narration is back (#3).
  • Frame generation: Auto works on the console, 2x is the default, the menu says which generator is used, and Lossless Scaling is available with your own Lossless.dll.
  • The game starts in your console's language (English where the game doesn't have it); the menu has a Follow the console choice.
  • Threaded rendering On is now the recorder thread alone (an optional speed-up); Auto stays off.
  • New title art: a DualSense-tipped icon and a horse background.
  • The title's cache and log folders can be deleted over FTP again.

Known

  • Not yet tested: Castle Town itself on a base PS5, and a very first start with nothing cached on the newest code.
  • In places you have already played, a prepared install keeps ~200 MB more of the driver's memory than before.
  • Your translated shaders from earlier versions are not reused: the cache is compressed now, and the first start makes it again. The old cache/longshot_programs.bin can be deleted.

Downloads

Your computer File
Linux LongshotPS5Builder-v0.1.4-x86_64.AppImage
Windows LongshotPS5Builder-v0.1.4-windows-x64.zip (a portable folder: unpack it, start LongshotPS5Builder.exe; no installer)

They are attached by the release workflow a while after the release is published. Build your title again with this version and pick your game's .nup file: the new shader lists are made from it (a folder with just the program in it gets no lists, and the game then compiles as it plays, as before). How to use it: Install and play.

No PC builds of Longshot are here, and no game files. Never share the folder the builder makes: it comes from your game.

Longshot PS5 Builder v0.1.3

Choose a tag to compare

@heydemoura heydemoura released this 16 Nov 21:47

Fixes the Linux builder. v0.1.1 and v0.1.2 on Linux stopped at "Reading the game's program" with ValueError: ZBIC: decompression failed (-2 of 63201744 bytes). If you saw that, download this version and build again. The Windows builder was not affected; it is rebuilt here with the same check.

What was wrong

The game's main program is ZBIC-compressed in a dump, and the builder carries a small library that unpacks it. The Linux one was compiled by the release machine's GCC 11, and that build could write ZBIC data but not read it. It is now compiled by the same pinned LLVM as the Windows one, and the library has a self-test that the release's own checks run on both systems before anything is published.

Also in this version (from v0.1.2)

  • Longshot v3.0.0-rc.5 from upstream, with higher frame rates: Kokiri Forest on a PS5 Pro at 1920x1080 at 34 game frames a second, 68 shown with frame generation.
  • AMD FSR 3.1 is the default upscaler.

Downloads

Your computer File
Linux LongshotPS5Builder-v0.1.3-x86_64.AppImage
Windows LongshotPS5Builder-v0.1.3-windows-x64.zip (a portable folder: unpack it, start LongshotPS5Builder.exe; no installer)

They are attached by the release workflow a while after the release is published. How to use it: Install and play.

No PC builds of Longshot are here, and no game files. Never share the folder the builder makes: it comes from your game.

Longshot PS5 Builder v0.1.2

Choose a tag to compare

@heydemoura heydemoura released this 16 Nov 20:38

Warning

On Linux, use v0.1.3 instead. This version's AppImage cannot unpack the game's program ("ZBIC: decompression failed"). The Windows zip works.

What is new

  • Updated from upstream Longshot. The port now carries Longshot v3.0.0-rc.5: its runtime and renderer, with the PS5 port on top. Among what came in, the render thread is no longer held to one core, upstream's fix for stalls in busy places.
  • Higher frame rates. Kokiri Forest on a PS5 Pro at 1920x1080 ran at 34 game frames a second, 68 shown with frame generation, where the earlier builds ran at 31 to 32 and 63. (Measured with the game's own upscaler, before the next change.)
  • AMD FSR 3.1 is now the default upscaler. A new install uses it, and so does one whose Quality preset is on Auto, from its next start. Settings you chose yourself stay as they are, and the game's own upscaler is still on the Upscaler row of the in-game menu (touch pad click and Options together).

Downloads

Your computer File
Linux LongshotPS5Builder-v0.1.2-x86_64.AppImage
Windows LongshotPS5Builder-v0.1.2-windows-x64.zip (a portable folder: unpack it, start LongshotPS5Builder.exe; no installer)

They are attached by the release workflow a while after the release is published. To update: download this builder, build again and copy the new PPSA99025 folder over the one on the console; your saves and settings stay. How to use it: Install and play.

What was tested, and what was not

  • This version's title was run on a PS5 Pro from the autosave into Kokiri Forest (the figures above). FSR 3.1 was played with on a console by hand; it was not measured in a logged run.
  • It runs on a base PS5 as well, with about 20 fewer frames a second shown than on a Pro.
  • Nothing beyond Kokiri Forest has been played in a test run.

No PC builds of Longshot are here, and no game files. Never share the folder the builder makes: it comes from your game.

Longshot PS5 Builder v0.1.1

Choose a tag to compare

@heydemoura heydemoura released this 16 Nov 17:33

Warning

On Linux, use v0.1.3 instead. This version's AppImage cannot unpack the game's program ("ZBIC: decompression failed"). The Windows zip works.

Fixes v0.1.0, which could not read a game file. If the build stopped at "Reading the game's program" with a traceback from nup.py, this is the fix. Download this version and build again; nothing else changes.

What was wrong

A real dump keeps the game's main program ZBIC-compressed (a zstd variant). The library that unpacks it was built on first use by a compiler, which a player's computer does not have, so the build stopped at its first step, on Windows and on Linux. v0.1.0 was tested with program files unpacked earlier, never with a .nup itself. The library now comes ready inside both packages, and the packages' self-check asks for it.

Downloads

Your computer File
Linux LongshotPS5Builder-v0.1.1-x86_64.AppImage
Windows LongshotPS5Builder-v0.1.1-windows-x64.zip (a portable folder: unpack it, start LongshotPS5Builder.exe; no installer)

They are attached by the release workflow a while after the release is published. How to use it: Install and play.

What was tested, and what was not

  • The game's program is now read from a real .nup by both packages (the Windows one under Wine), and comes out identical to the files every earlier build was made from.
  • Still not done: a whole build on a real Windows PC, and a console run of a title built with a released package. On a PS5 Pro the port itself was played from a new game to Kokiri Forest; nothing beyond, and no base PS5.

No PC builds of Longshot are here, and no game files. Never share the folder the builder makes: it comes from your game.

Longshot PS5 Builder v0.1.0

Choose a tag to compare

@heydemoura heydemoura released this 16 Nov 16:15

Warning

Use v0.1.1 instead. v0.1.0 cannot read a game file: the build stops at "Reading the game's program".

The first release of Longshot for the PlayStation 5: the Longshot PS5 Builder, a desktop program that makes the PS5 title folder from your own copy of the game, on your own computer.

No PC builds of Longshot are here, and no game files. For Longshot on a PC, see Longshot itself.

Downloads

Your computer File
Linux LongshotPS5Builder-v0.1.0-x86_64.AppImage
Windows LongshotPS5Builder-v0.1.0-windows-x64.zip (a portable folder: unpack it, start LongshotPS5Builder.exe; no installer)

Each has a .sha256 beside it. They are attached by the release workflow a while after the release is published.

How to use it, what you need and where the files go on the console: Install and play.

What this version is

  • Longshot at 1764fed2 (2026-11-16) with mihawk-99's PS5_Hookshot port brought onto it, and PS5_Vulkan as the Vulkan driver.
  • The title is PPSA99025. It starts at 1920x1080 with the full picture; frame generation is on.
  • The builder asks which console the folder is for: PS5 / PS5 Slim or PS5 Pro.

What was tested, and what was not

  • On a PS5 Pro: a new game through the opening to Link's house, a start from that autosave, and Kokiri Forest. 31 to 34 game frames a second in the forest, about twice that shown with frame generation.
  • Nothing beyond Kokiri Forest has been played.
  • No base PS5 has run it. The base profile was measured on a Pro started in the base console's mode (12 GB of memory).
  • The in-game menu has not been opened on a console. Sound and a real controller were not checked by a person: the test runs used scripted input.
  • The builder's packages are started and checked on Linux and on Windows by the release workflow; a whole build was run with the Linux one. A whole build has not been run on a real Windows PC, and choosing a real .nup in the window was not exercised (the tests gave the game's extracted program files).

A jailbroken PS5 with a homebrew environment is needed. Never share the folder the builder makes: it comes from your game.