faisalkindi/DLSS5oneclick v0.11.23

on GitHub

Fixed

• Red Dead Redemption 2 still read as DirectX 9 after v0.11.21 and v0.11.22 (#53). Its import table, supplied by the reporter, explains why: it statically imports Direct3DCreate9Ex — a real Direct3D 9 entry point, so the debug-marker rule did not apply — and imports no dxgi.dll at all, so the DXGI rule did not either.

  What does name the renderer is what sits beside it: ffx_fsr2_api_dx12_x64.dll, ffx_fsr2_api_vk_x64.dll and nvlowlatencyvk.dll. AMD ships one FidelityFX FSR2 backend per graphics API and names the API in the file; NVIDIA's Reflex library for Vulkan is nvlowlatencyvk.dll. A game carrying those is a D3D12/Vulkan renderer creating its device at runtime, whatever it does with d3d9.dll.

  d3d9.dll is now taken as the renderer only when the executable carries nothing that implies something newer.

Thanks to @Roowdyx15 for running --imports and posting the table — that is what made this solvable without owning the game.