Two neural consumers in one folder now cancel out properly — the route that replaces the RenoDX add-on removes it. (#75, reported and patched by @Dewkin)
The Neural Upstream plan already declined to install renodx-dlss5.addon64, but nothing removed one an earlier run had placed, and ReShade loads every add-on it finds. So anyone who installed once with the default and again with Neural Upstream ended up with both.
They are not additive. Both detour NVSDK_NGX_D3D12_CreateFeature and EvaluateFeature, and both create NGX feature 18 on the same device. The second create is refused:
[RenoDX] feature 18 created ... 5120x1440 -> 5120x1440
[other] CORE CreateFeature(18, 5120x1440) -> 0xBAD0000B handle=0
0xBAD0000B is UnableToInitializeFeature — the result is no neural rendering at all, rather than one of the two implementations. Observed on an RTX 5070 Ti in Assassin's Creed Black Flag Resynced and The Witcher 3; deleting the file by hand fixed both.
Install now removes it as part of the Neural Upstream route, and says so. Nothing changes on any other route, and it is a no-op when the file is not there.
Two changes on top of the patch as submitted: the file is taken from the consumer directory rather than the game directory, so a 32-bit game's host64\ copy is covered by the same step; and a test asserts the step is in that plan, absent from the default one, removes the file, and is a no-op the second time.
SHA-256 of dlss5oneclick.exe: d4f50c7df053357034cabe61afd45d78241cc356fdc0fe3be366158719fb7092