Regression on the Vulkan interop path between 0.1.1.5 and 0.2.0-patch1 (No Man's Sky crashes on load)

[rakanki911]

Reporting this on behalf of a user of DLSS 5 Swapper, which pins your releases by URL and SHA-256. Their bisection is clean and the two builds are the only variable.

What changed for them

DLSS 5 Swapper 2.2.1 → OptiScaler DLSSNR 0.1.1.5-dlssnr	works, hours of play
DLSS 5 Swapper 2.2.2+ → OptiScaler DLSSNR 0.2.0-patch1	reaches the main menu, then crashes when a save is loaded

Nothing else differs. They repeated it both directions: reinstalled 0.2.0-patch1 on the newer app (crash), then went back to the older app without even restoring the folder first (works). Driver 616.56, RTX card, game is No Man's Sky on Vulkan.

What their log shows

OptiScaler.log, in the last seconds before it stops:

[W] IFeature_VkwDx12::ProcessVulkanTextures Failed to capture and replay
    command buffer state or state is empty

It appears twice, in the Vulkan→D3D12 texture path, and the log ends shortly after with no further output. The NGX side looks healthy right up to it — NVSDK_NGX_VULKAN_EvaluateFeature returning 1 repeatedly.

Also present earlier, in case they are related:

[E] DxgiFactoryHooks::HookToFactory Failed to hook IDXGIFactory: 10DD
[E] StreamlineHooks::unhookDlssg Failed to unhook DLSSG: 1E7

Where the logs are

Both OptiScaler.log and ReShade.log are attached to the downstream report, with the reporter's own account of the bisection:
rakanki911/DLSS5-Swapper#238

Happy to gather anything else that would help — the reporter is responsive and has both builds installed side by side, so an A/B with extra logging is straightforward for them.

Thank you for the work on this fork; it is the OptiScaler build DLSS 5 Swapper ships.