Independent community database.

Hi-Fi RUSH

Issues

PPSA17191 · Windows · Title screen visible and responding to presentation; ~11 FPS with queue memory-wait bottleneck

Current conclusion

A Windows main 2f161d4f33f8 test of Hi-Fi RUSH displays the 'Press Any Button' title screen at about 11 FPS on an RTX 5070 Ti with 3840×2160 guest output.

An eight-second trace recorded 93 presents, median 84.9 ms per frame and 19.7 ms of GPU work per present. Queue worker 0x20 spends about 84.6 ms of each frame waiting on memory, but the source has not identified the awaited label or its late writer. An earlier untraced gameplay corridor run was described at roughly 9 FPS; it is not equivalent to the captured title-screen performance.

Hi-Fi RUSHPS5
Hi-Fi RUSH — promotional gameplay screenshot

Platform test results

Windows · Title screen visible and responding to presentation; ~11 FPS with queue memory-wait bottleneck

Issues

At the title screen, the recorded eight-second trace covers 93 presents, median 84.9 ms and p90 92.7 ms per frame, approximately 11.6 presents/second. GPU work averaged 19.7 ms per present; queue worker 0x20 spent about 84.6 ms/frame waiting in Driver.Packet.memory_wait. Its waits reached roughly 92–114 ms each.

Queue 0x0's event buffer filled 6.4 seconds into the trace, but queue 0x20's trace was complete. The author has not isolated which queue or guest event sets the awaited label. An earlier first-corridor measurement around 9 FPS had no attached capture.

Build: Unmodified main 2f161d4f33f8 (clean); APS5_PLAYGO_UNLISTED_CHUNKS=installed; warm shader caches; APS5_TRACE_SECONDS=60:8 performance trace
Report: Oct 21, 2026

October 21 Hi-Fi RUSH title-screen trace and 0x20 memory wait (#9117) ↗

Known issues

Windows · Title screen visible and responding to presentation; ~11 FPS with queue memory-wait bottleneck

  • A memory-wait on queue worker 0x20 dominates title-screen frame time, with far less measured GPU execution time; the exact producer and synchronization root cause are unresolved.
  • One trace with a partially dropped queue-0 event stream cannot establish an across-build FPS improvement or whole-game playability.

Test environments

Platform
Windows
Game version
01.004.000
Hardware / tools
Windows 11 build 26200; AMD Ryzen 7 9700X (16 threads); RTX 5070 Ti, NVIDIA 616.64; 31,801 MiB reported system memory; 3840x2160 guest output in window

PPSA17191, Hi-Fi RUSH content version 01.004.000. This Windows RTX 5070 Ti trace measures the unmodified main title screen (Press Any Button), not a repeatably measured gameplay segment.