v0.10.3

The file attached to this release is wrong. It was tagged before the version bump was applied, so the exe here is a 0.10.2 build: installing it leaves you on 0.10.2 and the update bar comes back. Use v0.10.4 instead, which carries the right binary and makes the updater refuse a mis-tagged asset. (#26)

0.10.3

Diagnose no longer blames the driver when the driver is fine. 0.10.2 ended every NVSDK_NGX_*_Init -> 0xBAD00001 finding with "update the NVIDIA driver". On all three machines that have reported this the driver is current and NGX Core is installed (#6 RTX 5080, #16 RTX 5090, #25 RTX 4070 — same driver 616.56, same DriverStore folder as a machine here where the identical files initialise NGX successfully).

Diagnose now checks NGX Core and the driver version first. When they are fine it says what the evidence supports instead: NGX is refusing the Feeder's private in-process D3D12 device; the same chain initialises NGX without trouble in the 32-bit host64 helper (a separate process) and on the native path where the game owns the device. The suggested step is a game that ships its own DLSS — that path opens no private device — and then a report to jlrouzies-fr/DLSS5-Feeder, which owns that code. When NGX Core really is missing or the driver is older than 616.56, the old advice still appears.

SHA-256 dlss5oneclick.exe: 6f8699926e13e101df15e26b3af71c0e08e633ad91b996f60b9ba039bbc96fb0