Deploy: --pipe trim -- named-pipe serials to vRIO/vPLASMA for every mode
Dev-rig policy (2026-07-17): everything on the dev machine runs named pipes to vRIO until Real-RIO testing -- no com0com. pod-launch --pipe selects the <mode>_pipe conf (serial1=namedpipe pipe:vrio, serial2=namedpipe pipe:vplasma); pipe variants of all three deploy templates (auto-staged/ rendered) + a dev-tree net_loop_pipe.conf beside the existing RP one. Requires the vRIO dist >= 20260716-68e3d1f (VRioPipeService/ VPlasmaPipeService landed there). Arcade cockpits with the physical RIO keep the plain COM-port confs. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
@@ -70,6 +70,7 @@ see `../CAMERA-REVIEW-NOTES.md`. Default mode: `bt`.
|
||||
| `--layout cockpit\|explode` | `cockpit` = borderless VDB head windows (default); `explode` = 7-window debug |
|
||||
| `--no-bridge` | pod only, no GL render window |
|
||||
| `--no-focus` | skip the renderer-topmost / DOSBox-focus pass |
|
||||
| `--pipe` | use the `<mode>_pipe` conf: serials as named pipes to vRIO (`pipe:vrio`) + vPLASMA (`pipe:vplasma`), no com0com. **Dev-rig policy (2026-07-17): always `--pipe` on the dev machine** — vRIO dist ≥ `20260716-68e3d1f` speaks the pipe; the plain confs (real COM ports) are for cockpits with the physical RIO/plasma |
|
||||
|
||||
### Window placement (per-rig; normally fixed, overridable per-launch)
|
||||
|
||||
|
||||
Reference in New Issue
Block a user