KB: merge-reconciliation note (btinput stand-down; one input system per mode)
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
@@ -161,3 +161,16 @@ map `169.254.77.1=<steamID64>` → egg roster carries the token → mission proc
|
||||
`[steamnet] up ... 1 roster token(s) incl. self` → pod self-matches → stock console ladder →
|
||||
mission RUNS (46 ticks). 3-config build matrix green throughout. **Remaining (user hardware):**
|
||||
the live 2-account cross-machine session — procedure in `docs/STEAM_TEST.md`.
|
||||
|
||||
## 2026-07-18 — Merge origin/master (commit f889e24): btinput meets PadRIO
|
||||
|
||||
Master's 33-commit run landed (D1 relay/operator-console line, CONTROLS.MAP+XInput binding
|
||||
engine `btinput.cpp`, camera seats, torso pitch, sign fixes, the 1995 manual, version stamping).
|
||||
**The reconciliation:** btinput (ungated, dev/pod desktops) joined the stand-down convention —
|
||||
`BTInputPoll` yields and `BTInputSuppressKey` claims nothing when an operational cockpit device
|
||||
(serial RIO / PadRIO) owns the input path (`BTRIODevicePresent`; `BT_KEY_BRIDGE` override;
|
||||
forced harness exempt). **One input system per mode:** `CONTROLS.MAP`/btinput on dev+pod
|
||||
desktops, `bindings.txt`/PadRIO on glass. The D1 relay keeps its own raw sockets by design
|
||||
(relay and Steam are alternative wires; the BTNet seam covers the arcade mesh both need).
|
||||
Verified: 3-config build, glass stand-down live, pod forced-walk with btinput active, 2-node
|
||||
loopback MP 31/31.
|
||||
|
||||
Reference in New Issue
Block a user