v0.1.5

Project Helghast 0.1.5, a pre-release: partly playable, see docs/RELEASE-CRITERIA.md. New in 0.1.5:

Fixed

• Settings you add to kz3.ini by hand (for example discord_presence = 1) are kept when the game starts. Comments in the file are not kept.
• When the game opens a file to create, truncate or append to it, the request is read with the PS3's flag values. No visible change from this has been seen yet.
• When the setup stops, its message box says why (the same reason the log has), and the next start asks again for the file that was wrong. The EBOOT page refuses the disc's 1.00 EBOOT and names the update's USRDIR folder, where the 1.14 one is (#8, thanks @genericuser001).
• With a decrypted ISO as the disc dump, the first check no longer stops with "No module named 'iso9660'" (#15, thanks @MOW531).
• When a game-file check fails, the setup and the first start say which input failed (disc dump, 1.14 update or EBOOT), the path, what is there and what it must hold. They spot a swapped disc and update, or a drive root, and say which inputs passed. The README starts with a Windows quick start (#10, #12, #13, thanks @Tzeentchnet and @Jayinem).

Added

• Options > Display > Discord status (On/Off, off by default): shows "Playing Killzone 3" and your chapter on your Discord profile through the Discord app on this PC; the choice is saved in kz3.ini (discord_presence).
• Start menu entry "Discord status on or off": shows whether the Discord status is on and switches it (the port tells the Discord app on this PC what to show on your profile; nothing is sent when it is off; the Discord app must be running).

See CHANGELOG.md for the full list.

Windows installer and portable zip. You need your own Killzone 3 disc dump (a folder or a decrypted ISO), the 1.14 update and a decrypted EBOOT from your own copy; none of them is included or downloaded. SHA-256 sums: SHA256SUMS (and the .sha256 files). See the README for what it does and what goes online.

v0.1.4

Project Helghast 0.1.4, a pre-release: partly playable, see docs/RELEASE-CRITERIA.md. New in 0.1.4:

Fixed

• Mouse look no longer holds still and then jumps to a new direction in busy scenes (seen at the start of the first level): mouse, keyboard and pointer input is now read on every frame tick. In our tests at that spot the view follows the mouse without jumps.
• Opening Options > Wireless Controller or Options > Display after installing a new version no longer ends the level with error 20000: the game's file cache is rebuilt once when the installed version changes, so the first start after an update loads a little slower.
• The game log now records the scheduler and memory lines that tell us whether a fix is in your build.
• When the first start asks for the decrypted EBOOT, a folder is accepted too: the setup looks for EBOOT.elf in it and in its USRDIR folder, and says so when it is not there.

See CHANGELOG.md for the full list.

Windows installer and portable zip. You need your own Killzone 3 disc dump (a folder or a decrypted ISO), the 1.14 update and a decrypted EBOOT from your own copy; none of them is included or downloaded. SHA-256 sums: SHA256SUMS (and the .sha256 files). See the README for what it does and what goes online.

v0.1.3

Project Helghast 0.1.3, a pre-release: partly playable, see docs/RELEASE-CRITERIA.md. New in 0.1.3: the game no longer stops a few seconds after a level starts (for example after the chapter 1 movie); the setup had built the game with the wrong table of replaced functions for the 1.14 update. If you have an earlier version, install this one over it: the first start lifts and builds the game again. A disc dump whose game archive is split into parts (data_ps3.psarc.66600, .66601 and so on, as a FAT32 drive stores it) is accepted as it is. The Asian (BCAS25008) and Japanese (BCJS30066) discs are accepted as untested regions. The first run checks the disc's game archive against the known copy and says when it differs. The game folders are given once: a later first start checks the folders from the setup instead of asking for them again. The game window shows the project's icon. A new page, docs/GETTING-FILES.md, shows what each input must contain and what every first-run check code means. See CHANGELOG.md for the full list.

Windows installer and portable zip. You need your own Killzone 3 disc dump (a folder or a decrypted ISO), the 1.14 update and a decrypted EBOOT from your own copy; none of them is included or downloaded. SHA-256 sums: SHA256SUMS (and the .sha256 files). See the README for what it does and what goes online.

v0.1.2

Project Helghast 0.1.2, a pre-release: partly playable, see docs/RELEASE-CRITERIA.md. New in 0.1.2: on PCs in time zones west of UTC (the Americas) the build no longer stops with "manifest 'build.ninja' still dirty after 100 tries"; if you hit that with an earlier version, uninstall and install this one. A decrypted disc ISO works as the game source next to a folder dump; the EU disc (BCES01007) is accepted as an untested region; the disc page names the disc it found and refuses other games. See CHANGELOG.md for the full list.

Windows installer and portable zip. You need your own Killzone 3 disc dump (a folder or a decrypted ISO), the 1.14 update and a decrypted EBOOT from your own copy; none of them is included or downloaded. SHA-256 sums: SHA256SUMS (and the .sha256 files). See the README for what it does and what goes online.

v0.1.1

Project Helghast 0.1.1, a pre-release: partly playable, see docs/RELEASE-CRITERIA.md. New in 0.1.1: opt-in crash reports. When turned on, the launcher sends one scrubbed report after a crash, never a memory dump; see CHANGELOG.md.

Windows installer and portable zip. You need your own Killzone 3 disc dump, the 1.14 update and a decrypted EBOOT from your own copy; none of them is included or downloaded. SHA-256 sums: SHA256SUMS (and the .sha256 files). See the README for what it does and what goes online.

v0.1.0

Project Helghast 0.1.0. Windows installer and portable zip. You need your own Killzone 3 disc dump and the 1.14 update; neither is included or downloaded. SHA-256 sums: SHA256SUMS (and the .sha256 files). See the README for what it does and what goes online.