Hello Neighbor on AnyPS5

Verified

• Windows 11 Pro / WinLibs GCC 15.2.0 / NVIDIA GeForce RTX 5090 32 GB (NVIDIA 617.42, Resizable BAR on) / AMD Ryzen 9 9950X3D / 64 GB RAM (discussion #6991, 19 Oct 2026): Hello Neighbor PPSA35154 content 01.001.000 on main 81cb86339 with #7603 on top. Windows in game — Continue reached the street in front of the house at the start of Act 1. Four runs of 4 to 11 minutes had no stop; two of them started from a fresh save and went through the menus. The act menu runs at about 31 FPS. The window-title counter over 60 s starting 120 s after Continue read 7.9 and 7.7 FPS on two runs. #6455 and #6678 are merged in that main. The reporter does not expect #7603 to matter here. #7603 has since merged (20 Oct) and is not in v0.1.3. 81cb86339 is in v0.1.3. Single community self-report. In game ≠ Playable.
• Same Windows host and thread: Relinked with relinker --windows source/eboot.bin hello-neighbor.exe. Those flags are relinker flags, not a game patch. eboot.bin and the 5 modules in sce_module were unwrapped from fSELF with tools/unwrap_self.py. That unwrap is a conversion step, not a game patch. Import audit on 81cb86339 found 0 absent imports and 52 stubs. None of the stubs was called. No extra title patch file is named as required. The 19 Oct runs used APS5_PAD_INPUT_FILE. The draw-input patch was not checked on that build.
• Same Windows host (discussion #6991, 17 Oct 2026): unmodified main 47a266cf9 with no pull requests on top. Continue to the Act 1 street, 60 s of window-title frames starting 120 s after Continue: 3.6 FPS in game. The same method with #6455 + #6678 on that commit read 8.1 FPS. #6455 and #6678 have since merged and are in 81cb86339 and in v0.1.3.

Blocked

• Current blocker named in discussion #6991: performance. The 19 Oct Continue runs on main 81cb86339 with #7603 read about 7.7 to 7.9 FPS in game. On unmodified main 47a266cf9 the same method read 3.6 FPS. Earlier profiled runs were CPU-bound on queue 0; the GPU was about 10 % busy. In game ≠ Playable.
• The form furthest point is In game. The body says the title is playable in game; that is a casual claim. In game on that cited main 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. The cited play used main 81cb86339 with #7603 on top, not a release zip. v0.1.2 was checked and stopped; the v0.1.3 zip was not checked.
• Linux. No cited Linux session of this title in discussion #6991.
• macOS. No cited macOS session of this title in discussion #6991.
• AMD or Intel GPU in-game reports. The cited Windows host is GeForce RTX 5090 only.
• How far play went past the Act 1 street, or completion. The cited later sessions name Continue to that street and runs of 4 to 11 minutes only.
• The second-cutscene crash on later main. One run on 153d5d469 hit FATAL: unhandled exception 0xc0000005. Later Continue runs start after that cutscene and did not retest it.
• The draw-input patch and #6763 on the 19 Oct build. The reporter says that patch was not checked there.
• Other Hello Neighbor titles. This page is Hello Neighbor PPSA35154 only, not Hello Neighbor 2.
• Whether the current v0.1.3 zip, which includes #5760, still stops as v0.1.2 did after New Game.

Saves

Status: Known

Known. Discussion #6991 says the menu finds save slots, New Game loads, and Continue loads the street at the start of Act 1. Two of the four later runs started from a fresh save and went through the menus.

Game patch

Status: Known

Known. The cited report names Hello Neighbor PPSA35154 content 01.001.000. Relinked with relinker --windows source/eboot.bin hello-neighbor.exe. Those flags are relinker flags, not a game patch. eboot.bin and the 5 modules in sce_module were unwrapped from fSELF with tools/unwrap_self.py. That unwrap is a conversion step, not a game patch. No extra title patch file is named as required. Furthest cited in-game used a patched stack: main 81cb86339 plus #7603. #7603 has since merged (20 Oct 2026) and is not in v0.1.3. 81cb86339 is in v0.1.3.

Network

Status: Unknown

Unknown. No cited report checks online or networked play.