Warhammer 40,000: Boltgun (PPSA07247)

[THEMANnt]

Existing thread

• I searched this category for the title ID and no thread exists for this title on any platform.

Title

Warhammer 40,000: Boltgun (PPSA07247)

Content version tested

01.007.000

AnyPS5 commit

Unmodified main aff1f7190dbbe2449630335dc38962a5b048f24b, built in Release. No additional PRs or local source patches.

System tested

• Windows 11 Pro, build 26200
• AMD Ryzen 7 7800X3D; 32 GB RAM
• NVIDIA GeForce RTX 5070 Ti, 16 GB VRAM; driver 616.92
• MinGW-w64 GCC 15.2.0

Furthest point

In game

What is shown

The first launch initially showed a black window marked as not responding while shaders were being prepared. It subsequently progressed to the logo, became responsive, and reached gameplay.

During manual play, the frame rate was approximately 30–40 FPS after the scene rendered. One window-title sample reported 35.69 FPS; this is an observation rather than an instrumented benchmark.

Audio, save reload, and extended play were manually verified as working. The recorded session lasted about nine minutes (540 seconds) and exited naturally with code 0. This does not establish full-game completion or compatibility in every area.

Current blocker

No blocking issue encountered in the tested portion. Performance remains around 30–40 FPS, and the initial shader-preparation delay can temporarily look like a hang. No open PRs or local code changes were required for this run.

How it was run

Converted the game executable and bundled modules with the main-build relinker:

relinker.exe --windows --windows-diagnostics --registry "prepared-inputs/eboot.bin" "runtime/boltgun.exe"

Ran the resulting executable with the game assets under app0 and the same main build's runtime libraries under libs. Original sce_sys/param.json retained without overrides.

All gameplay controls were manual. APS5_PAD_INPUT_FILE pointed to an unused diagnostic input path; no scripted inputs were sent. No tracing or profiling switches were enabled. A background memory watchdog remained active and did not terminate the run.