Verify standalone packages and Windows Vulkan rendering under isolated Wine

This commit is contained in:
UnixNight committed 2026-10-23 17:42:05 -04:00
1 parent 008c0e16da
commit 670adb4795
10 files changed
+71 -13

No files matched your search

+23
View File
@@ -36,3 +36,26 @@ Those frames are also unusable. Failures must not be treated as original behavio
No native Windows installation/VM or Windows 98 image was available in the initial
environment/tool inventory. A local reference machine remains necessary if Wine
cannot render correctly. Native Windows port execution remains separately untested.
## Preliminary Windows-port smoke under Wine64
`python3 tools/recon/reference_capture.py --port-smoke --seconds 24 --debug`
mounts only the self-contained Windows package in a fresh filesystem/network
namespace, with its own win64 prefix. The runtime, assets, shaders and scene data
all come from that package; the source, SDK and Original directory are not mounted.
The new port calls Vulkan directly and does not use Wine's legacy D3D backend.
The Windows x64 .NET10.0.13 executable decoded LV1B, loaded original lab/character
resources and rendered two offscreen frames through lavapipe, exiting0. This test
disabled Vulkan validation and **does not** establish Windows-driver validation,
SDL window/audio/input functionality or native Windows compatibility.
At fixed morph time0.05, its PPM GPU readback is byte-identical to the native Linux
package readback (SHA-256 `c30bcbc95d00ce104b146cc46c84e9a9d50849bf0b0bf33c027a402bb46e47c4`).
Both use the same software Vulkan driver. This establishes consistency between
those two package executions, not fidelity to the original game.
An initial harness configuration disabled mscoree for the legacy game and thereby
prevented Wine from loading the port's IL-only System.Runtime.dll. Port mode now
uses Wine's built-in mscoree, correcting the test environment; no app workaround
or Mono runtime is required. Logs/readback are in artifacts/windows-smoke/.