Pokopia Recomp 0.7.8 (build K: Kudu)

Press Update in the launcher and it does the rest. The game code is unchanged, so you do not need to Set up again.

This update adds a Mods folder for community translations and texture mods, removes the resize grip that stuttered, and makes the README available in four more languages. If a mod does not load, please open an issue and attach pkp.log from the game folder: the log now warns when none of the mod's files replaces a game file.

~Jerban

Known issues

• Linux still runs the game and the shader setup through Proton.
• Mods that replace files containing shaders are not supported. Mods that only change text or textures are the intended use.
• The translated READMEs are machine translations and may contain mistakes. The English README is the authoritative text.
• Use the game clock in single player only for now.

New

A folder for text and texture mods

Before: using a translation or texture mod meant replacing files inside the game dump, and going back to the original meant keeping a second copy.

Now: Settings > Game has a Mods row, saved in pkp.ini as [fs] romfs_mod. Choose a folder, and its files replace the update and base game files that have the same path. Folders are merged, and files that exist only in the mod are served too. Leave the row empty to turn mods off. Adding, swapping or removing a mod does not change the shader cache key and never asks for Finish update. No mod is bundled with this project: get one from its author.

Choosing the right folder: the folder must contain the same files and folders as the game's own romfs, starting at its top level. If a download has an outer folder (for example 2.0.1/romfs/...), choose the inner romfs folder, the one that contains LD_C0_R.BIN. If the level is wrong, pkp.log now says that none of the mod's files replaces a game file. The README shows an example, in English and in Portuguese (Brazil).

Still not: mods that replace files containing shaders are unsupported and need Set up to be run again by hand.

The README in Simplified Chinese, Spanish, Arabic and Hindi

Before: the README was English only.

Now: the README and the Linux package's README.txt have machine translations in Simplified Chinese, Spanish, Arabic and Hindi, so more people can follow the setup and share their own translation mods. They are in docs/i18n/, and the Linux download includes them as README.<language>.txt. A pull request check keeps their structure in line with the English file, and tools/i18n/README.md explains how to refresh or add a language.

Still not: no native speaker has reviewed these translations yet. Corrections are welcome as pull requests.

Shader files take about a fifth of the space (prototype, not measured on a full cache yet)

Before: the translated shaders were ~99,000 separate files, about 26 GB, for a 12 GB game. Setup needed about 36 GB free.

Now: they can be packed into a few compressed files in shader_cache/spirv.archive. The game reads them as quickly as loose files,
so it runs the same, and nothing is translated again to switch. When the launcher finds loose shader files after a finished setup, it
asks once per start: Free up about N GB? (a few minutes, can be stopped and continued). Settings > Game > Shader files has the
same button, and Use loose files to go back. A new setup packs as it translates (on by default, Packed shader files on the
Set up page), so the loose files never pile up: a new setup now needs about 14 GB free instead of about 31 GB (36 GB was
quoted before), and the free-space check and the Set up page follow the toggle. The launcher writes the real sizes and times to
setup.log.
Loose shader files are on their way out: a later release stops reading them.

A Nearest upscaler, and the other upscalers are switched off for now (#232)

Before: the upscaler list offered FSR 1, FSR 3, DLSS, DLAA, NIS and XeSS. Several of them looked glitchy or no different from Off, and there was no way to keep a sharp pixel look.

Now: there is a new Nearest upscaler (sharp pixels, no smoothing), next to Off and FSR 1, in the launcher and on the F1 page. FSR 3, DLSS, DLAA, NIS and XeSS are switched off until they are reworked: if your settings use one of them, the game runs with Off instead. Their code stays in place.

If Nearest or the switched-off modes behave oddly, please open an issue.

Fixes

Link Play kept old settings between sessions (#239)

Before: a mode = join:<address> left in pkp.ini from an earlier visit made the game visit-only, so a room you hosted could not be reached, and with a relay set the game switched Link Play off.

Now: the launcher puts the Link Play settings back to their defaults when it starts (Off stays Off). The Link Play page still remembers your addresses and room codes, so your last setup is one click away. The page no longer fills in this PC's own relay address while that relay is not running. The log warns when a join address is set, and internet play through a relay uses auto even if an old join address is left in the file. Starting the game from Steam with --play keeps your last saved settings.

Link Play now shows the address to share, and refuses your own PC's address (#245)

Before: the Link Play page only listed this PC's local network and VPN addresses, so a host over the internet shared the 127.0.0.1 from the relay field. On a friend's PC that address means the friend's own PC, so the friend could not find the room.

Now: when you host over the internet, the first row under "Share with visitors" is Over the internet: this PC's public address with a copy button, with the right port for your relay or for direct hosting. A visitor who types a 127.x address is told it is their own PC. To find the public address the launcher makes one small request to a what-is-my-IP service (api.ipify.org, with ipv4.icanhazip.com as a backup), only while the page shows an internet host.

Still not: on a connection where the provider shares one public address between many customers, the address found is the provider's, and port forwarding cannot work there. The page cannot detect that.

A controller switched off and on again was not found on Linux (#226)

Before: on SteamOS and other Proton setups, a controller that was turned off and on again was not seen until the game was restarted.

Now: under Wine and Proton the game checks the four controller slots once a second and rescans the controllers when they change. The log line rescanning gamepads shows when it happens.

Still not: a controller that Proton shows only as a generic device (no controller slot) still needs a restart.

Photos were blank in the in-game album with HDR on (#229)

Before: with HDR on, photos did not show in the in-game album or main menu, while "Save to console album" still wrote a correct picture.

Now: the game's pictures that the CPU writes into HDR render targets are converted and uploaded instead of dropped.

If photos are still blank with HDR on, please open an issue and attach pkp.log.

DLC inside a .nup is unpacked (#236)

Before: the .nup unpacker skipped add-on packages, so DLC never reached the add-on folder and had to be built by hand.

Now: add-ons with a RomFS are unpacked into nup_dump/aoc/<id>/romfs/, which the launcher already finds. An earlier finished unpack gets its add-ons the next time you pick the file.

The bottom-right resize grip stuttered while dragging

Before: dragging the resize grip in the bottom right corner of the launcher stuttered.

Now: the grip is gone. The window edges and corners resize the window as before, without the stutter.