v0.1.22: clearer message for a disc EBOOT

Changed

• "My game version shows 1.0, but RPCS3 says 1.04." The update is installed fine in that case: the EBOOT.elf chosen in the launcher was decrypted from the disc's EBOOT.BIN. The game-file check now says so and names the exact file to decrypt instead: the update's dev_hdd0\game\BCUS98125\USRDIR\EBOOT.BIN, via RPCS3's Utilities > Decrypt PS3 Binaries.

The launcher updates itself (Update now), or download inFamous2Recomp-v0.1.22-windows.zip / inFamous2Launcher.exe below.

v0.1.21: recover a cut-off first-start install

Fixed

• Black screen after the intro, every start, after the first start was closed early (#13). The first start copies about 2.5 GB of game data into game\hdd0 (as a PS3 does). If the game was closed during that copy (easy on a slower drive, since the screen stays dark), the half-made install folder stayed behind, and every later start believed the game was installed: it played the intro and then stayed black. Now the game checks the install when it starts. If it was cut off, the folder is moved aside to <title>_INSTALL.incomplete-<time> (nothing is deleted; you can delete that folder yourself afterwards) and the install runs again. Let the first start run until the menu appears.
• The first-start notice from v0.1.18 now also works for European copies (it was watching the US install folder).

Press Update now in the launcher, then Build / Play. From v0.1.20, only the last build step reruns; from an older version, every step runs once (v0.1.20 updated the toolkit). Or download inFamous2Recomp-v0.1.21-windows.zip / inFamous2Launcher.exe below.

v0.1.20: core placement for 6-core and Intel hybrid CPUs

Faster on more CPUs

• CPU core placement now works on 6-core CPUs and Intel hybrid CPUs (#3, #12). The game's busiest threads (the renderer and four SPU workers) get physical cores of their own, so no other thread slows them down. Until now that only happened on 8-core CPUs. Now:
  • 6+ core CPUs with SMT / Hyper-Threading (Ryzen 5 / 7, Core i5-12400, ...): about +13% fps in the heaviest fights (measured with the test PC limited to 6 cores: 35.6 -> 40.1 fps); busy-street walking is unchanged, and so are the worst moments.
  • Intel 12th-14th gen and Core Ultra with 6+ P-cores: those threads go on P-cores, and the game's main thread is kept off the E-cores; everything else uses the E-cores. (Decided per CPU; not measured on a hybrid CPU here, as the test PC isn't one: reports welcome!)
  • 4-core CPUs: no gain measured, so it stays off there.
  • It respects a limited CPU set (Process Lasso and similar).
  • PC Settings > Frame > CPU core placement (an advanced row) > Off turns it off if you ever suspect it.

Note: this updates the toolkit, so the first build after updating runs every step again (like the first install; the compile is the long part). Press Update now in the launcher, then Build.

The launcher updates itself (Update now), or download inFamous2Recomp-v0.1.20-windows.zip / inFamous2Launcher.exe below.

v0.1.19: moved folders play right away

Changed

• A moved or renamed game folder plays right away (#3). The launcher used to compile the game again after the folder moved, the long step. The compiled game doesn't depend on its folder, so now only the quick file check reruns and Play starts the game. The next real compile sets the build up in the new place by itself.
• Fixed: a step could run over and over when a path in its output pointed outside the folder (for example a linked game\ folder).

The launcher updates itself (Update now), or download inFamous2Recomp-v0.1.19-windows.zip / inFamous2Launcher.exe below.

v0.1.18: first-start install notice

Changed

• First start no longer looks like a black-screen hang (#13). The first time the game starts, it copies about 2.5 GB from your disc files into game\hdd0 (as a PS3 does), and the screen stays dark meanwhile. A notice now says so on screen ("First start: installing game data (2.5 GB). This takes a few minutes."), and another one says when it's done. Leave the game running until the intro appears; later starts are quick.

Only the last build step reruns: press Play in the launcher after updating. The launcher updates itself (Update now), or download inFamous2Recomp-v0.1.18-windows.zip / inFamous2Launcher.exe below.

v0.1.17: Save report makes a zip for GitHub

Changed

• Save report now makes a .zip you can attach on GitHub. GitHub refuses .log files, so Save report now also writes logs\report-<time>.zip. It holds the report plus your newest launcher log, game log and play-session issues file, with your user folder, user name and computer name replaced. It then offers to open the new-issue page: drag the .zip in.

The launcher updates itself (Update now), or download inFamous2Recomp-v0.1.17-windows.zip / inFamous2Launcher.exe below.

v0.1.16: download page when winget fails

Fixed

• Build tools' Install / Update buttons when winget fails (#8). If winget is missing or fails, or the tool still isn't found afterwards, the launcher now offers the tool's download page and says where to install it (e.g. LLVM 19+ into Program Files\LLVM). The launcher log now records winget's real exit code; before, it always said 0.

The launcher updates itself (Update now), or download inFamous2Recomp-v0.1.16-windows.zip / inFamous2Launcher.exe below.

v0.1.15: LLVM version check

Fixed

• Step 7 (build) fails with unknown type name '__m512i' / '__m256i' (#8). LLVM (clang-cl) 18 and older can't compile the game's AVX2 / AVX-512 code paths. The launcher now checks the LLVM version: an older one shows TOO OLD under the build tools with an Update button, which installs the current LLVM over it with winget. Then press Build; only the last step reruns.

The launcher updates itself (Update now), or download inFamous2Recomp-v0.1.15-windows.zip / inFamous2Launcher.exe below.

v0.1.14: RivaTuner freeze fix

Fixed

• Picture freezes (sound keeps going) with RivaTuner / MSI Afterburner's on-screen display (#10). RivaTuner's hook broke the separate layer the F1 options menu and the notices (such as "Controller: ... on player 1" at start) are drawn on: its Present failed with "device removed", which took the game's picture with it. When RivaTuner is running as the game starts, the menu and notices are now drawn into the game's own picture instead, which RivaTuner handles fine. Start RivaTuner before the game. (OVL_HOST=composition keeps the old layer if you want it.)

Only the last build step reruns: press Build (or Play) in the launcher after updating. The launcher updates itself (Update now), or download inFamous2Recomp-v0.1.14-windows.zip / inFamous2Launcher.exe below.

v0.1.13 -- catch an older firmware's libsre

Fixed

• An older firmware's libsre.prx is caught at the file check (#4). The port uses three SPURS modules from libsre.prx. Firmware 4.80's are different, so before this release the build ran for minutes and then stopped at step 6.
  • The launcher now checks those modules the moment you choose the file.
  • If they differ, it asks for libsre.prx from firmware 4.92 or newer.
  • Other firmwares whose modules match (e.g. 4.93) are accepted as before.
  • A build failure only blames libsre.prx when its modules actually differ.

The launcher updates itself (Update now), or download inFamous2Recomp-v0.1.13-windows.zip / inFamous2Launcher.exe below.