CydandClaude Fable 5
3d186293bf
The provisioning text on the pod's plasma panel came up garbled — stale content bleeding through, new text overlapping at the wrong position. Root cause recovered from the dumped PD01D221 controller firmware (vrio/PlasmaNew): PlasmaWriter.ClearAll() sent ESC J, which on this controller is NOT a clear — it toggles an orientation/mode bit — so the panel never cleared and the cursor never homed. Fix: ClearAll() now sends the real commands ESC @ (clear active buffer, reset text state) + ESC L (home to 0,0), and the writer hides the cursor once at open with ESC G 0 — exactly what the game and the ROM's own demo do. Verified by running the launcher's actual byte streams through the firmware-modeled vPLASMA emulator: the old ESC J path left stale pixels (732 lit vs 404); the new path renders byte-identical to a freshly cleared panel (404 lit, cursor hidden). Version bumped 4.11.4.3 -> 4.11.4.4 across Launcher, Console, vPOD, the install/build banners, and the diff-suite version assertion. This cuts a clean release boundary that also carries the earlier field fixes (process-tree kill on Stop, Win10 install.bat icacls quoting, real system volume + pre-uninstall opt-in, and the volume menu check-mark fix). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
87 lines
4.0 KiB
XML
87 lines
4.0 KiB
XML
<Project Sdk="Microsoft.NET.Sdk">
|
|
|
|
<!--
|
|
vPOD - a virtual pod / game-client stand-in for testing the Tesla game
|
|
consoles (Red Planet and BattleTech) without real cockpit hardware.
|
|
|
|
It speaks the Munga command/control protocol as a SERVER on TCP 1501 (the
|
|
console connects to it exactly as it would a real rpl4opt.exe / btl4.exe),
|
|
emulates the pod ApplicationState machine, reassembles the streamed egg,
|
|
and shows both on a live display. Deployable to a pod machine via the
|
|
console's Manage Site -> Install Product (see dist\ + Console\RedPlanet\Apps.xml).
|
|
|
|
net40 (XP11): runs on XP SP3 through Windows 11, like the Launcher and the
|
|
Console — one flavor everywhere (Contract and SecureConfig included). The
|
|
differential tests' net48 host loads all of it fine (net40 and net48 are both
|
|
CLR4). The vendored Munga Net.dll is CLR2 pure-IL, so it loads anywhere.
|
|
WinForms comes via plain framework references: UseWindowsForms is not wired
|
|
up for net40, and all UI here is code-built (no designer).
|
|
-->
|
|
<PropertyGroup>
|
|
<OutputType>WinExe</OutputType>
|
|
<TargetFramework>net40</TargetFramework>
|
|
<LangVersion>latest</LangVersion>
|
|
<Nullable>disable</Nullable>
|
|
<ImplicitUsings>disable</ImplicitUsings>
|
|
<AssemblyName>vPOD</AssemblyName>
|
|
<RootNamespace>VPod</RootNamespace>
|
|
<GenerateAssemblyInfo>true</GenerateAssemblyInfo>
|
|
<!-- Versioned with the suite since v4.11.4.3 (was its own 1.0.0 line). -->
|
|
<AssemblyVersion>4.11.4.4</AssemblyVersion>
|
|
<Version>4.11.4.4</Version>
|
|
<Product>vPOD</Product>
|
|
</PropertyGroup>
|
|
|
|
<ItemGroup>
|
|
<!-- .NET Framework reference assemblies so this builds without a full
|
|
targeting pack installed (resolves per-TFM, covers net40 and net48) -->
|
|
<PackageReference Include="Microsoft.NETFramework.ReferenceAssemblies" Version="1.0.3" PrivateAssets="all" />
|
|
<Reference Include="System.Windows.Forms" />
|
|
<Reference Include="System.Drawing" />
|
|
</ItemGroup>
|
|
|
|
<!-- JSON for LaunchApps.json persistence + RPC arg materialization: Newtonsoft,
|
|
matching the Contract (System.Text.Json has no net40 target). -->
|
|
<ItemGroup>
|
|
<PackageReference Include="Newtonsoft.Json" Version="13.0.3" />
|
|
</ItemGroup>
|
|
|
|
<ItemGroup>
|
|
<!-- The differential suite drives the real PodManagerConnection client against
|
|
vPOD's LauncherRpcServer in-process (VPodLauncherServerTests). -->
|
|
<InternalsVisibleTo Include="TeslaConsole.DiffTests" />
|
|
</ItemGroup>
|
|
|
|
<ItemGroup>
|
|
<!-- InstallProduct zips are extracted with the Launcher's own MiniZip on BOTH
|
|
legs (ZipFile/ZipArchive are net45+, absent on net40): identical extraction
|
|
behavior to the real pod service, and the differential suite's install
|
|
round-trip exercises MiniZip against real ZipArchive-built archives. -->
|
|
<Compile Include="..\Launcher\MiniZip.cs" Link="MiniZip.cs" />
|
|
<!-- The real pod's master-volume chain (nircmd -> CoreAudio -> winmm), for
|
|
the "Actually set system volume" mode. Same linked-source sharing. -->
|
|
<Compile Include="..\Launcher\VolumeControl.cs" Link="VolumeControl.cs" />
|
|
</ItemGroup>
|
|
|
|
<ItemGroup>
|
|
<!-- The Munga wire types (messages, header, enums), vendored under the
|
|
console's lib\. Copied next to vPOD.exe so the deployable package is
|
|
self-contained. -->
|
|
<Reference Include="Munga Net">
|
|
<HintPath>..\Console\lib\Munga Net.dll</HintPath>
|
|
<Private>true</Private>
|
|
</Reference>
|
|
</ItemGroup>
|
|
|
|
<ItemGroup>
|
|
<!-- The shared console<->launcher wire libraries, so vPOD can also stand in
|
|
for the pod's TeslaLauncher service (Site Management / Install Product):
|
|
PodRpc framing + ILauncherService wire types, and the SecureConfig
|
|
provisioning protocol + OFB crypto-stream handshake. vPOD implements the
|
|
SERVER side of the existing contract only - no new RPCs. -->
|
|
<ProjectReference Include="..\Contract\Tesla.Contract.csproj" />
|
|
<ProjectReference Include="..\SecureConfig\Tesla.SecureConfig.csproj" />
|
|
</ItemGroup>
|
|
|
|
</Project>
|