Two new Diagnose findings for "everything looks right but nothing is hooked"
Baldur's Gate 3 ships two executables — bg3.exe (Vulkan) and bg3_dx11.exe — and a reporter had installed for one and played the other (#33). ReShade loaded, the DLSS 5 add-on registered, and no DLSS call was ever intercepted, with nothing in the output explaining why.
1. A Direct3D 11 game with its own DLSS and no bridge is now named as such.
The add-on hooks NVSDK_NGX_D3D12_*. A D3D11 game calls the D3D11 entry points, which it can never see — that is exactly what the DX11 bridge exists for. Diagnose used to blame the game's DLSS setting; it now says the bridge is missing and to re-run Install.
2. Diagnose reads which exe ReShade actually loaded into.
ReShade's first log line names it. When that differs from the exe the install was made for, you now get:
[warn] ReShade loaded into bg3_dx11.exe, but this install was set up for bg3.exe. Those are
different executables, and the install is tuned to the one you picked (the DX11 bridge in
particular). Point the tool at bg3_dx11.exe and run Install again.
This catches any game with a launcher plus a game exe, or separate Vulkan and DirectX builds.