BlackMark 056a478e19 Forward rumble back to the guest controller (both backends) ...

The XInput hook used to swallow XInputSetState; now it records the requested
left/right motor speeds into the status back-channel (protocol v8->v9: per-slot
rumble_left/right in HookStatus). Each frame the host reads them and, only on
change, drives the guest's actuator via the active backend:
- XInput: XInputSetState on the guest's slot (the open question is whether Steam's
  RPT virtual pad accepts vibration and routes it to the guest -- needs live RPT);
- Steam Input: SteamInput TriggerVibration on the slot's controller handle, with the
  XInput fallback for slots Steam isn't driving.

InputSource gains a set_rumble(slot,left,right) hook (default no-op) implemented by
both backends; SteamInputSource now tracks per-slot controller handles + which slots
it drives.

Verified: hook_selftest (x64 + x86) now asserts the hook records the rumble from
XInputSetState into the status; full build x64 + x86 clean; ctest x64 9/9, x86 3/3.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

2026-06-21 05:11:33 +02:00

..

audio_ring.hpp

Audio render-hook M1: shared audio ring + protocol diag fields

2026-06-19 11:49:18 +02:00

log_ring.hpp

Log window: stream the hook's logs over IPC into an in-app Log panel

2026-06-19 20:25:04 +02:00

protocol.hpp

Forward rumble back to the guest controller (both backends)

2026-06-21 05:11:33 +02:00

shared_memory.hpp

Phase 2: Present-hook video path (shared-texture mirror)

2026-06-20 11:34:12 +02:00

tool_paths.hpp

Restructure bin/: deployables at root, tests and tools in subfolders

2026-06-21 00:59:03 +02:00