Files
TeslaSuite/Console/RedPlanet/Apps.xml
T
CydandClaude Fable 5 cb7c655530 Promote vPOD to a top-level project (Console/vPOD -> vPOD/)
vPOD has outgrown its home inside the console's folder: it now emulates both
halves of a pod (Munga game client + TeslaLauncher service / provisioning),
so it lives at the repo root beside Console/, Launcher/, Contract/ and
SecureConfig/, like the peer it has become.

Accompanying changes: project references rebased (Contract, SecureConfig,
the console's vendored Munga Net.dll), solution + DiffTests reference paths,
the console csproj's now-obsolete vPOD source exclusion removed, and the
root README / Apps.xml / vPOD README path mentions updated. pack.ps1 is
self-relative and now emits vPOD/dist/vPOD.zip.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-10 09:52:59 -05:00

144 lines
6.2 KiB
XML

<?xml version="1.0" encoding="utf-8"?>
<!--
Tesla Console product catalog.
This file is the single source of truth for installable products and the
launch entries each one registers on a pod. It replaces the products that
were previously hardcoded in SiteManagement.cs.
Element/attribute reference:
<Product id = install/product key (Guid) used while transferring the package
name = friendly product name (used in menu + status text)
menuText = exact text shown in the Install Product submenu
hostTypeDialog = "true" to prompt for resolution + roles
(Game Client / Live Camera / Mission Review),
"false" to register all launch entries as-is>
<Launch key = launch entry Guid registered on the pod (LaunchData.LaunchKey)
displayName = name shown in the pod's app list
exe = absolute path to the executable on the pod
args = command-line arguments; "{res}" expands to " -res W H"
when a custom resolution was chosen, otherwise to ""
workingDirectory = optional; defaults to the directory of exe
autoRestart = "true"/"false"
hostType = GameClient | LiveCamera | MissionReview | None
(only meaningful when hostTypeDialog="true"; an entry
is registered only if its role was selected) />
</Product>
To add a product, append a <Product> with one <Launch>. exe must live under
the install directory the package extracts to (currently C:\Games\...).
-->
<AppCatalog>
<Product id="7D241B1F-AB6D-4e08-9C20-12294E743D94"
name="Red Planet 4.11"
menuText="Red Planet 4.11..."
hostTypeDialog="true">
<Launch key="7D241B1F-AB6D-4e08-9C20-12294E743D94"
displayName="Red Planet 4.11"
exe="C:\Games\RP411\rpl4opt.exe"
args="-net 1501{res}"
autoRestart="true"
hostType="GameClient" />
<Launch key="57A0B3C2-D5CF-46d6-ABED-A8F4A26AB086"
displayName="Red Planet 4.11 LC"
exe="C:\Games\RP411\rpl4opt.exe"
args="-net 1501{res} -lc"
autoRestart="true"
hostType="LiveCamera" />
<Launch key="8F71D5C2-38E4-413c-8E22-88CAD08774D2"
displayName="Red Planet 4.11 MR"
exe="C:\Games\RP411\rpl4opt.exe"
args="-net 1501{res} -mr"
autoRestart="true"
hostType="MissionReview" />
</Product>
<!-- The bt411 Windows port (C:\VWE\BT411 repo; btl4.exe on the shared RP411
engine, same -net/-res/-lc/-mr command line). Deploys to C:\Games\BT411
like RP411 does to C:\Games\RP411. -->
<Product id="F4C957FD-72F7-4C5F-8971-28095007E8DF"
name="BattleTech 4.11"
menuText="BattleTech 4.11..."
hostTypeDialog="true">
<Launch key="F4C957FD-72F7-4C5F-8971-28095007E8DF"
displayName="BattleTech 4.11"
exe="C:\Games\BT411\btl4.exe"
args="-net 1501{res}"
autoRestart="true"
hostType="GameClient" />
<Launch key="D393711A-EDA0-48B2-82A0-89DF12B768AF"
displayName="BattleTech 4.11 LC"
exe="C:\Games\BT411\btl4.exe"
args="-net 1501{res} -lc"
autoRestart="true"
hostType="LiveCamera" />
<Launch key="2E9B8628-9C20-42FB-B070-E9C38D521082"
displayName="BattleTech 4.11 MR"
exe="C:\Games\BT411\btl4.exe"
args="-net 1501{res} -mr"
autoRestart="true"
hostType="MissionReview" />
</Product>
<Product id="CC8500ED-A653-45a7-BEF8-C332D30371A6"
name="BattleTech Firestorm"
menuText="BattleTech Firestorm..."
hostTypeDialog="false">
<Launch key="CC8500ED-A653-45a7-BEF8-C332D30371A6"
displayName="BattleTech Firestorm"
exe="C:\Games\MW4\launcher.exe"
args=""
autoRestart="true"
hostType="None" />
</Product>
<!-- RIOJoy — virtual-gamepad feeder for the cockpit RIO board (separate repo,
net48 framework-dependent). Its dist\RIOJoy-<ver>.zip is purpose-built for
Install Product: extracts to C:\Games (giving postinstall.bat + RIOJoy\),
and the launcher runs postinstall.bat as SYSTEM to install the ViGEmBus
driver. The console + launcher then own RIOJoy's lifecycle: the launch entry
below starts it and autoRestart keeps it alive (no logon auto-start entry).
On uninstall the launcher runs RIOJoy\pre-uninstall.bat (removes ViGEmBus +
config) and deletes C:\Games\RIOJoy. -->
<Product id="87FBC2E6-6359-4EF4-96A5-DF157823CFF6"
name="RIOJoy"
menuText="RIOJoy..."
hostTypeDialog="false">
<Launch key="FE83E212-45DF-48F9-848E-0B3CEE0692A3"
displayName="RIOJoy"
exe="C:\Games\RIOJoy\app\RioJoy.Tray.exe"
args=""
autoRestart="true"
hostType="None" />
</Product>
<!-- vPOD - virtual pod / game-client stand-in for testing the game consoles
(vPOD\ at the repo root). Speaks Munga on 1501 like a real
rpl4opt.exe/btl4.exe and reports either ApplicationID (toggled live in
its window). Deploy it to a pod exactly like a real client; the package
(vPOD\dist\vPOD.zip, built by pack.ps1) extracts to C:\Games\vPOD. -->
<Product id="0041C870-6E5E-4F3B-9782-F94F2F76F21D"
name="vPOD (Virtual Pod)"
menuText="vPOD (Virtual Pod)..."
hostTypeDialog="true">
<Launch key="0041C870-6E5E-4F3B-9782-F94F2F76F21D"
displayName="vPOD"
exe="C:\Games\vPOD\vPOD.exe"
args="-net 1501{res}"
autoRestart="true"
hostType="GameClient" />
<Launch key="EA0D4129-8950-428D-8399-E6A77D2D566A"
displayName="vPOD LC"
exe="C:\Games\vPOD\vPOD.exe"
args="-net 1501{res} -lc"
autoRestart="true"
hostType="LiveCamera" />
<Launch key="FC7CE34E-F4FE-4218-84CD-B13A6FA58E57"
displayName="vPOD MR"
exe="C:\Games\vPOD\vPOD.exe"
args="-net 1501{res} -mr"
autoRestart="true"
hostType="MissionReview" />
</Product>
</AppCatalog>