BT_POD_RGB: the authentic RGB-split output -- one window per VGA PORT

Implements what the pod actually does (pod-hardware.md THE RGB SPLIT): a VGA
port's R/G/B lines each drive a separate mono MFD monitor, so a window is not
one MFD -- it is one PORT carrying up to three.  BT_POD_RGB=1 collapses the
five MFD windows into the two ports the cab drives (Port A: Comm=red,
Mfd2=green, Heat=blue; Port B: Mfd1=red, Mfd3=green) and composites each
group's planes into the colour channels, leaving the radar on its own
full-colour port.  Channel comes from the live port (GetEnableID), never a
hardcoded table, so an Eng-page swap follows automatically; BlankColor planes
contribute nothing, exactly as on the pod.  Implies BT_POD_SURFACES (bare
640x480 pictures -- the cab's buttons are physical).

Verified locally (bare windows, "RGB COMPOSITE of 2 plane(s): Comm Mfd2") and
LIVE ON NICK'S CRASH CART over the tailnet: Port A -> DISPLAY4, Port B ->
DISPLAY2, radar -> DISPLAY1, all exact-fit.  Pod scratch kit included (ssh
helper, layout cfgs for both modes, launcher; the mission-egg launcher fix --
a bare MP.EGG exits the mission loop with no relay, and BT_FE_SOLO parks at
the menu, so neither lights the panels).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
Joe DiPrima
2026-08-06 12:55:05 -05:00
co-authored by Claude Fable 5
parent e0e9dcc292
commit e179c7033f
4 changed files with 155 additions and 11 deletions
+9
View File
@@ -0,0 +1,9 @@
# BT411 -- ALPHA-MR, RGB SPLIT mode (BT_POD_RGB=1). Each line is ONE VGA PORT
# whose R/G/B lines feed three mono MFD monitors:
# VGA Port A : Comm=red, Engineering/Mfd2=green, Heat=blue
# VGA Port B : Mfd1=red, Mfd3=green (blue spare)
# Console-session displays: DISPLAY3 800x600 primary (main view),
# DISPLAY4 800,122 / DISPLAY2 1440,123 / DISPLAY1 2080,124 (all 640x480).
VGA Port A=800,122,640,480,noframe,bare
VGA Port B=1440,123,640,480,noframe,bare
Secondary / Radar=2080,124,480,640,noframe,bare
+4 -10
View File
@@ -1,18 +1,12 @@
@echo off
REM BT411 pod launch -- runs from the game's content dir in the CONSOLE session.
REM Started via schtasks /IT so the windows land on the REAL panels (an SSH
REM session is session 0 with a dummy display and would render nowhere).
REM BT411 pod launch -- console session (started via schtasks /IT).
cd /d C:\bt411\BT411_4.11.801\content
REM glass cockpit, per-display windows, POD surface mode (bare 640x480 pictures,
REM no on-screen button banks -- the cab's buttons are physical), sticky layout
REM loaded from glass_layout.cfg beside this file.
set BT_GLASS=1
set BT_GLASS_PANELS=1
set BT_POD_SURFACES=1
set BT_POD_RGB=1
set BT_GLASS_LAYOUT=load
set BT_GLASS_LOG=1
set BT_START_INSIDE=1
set BT_FE_SOLO=1
set BT_LOG=podrun.log
start "" ..\build\Release\btl4.exe -egg MP.EGG
start "" ..\build\Release\btl4.exe
+12
View File
@@ -0,0 +1,12 @@
@echo off
REM BT411 pod launch -- console session (started via schtasks /IT).
cd /d C:\bt411\BT411_4.11.801\content
set BT_GLASS=1
set BT_GLASS_PANELS=1
set BT_POD_RGB=1
set BT_GLASS_LAYOUT=load
set BT_GLASS_LOG=1
set BT_START_INSIDE=1
REM no front end -- straight into a mission
set BT_LOG=podrun.log
start "" ..\build\Release\btl4.exe -egg PODTEST.EGG