Work advanced the application startup path while a separate D7VK investigation tested a practical Vulkan route for the original executable. The native integration session crossed into October 13; its confirmed live menu and gameplay results are recorded in the following day's summary.
Native application integration
The execution map and host notes followed startup through heap and allocation state, application initialization, window services, and rendering dependencies. Static application maps guided the work, but were kept separate from functions actually executed by the native host.
The aim was to provide the services and initialization effects the original code expected, while stopping visibly at unsupported boundaries.
D7VK evaluation and wrapper work
An authored graphics fixture exercised D7VK's Vulkan path on the development hardware. That made it a strong adaptation candidate, with further source integration and validation still required for the native host.
A separate, isolated original-game profile explored the wrapper route. Recorded tests distinguished display-mode failures on a non-interactive desktop from successful interactive-desktop behavior, then continued into menu and gameplay testing. This route kept the original executable running and did not count as native recompilation progress.
What came next
The native host needed complete lifecycle and live scene evidence. The wrapper needed broader mission-transition and configuration testing, along with a repeatable setup suitable for eventual users.
The source repository is currently private; GitHub links require collaborator access.