Games · Compatibility · Home
Warhammer 40,000: Boltgun on AnyPS5
Windows is in game — logo then gameplay, with audio, save reload and about nine minutes of extended play — at about 30–40 FPS after the scene rendered on unmodified main aff1f7190d (Windows 11 Pro / Ryzen 7 7800X3D / RTX 5070 Ti), with no blocking issue in the tested portion and a first-launch shader-preparation delay that can look like a hang; Linux and macOS were not checked. Cited commit aff1f7190d (18 Oct) predates v0.1.3 (3fd1cc393b, 20 Oct). The cited furthest in-game used plain main. No cited run tested the official release zip. Whether the current official release zip matches this report is unknown, so an official zip may stop earlier. This title is not in the official table. Build source is main — the cited furthest in-game used unmodified main aff1f7190d, not a release zip. In game on that cited main commit is not a Playable claim. A single self-report is not an official-table row.
PPSA07247
Snapshot
| Stage | In game |
|---|---|
| Platforms in this snapshot | Windows |
| Build source | main · aff1f7190d |
| Last verified in snapshot | 18 Oct 2026 |
| Snapshot assembled | 14 Oct 2026 · checked 11 Oct 2026 |
Allowed values: release, main, fork, patched, unknown. Official table membership is not a release-zip claim.
Furthest public stage shown, including testing branches. Not an official playable verdict.
Page content updated: 22 Oct 2026. This date is when the page text changed. It is not a new hardware test.
Playable here can come from later main or extra patches. The official release zip may stop before that furthest stage.
Verified, blocked, unknown
Verified
- Windows 11 Pro, build 26200 / Ryzen 7 7800X3D / 32 GB RAM / RTX 5070 Ti 16 GB (NVIDIA 616.92) / MinGW-w64 GCC 15.2.0 / Release (discussion #7617, 18 Oct 2026): Warhammer 40,000: Boltgun PPSA07247 content 01.007.000 on unmodified main aff1f7190d, built in Release, no additional PRs or local source patches. Windows in game — 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. Unmodified main, not a release zip. Single community self-report. In game ≠ Playable.
- Same host and thread: relinked with 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. aff1f7190d predates v0.1.3.
Blocked
- Current blocker named in the report: none in the tested portion (discussion #7617). 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.
- Not checked in the cited report: full-game completion, compatibility in every area, Linux, or macOS. In game through the sampled session is not a Playable claim.
Unknown
- Official-table membership. This title is a community report (official: false), not a tested-compatibility table row.
- Whether the current official release zip matches this report.
- Linux. No cited Linux session of this title in discussion #7617.
- macOS. No cited macOS session of this title in discussion #7617.
- Network or online play. No cited report tests it.
- AMD or Intel GPU in-game reports. The cited Windows host is RTX 5070 Ti only.
- Play past the sampled nine minutes, or completion.
Saves, patch, and network
Saves
Status: Known
Known. Discussion #7617 says audio, save reload, and extended play were manually verified as working.
Game patch
Status: Known
Known. The cited report names Warhammer 40,000: Boltgun PPSA07247 content 01.007.000. Relinked with relinker.exe --windows --windows-diagnostics --registry. No extra title patch file is named as required. Furthest cited in-game used unmodified main aff1f7190d.
Network
Status: Unknown
Unknown. No cited report tests online or networked play.
Windows
Windows 11 Pro, build 26200 / Ryzen 7 7800X3D / 32 GB RAM / RTX 5070 Ti 16 GB (NVIDIA 616.92) / MinGW-w64 GCC 15.2.0 / Release (discussion #7617, 18 Oct 2026): Warhammer 40,000: Boltgun PPSA07247 content 01.007.000 on unmodified main aff1f7190d, built in Release, no additional PRs or local source patches. Windows in game — 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. Relinked with relinker.exe --windows --windows-diagnostics --registry. 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. aff1f7190d predates v0.1.3. The cited furthest in-game used plain main. Linux and macOS were not checked. Single community self-report. In game ≠ Playable.
Linux
No report in the cited thread. Linux was not checked.
Sources
Live threads beat this snapshot: Game bring-up discussions.
Need the files? Download v0.1.3 from GitHub, then relink. This page is not a store and does not host games.