Furi on PC: official version and experiment
An official PC route is linked separately below. The records on this page concern the PS5 executable or named homebrew build.
What is established for Furi AnyPS5? A Windows report reaches tutorial combat on an unmodified main build, then crashes in the prison area after the tutorial boss. Three original screenshots document the menu and fight.
Furi AnyPS5: compatibility evidence
Furi already has an official PC edition. This page records a different experiment: its PS5 PPSA06147 v01.007.225 executable, relinked with AnyPS5 main ea5c27b53e5bc7eff6f128aaf333766d562d8bea on Windows 11. Source ↗
The tester supplies menu and tutorial-fight captures and reproduces an AK::EventManager access violation after the tutorial boss in two runs. The report proposes an audio-object lifetime explanation, but does not establish the exact root cause or a verified fix. No complete playthrough is reported. Source ↗
This title has guest modules in Media/Modules and Media/Plugins in addition to the usual sce_module folder. The source uses repeated --module-dir options and separately stages matching host PRXs with their supporting DLLs. Its backup-module ambiguity was investigated without deleting the original files. Source ↗
Compare builds and reported hardware
| Hardware / platform | Build / reported result | Evidence |
|---|---|---|
| PPSA06147 Ryzen 5 5600X Radeon RX 6600 16 GB RAM · Windows | main ea5c27b53e5bc7eff6f128aaf333766d562d8bea · Release · GCC 15.2.0 · no local changes Gameplay reported Menus and tutorial combat reported, with original captures. The prison area after the tutorial boss crashes in both recorded runs. Main snapshot · Test date unknown | Details ↓ Report ↗ |
Test reports
Furi AnyPS5 · Windows · Main snapshot
Gameplay reportedMenus and tutorial combat reported, with original captures. The prison area after the tutorial boss crashes in both recorded runs.
- Title ID
- PPSA06147
- Test date
- Unknown — not stated in source
- Post date
- 2026-10-17
- System
- Windows 11 build 26200 · CMake 4.3.1 · Ninja 1.13.2
- Tested build
- main ea5c27b53e5bc7eff6f128aaf333766d562d8bea · Release · GCC 15.2.0 · no local changes
- Reported CPU
- Ryzen 5 5600X
- Reported GPU
- Radeon RX 6600
- Reported RAM
- 16 GB
- Evidence
- zanopi ↗
No verified fix for the AK::EventManager access violation. Window-title FPS in screenshots is a momentary reading, not an averaged benchmark. No APS5 switches or local source patches were used.
Known limitations
- AK::EventManager reads outside a live object after the tutorial boss, reproduced in two runs; the cause remains under investigation. Evidence ↗
- Extra guest-module folders and matching host-library DLL dependencies must be staged separately. Duplicate backup modules can cause an ambiguous dependency name. Evidence ↗
Reported milestones
Windows source report adds menu and tutorial-fight screenshots, exact build and a repeatable post-boss crash.
Source ↗
More community captures
Community image unavailable. View the original report ↗
Community image unavailable. View the original report ↗
Common questions
Can I play Furi on PC without AnyPS5?
Yes. Furi has an official PC edition. The records here concern the experimental PS5 conversion, not a requirement for playing the PC game.
Does the report prove Furi is fully playable?
No. It reaches tutorial combat and then reports a repeated crash after the boss. Neither the screenshots nor a successful conversion establish a full playthrough.
Should every title use Media/Modules and Media/Plugins?
No. Those folders belong to this title’s source layout. Check your title and the exact relinker revision before adding extra module paths.
Furi AnyPS5: is this a complete playthrough?
The selected reports establish only their recorded scenes and stopping points. None of these entries establishes full-game completion. Read the original report before extending its scope.
Furi AnyPS5: are these minimum requirements?
No. The hardware belongs to a particular reported build and test. It is not a minimum specification, a recommendation for the official PC edition or a prediction for another machine.
Furi AnyPS5: which game edition is tested?
Furi reports here concern the PS5 edition identified by each title ID. Results from another console generation or the official PC edition must be kept separate.
Has Port Record reproduced this test?
No. These are reviewed community reports. Follow the original source for its complete environment; our review date is not a test date.
Furi AnyPS5: prepare the same build
Use the title’s build and patches as your reference. These tools prepare input and compare records; they do not reproduce a test.
Relinker command builder ↗
Choose a platform, check module folders and generate a quoted v0.1.2 command.
ELF header checker ↗
Read the first 64 bytes of a local file. Inspect the format before conversion.
Compare my PC ↗
Find hardware components in sourced reports. See the exact build and limitations.
To investigate Furi AnyPS5, start from the source attached to the exact platform and build record. Preserve the local patches, game version and observed scene before comparing a new result. A source update can change the context after this review.