featureJosh/Recompia v0.8.1-beta.7

Pokopia Recomp 0.8.1-beta.7 (Testing)

on GitHub

Changes in this build

• #303 Launcher: choose a build (Testing builds on joining, older builds with a warning)
• #300 Upscaler plumbing fixes (modes stay off) and menu pointer gate logging

Update: press Update in the launcher. If you come from 0.7.9 or older, run Set up again once when the launcher asks (0.8.0 changed the game build); from 0.8.0 on no Set up again is needed.

Game

• Added lines to pkp.log that say why the mouse pointer in menus is up or not
  • Before: when the mouse did nothing in a menu, the log could not say whether the window had lost focus, an overlay was open, the game was not in a menu, or the mouse setting was off
  • Now: play: menu pointer gate lines (at most 24 a session) show the state each time it changes, including whether [mouse] menu_cursor is on
• Fixed three small mistakes in the upscaler code that is switched off in this release (depth direction, number of jitter steps, when the picture history is reset). Nothing changes while the upscalers stay off
• Fixed pkp.log not saying which version you run
  • Before: the first lines of pkp.log read pkp $env:VERSION in every release, so a log could not be matched to a build
  • Now: the line shows the real version of the runtime (for example 0.8.1-beta.6)
• Fixed a wrong line in pkp.log about the menu mouse
  • Before: it said the mouse pointer moves the game's cursor in menus. It does not: the wheel and the keys move the selection, and a left click confirms the selected entry
  • Now: the line says what the mouse does

Launcher

• Added Settings > About > Choose a version, and a list of Testing builds when you join the Testing channel
  • Before: Update only ever installed the newest build, and there was no way to read about a build before installing it or to go back
  • Now: the list shows the builds of your channel (Testing builds and the normal releases on Testing, only releases on Stable), newest first, each with its notes. A newer one installs like an update. Going back to an older one asks first; a long way back (an older release line) shows a stronger warning with a box to tick before it can go on. The launcher first copies your save folder, pkp.ini, controls.ini, profiles.json and launcher.json to rollback-backups next to the game (the last three are kept), and stops without changing anything if that copy cannot be made. Joining Testing opens the list of Testing builds right away
• Added a question when you switch the launcher to the Testing channel, and help for testers
  • Before: switching to Testing just switched, and nothing said what to do when something went wrong
  • Now: the launcher asks you to confirm, and says Testing builds can have bugs and that testers are expected to share what they find and their pkp.log. While on Testing, Settings > About has Report a problem and Show pkp.log buttons. Each Testing build's notes now list what to test and how to report, and the bug form asks which channel you were on
• Fixed a start from a shortcut (Steam, Sunshine) ignoring a profile problem
  • Before: if the launcher could not write the chosen profile into pkp.ini, a start with --play carried on anyway and the game could open another player's save
  • Now: that start stops with a message, like Play in the launcher window
• Fixed a damaged profiles.json being replaced without a trace
  • Before: a cut-off or unreadable profiles.json turned into one default profile, and adding a profile then overwrote the file, losing which save belonged to which profile
  • Now: the damaged file is first copied to profiles.json.damaged-<date and time> next to it, and if that copy cannot be made nothing is changed. Your save folders were never touched
• Added Settings > About > Repair and reset for when a setting or a leftover file causes trouble
  • Before: the only fix was to edit pkp.ini by hand or delete files
  • Now: choose what to fix (game settings, controls, launcher settings, caches, old copies of the runtime and launcher). You see the list of files before anything changes, and a copy of the changed settings files is kept, so Undo last repair puts them back. Your saves, profiles, shaders and game files are never touched
• Added a Testing changelog to What's New for players on the Testing channel
  • Before: Testing builds were listed among the releases, each with the whole pending change list
  • Now: a Testing group with All Testing changes (every Testing build since the last stable release, newest first), what changed in each build, and its regressions and known problems as a highlighted block at the top. Stable players see no change
• Fixed the launcher feeling slow on Linux with an NVIDIA card: changing pages and scrolling lagged
  • Before: the Sunrise colours were a filter on the full-window background, which the launcher redrew on every page change. The picture itself was also much larger than the window needs
  • Now: the colours are part of the picture, which is smaller (about 180 KB for both themes instead of 430 KB for one), and a page change animates for 160 ms instead of 280 ms. It looks the same. On one test machine (RTX 4070 Ti, Wayland) the slowest frames of a page change (median of 6 runs each) went from 84 ms to 35 ms

What to test

• Choose a version: on Testing, open Settings > About > Choose a version. Read the notes of a build. Install the newest one if there is one. Report: what the list showed, anything missing or wrong, and how the install went
• Going back one build (only with a copy of your save folder): choose the build just before yours and read the question. Report: what the dialog said and whether the launcher restarted on the older build. Cancel is fine if you would rather not
• A long way back: choose a much older release and read the warning. The button must stay off until you tick the box. Please cancel unless you have a spare install; report whether the warning was clear
• Mouse in menus: open the pause menu and one more menu, move the mouse, click, scroll. A left click confirms the highlighted entry; the wheel and arrow keys move the highlight; the pointer does not pick. Report: what each did, and the lines in pkp.log that start with play: menu pointer gate and menu:
• Your version in the log: start the game, quit, and open pkp.log (next to pkp.exe). The line starting boot: pkp should show your version, for example 0.8.1-beta.6, not $env:VERSION. Report: what that line says
• Repair and reset (Settings > About > Troubleshooting): try each choice, one at a time. Before you start, copy your save folder. After each one, check that your save, your profiles and the game still start. Then try Undo last repair. Report: which choice, what the list showed, anything that did not come back, and the exact words of any error
• What's New on Testing: open All Testing changes and the newest build. Report: anything missing, cut off or confusing, especially the Regressions and What to test blocks
• Launcher speed: change pages for a minute in both colour themes. We measured it on one NVIDIA PC under Linux. Report: smooth or laggy (1 to 5), your graphics card, Windows or Linux (Wayland or X11), Steam Deck or another handheld
• Start the game after any repair and play for a few minutes. Report: whether it starts, how long the first start takes, any new stutter, and attach pkp.log

Regressions and known problems

• Going back to an older build has been tested with unit tests and in the launcher's test mode, not yet on a real install. The older launcher you land on may not have the newest pages
• Repair and reset has so far been tried only in the launcher's test mode and in unit tests, not yet on a real install. Make a copy of your save first, and report anything odd
• The launcher speed-up was measured on one NVIDIA PC under Linux. Other graphics cards, Steam Deck, Windows and X11 are not measured yet
• After Reset game settings, a setting you had set by hand (for example pool_mirror = off for Proton tuning) goes back to the game's default. Use Undo last repair if the game runs worse
• After Clear caches the first start builds the pipeline cache again and can stutter once

How to report

Open a bug report, choose Testing as the channel, say which version you have, and attach pkp.log (and setup.log if Set up ran). Thank you for testing.