Repository navigation
v0.1.4
Pre-release
Pre-release
·
31 commits
to main
since this release
Immutable
release. Only release title and notes can be modified.
Project Pyrrhus 0.1.4, a pre-release: partly playable, see docs/RELEASE-CRITERIA.md.
New in 0.1.4:
- Three optional gameplay settings, all off or original by default, kept in a new
gameplay.ininext tokeybinds.ini(orKZ2_AIM_ASSIST,KZ2_CROUCH_TOGGLE,KZ2_COVER_TOGGLEfor one run):crouch_toggle = 1makes crouch a toggle (tap to crouch, tap to stand; the game has this option itself but only turns it on online),cover_toggle = 1makes take-cover a toggle (tap to take cover, tap again, sprint or jump to leave), andaim_assist = offswitches the game's aim assist off (auto, the default, leaves it on for a pad and the keyboard). Hold to crouch and hold to take cover stay the default. Checked in scripted runs on the first level only. - A new install starts in a borderless window: the installer, the first-run prompt, the launcher and the game itself all default to it when no display setting exists yet; Alt+Enter switches to a window and back. An existing
display.inikeeps its mode, and exclusive fullscreen stays opt-in. - The game's whole post-processing chain (depth of field, upsampling, blur, bloom, film grain, Modulate, BloomIntegrate, ILR, Vignette, DepthToFuzzy, Downsample, Zero and the shared blend steps) now runs as native PC code by default, with bit-for-bit the same result as the SPU code on every input recorded in play. In our scripted runs on the first level its SPU time halved (31-42 to 16-19 milliseconds per frame), the median time from a button press to the frame being handed to Windows fell by about 12 ms, and the frame rate was ahead in 4 of 6 pairs (median 30.8 to 32.6 fps; the PC was shared with other work, so single pairs vary). Hand play is not measured.
KZ2_NATIVE_JOB_POST=0goes back to the SPU code;KZ2_NATIVE_JOB_<NAME>=0does it for one job. A few copies of shared steps that never ran in our recordings stay on the SPU code. - Depth of field now runs as native PC code by default, with bit-for-bit the same result (
KZ2_NATIVE_JOB_DOF=0goes back to the SPU code). In four of four scripted pairs on the first level the native version was faster (median 18 to 32 fps on that route). Hand play is not measured. - The game's data decompression (a zlib job that ran on the emulated SPU) now runs directly on the PC by default, with zlib 1.3.2 linked into the game (
KZ2_NATIVE_ZLIB=0goes back to the SPU job). The decompressed data is byte for byte the same, checked on two levels. In our scripted runs Corinth Sands started about 10 seconds sooner (70 to 60 seconds in three pairs), and frame times in play were unchanged. Hand play is not measured. - A frame waiting on a graphics job from the game's SPU code is resumed as soon as the job writes its result, instead of after a fixed 4 ms sleep. In two scripted pairs under Proton the wait between the game's frame request and the renderer's drain fell by 4 to 5 ms (median), and the whole time from a button press to the frame being handed to Windows fell by 2 ms in one pair and 12 ms in the other, to about 60 ms; the screen's own delay comes on top and was not measured. Hand play is not measured.
- The release notes on GitHub list each change as its own bullet, with the fixes in a list of their own, instead of one long paragraph.
- "Use my RPCS3 install" also finds a portable RPCS3 (the official Windows download is a zip) in a folder named
RPCS3in Documents, on the Desktop, in Downloads or at the root of a local drive, such asC:\RPCS3. Only those folders are looked at, and only one withrpcs3.exe,vfs.ymlorgames.ymlis offered. Picking the folder by hand works as before (#9).
Fixed:
- The release build now carries FFmpeg's headers into the installer and the portable zip, which the first run needs since 0.1.3; 0.1.3's own release build stopped there, so 0.1.3 was tagged but not released, and this version holds everything listed under it.
- Moving or renaming the unpacked portable folder after (or during) the first run no longer breaks it: CMake's build files kept the old folder's paths, so the build stopped with "CMakeCache.txt directory ... is different" or wrote into a folder with the old name. The first run and the launcher now notice the move, follow saved paths that were inside the folder (an extracted ISO), start the compiler's configure in an empty build folder and keep the lifted code, so only the compile runs again, and only when the game is updated or the build was not finished. A finished game keeps starting as it is. Checked with tests that move a temporary install between runs, not yet with a real portable install on Windows.
- The intro movie and the cutscenes were black and silent in every v0.1.2 install: the first run built the game without its movie decoder, because the release did not ship FFmpeg's headers and the build did not ask for them, so the game never loaded the FFmpeg DLLs installed beside it. The release now ships the headers (
ffmpeg/include, from the same LGPL FFmpeg build as the DLLs), the first run passes them to the build, the build stops if they are missing, and the first run's last check fails if the game was built without movie decoding. Installing this version over v0.1.2 rebuilds the game once. Reported by @kolomeets80 (#16). - The game stopped at the main menu, right after the intro, when the 1.29 update's data did not reach it: the 1.29 game then reads the disc's menus, which do not match it. The first-run check now fails (it only warned) when the update folder lacks
USRDIR\added_data_ps3.psarcor theUSRDIR\patch_data_ps3folder, the setup's update page asks for both, and the launcher checks the update folder before every start and says what is missing instead of starting a game that stops. Reported by @kolomeets80 (#16). - The game's log no longer shows the Windows user name: paths under
%APPDATA%,%LOCALAPPDATA%and the user's own folder are written as%APPDATA%\...,%LOCALAPPDATA%\...and%USERPROFILE%\...in every line of the log (for exampledisplay.iniandkeybinds.ini), and in the launcher'slauncher.log. Reported by @kolomeets80 (#16). - The setup and the first run refuse an install or build folder whose path contains
[,]or;, with a message, instead of failing later in the build: the bundled CMake cannot work from such a folder. The same failure was reported on Project Helghast (#20). - On a laptop with two graphics chips (for example an Intel iGPU and an NVIDIA or AMD GPU) the game could draw on the weaker chip. It now picks the high-performance adapter first, falls back to the default adapter and then to the software renderer, and writes every adapter it found and which one it chose to the log. Not yet confirmed on a hybrid laptop. Reported by @feanor-noldorin (#13).
- Switching to exclusive fullscreen no longer leaves the picture frozen if the next present fails: the swap chain is resized after every switch, a failed present is recovered from (the game leaves fullscreen and keeps drawing in a borderless window; only a lost graphics device, or eight failures in a row, stops the picture). Only tried under Proton, not yet on real Windows.
- The first-run log no longer keeps the Windows user name when a path is written in its escaped form, with doubled backslashes (an error message, or a list or JSON of paths). Reported by @feanor-noldorin (#9).
bump_version.pykeeps each file's line endings instead of writing Windows line endings when run on Windows. Reported by @feanor-noldorin (#9).tools/ps3recomp-patched.shstops before copying anything when git has checked the ps3recomp submodule out with Windows line endings (core.autocrlf, on by default in Git for Windows), and names the commands that fix it. Before, the patch series failed part-way through with a "patch does not apply" error. BUILDING.md has a note on cloning on Windows (#9).tools/ps3recomp-patched.shfinds a working Python 3 itself:python3, elsepython, else the Windows launcherpy -3. On Windows,python3is often the Microsoft Store alias, and the script used to stop with exit code 49 after applying every patch. With no working Python, it now stops before copying anything and says what it tried (#9).
If you have an earlier version, install this one over it: run the new setup and pick the same folder. The first start then translates and builds the game again where this version changes how it is built.
See CHANGELOG.md for the full list.
Windows installer (Project-Pyrrhus-setup.exe, recommended) and portable zip. You need your own Killzone 2 disc dump (US, BCUS98116), the 1.29 update and a decrypted EBOOT made from your own copy; none of them is included or downloaded. What each must contain: docs/GETTING-FILES.md. SHA-256 sums: SHA256SUMS (and the .sha256 files). See the README for what it does and what goes online.