docs: input integration guide (cockpit -> RIOJoy -> game)
Companion to OUTPUT-INTEGRATION.md: the three input surfaces (ViGEm x360 pad, SendInput scancode keyboard/mouse, RioGamepad HID), per-button routing kinds incl. the fixed 11-button pad order, axis calibration + routing with the triggers-are-buttons trap and the shipped Descent pattern, per-game strategy, profile building/triggers workflow, benchless testing, checklist. Cross-linked from README and the output guide. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
@@ -5,7 +5,8 @@ through RIOJoy: the lighted buttons (lamps) and the plasma/VFD text display.
|
||||
This is the integrator's view — what the hardware can show, which addresses
|
||||
mean what, and how to feed them. The exact wire grammar lives in
|
||||
[FEEDBACK.md](FEEDBACK.md); the RIO serial protocol in
|
||||
[PROTOCOL.md](PROTOCOL.md).
|
||||
[PROTOCOL.md](PROTOCOL.md); the mirror direction (cockpit inputs → game) in
|
||||
[INPUT-INTEGRATION.md](INPUT-INTEGRATION.md).
|
||||
|
||||
## The four output channels
|
||||
|
||||
|
||||
Reference in New Issue
Block a user