Play overlay: FPS, turbo, volume, save states (Retro-Runtime retro_overlay)

[TechnicallyComputers]

Depends on RetroPortingToolKit/Retro-Runtime#3; the submodule is pinned to its head (c69f744). Based on feat/direct-home, because it adds to that branch's n64lle Settings page.

What

PlaySession feeds Retro-Runtime's retro_overlay and draws its layers. The hub draws no overlay of its own, so every core gets the same presentation.

Key	Does
F3 (also "Show FPS" in settings and the pause menu)	FPS, top left
Tab (held)	turbo, >> TURBO top right, sound dropped
+ / - (main row or keypad)	volume in 10% steps, meter on the right edge
F7, or SELECT+R1	save-state browser: 12 slots with thumbnails, pauses like the quick menu

• F3, not F: F is the recomp-ui default for FPS, but in the hub it drives C-Left.
• Save states:
  • They go over link 1.1, between frames, and live in <save_dir>/states/.
  • A core without savestates, or a 1.0 runner, gets a toast instead of the browser.
  • A refused load shows the runner's reason.
  • Buttons held when the browser closes stay out of the game until released.
• Settings: Show FPS and volume persist in <data_dir>/play.ini for every core. The n64lle Settings page edits them in an "Overlay & audio" section, saved with the page.

Checked

• Builds; ctest 14/14.
• PlaySession driven offscreen with injected key events, with the framebuffer read back at each step:
  • against the fake core;
  • against n64lle 0.375.0 / Pokémon Stadium:
    • FPS, TURBO and the volume meter drew in place;
    • the browser opened over the dimmed game;
    • saving slot 1 took about 40 ms and showed the game frame as its thumbnail, and loading it back worked;
    • no dispatch misses, bridges or faults.

Not checked

A real screen, a real controller (the SELECT+R1 chord, stick repeat), volume by ear, and the settings section as drawn. Those verdicts are Alex's.

🤖 Generated with Claude Code