PS5_RetroArch

0 Fork 0

mirror of https://github.com/mihawk-99/PS5_RetroArch.git synced 2026-10-22 00:22:29 -05:00

Files

T

Mihawk a9ae2500fb docs: the capture has to hook the menu-only path, not the runloop's max-frames block

Command: bash tools/verify.sh -> PASS (format unit build integration evidence).

Evidence for the finding: three console runs with
"--max-frames=120/200 --max-frames-ss --max-frames-ss-path=/app0/shot.png" staged in
/app0/args.txt (klog/run-shot-r5.log, klog/run-PPSA99169-030553.log) ran their whole
watch window, wrote no shot.png and left /app0/retroarch.log at its old 1200 bytes. The
runloop's max-frames block compares frame_count, which is refreshed from
video_st->frame_count, and only video_driver_frame increments that - the menu is drawn
through video_driver_cached_frame, so the block is not reached without content.

Patch 0029 (a runloop-side counter of the runloop's own iterations, tried on the console
for exactly this) was removed instead of committed: it had no verified effect, and an
unverified patch does not belong in the set. The patch count stays 34 and the configured
tree is back to the committed state. Next step recorded in docs/ACTIVE.md and
docs/PHASE_LOG.md: put the counter and the take_screenshot call in
video_driver_cached_frame (gfx/video_driver.c), where every menu frame passes.

2026-09-19 03:08:39 -04:00

ACTIVE.md

docs: the capture has to hook the menu-only path, not the runloop's max-frames block

2026-09-19 03:08:39 -04:00

DEPLOYMENT.md

Link the title and register the PS5 video driver

2026-09-18 14:37:57 -04:00

FINDINGS.md

Link Vulkan instead of dlopening it, because a PS5 title cannot dlopen a driver

2026-09-18 22:40:22 -04:00

PHASE_LOG.md

docs: the capture has to hook the menu-only path, not the runloop's max-frames block