SaaS Metrics
GitHub Issue
NVSDK_NGX_D3D12_Init -> 0xBAD00001 on three machines with NGX Core installed and driver 616.56 (in-process session; same files succeed in host64)
**Summary:** on three different machines, all with a healthy NGX runtime, `NVSDK_NGX_D3D12_Init` returns `0xBAD00001` (FeatureNotSupported) when the feeder opens its **in-process private D3D12 session** in a 64-bit game. The same add-on files, the same DLSS 5 build and the same driver initialise NGX successfully when the init happens in the separate `host64` helper process. Reported through my installer (DLSS5oneclick), so the file layout is identical across all four cases below.
### Failing — in-process private D3D12 session
**A. Mafia: Definitive Edition, RTX 5080, driver 616.56** ([issue](https://github.com/faisalkindi/DLSS5oneclick/issues/6))
```
12:09:07.694 dlss5-feed 0.12.0 (built Sep 2 2026 17:38:39) attached.
12:09:07.697 [feed] DLSS 5 add-on: renodx-dlss5.addon64 v4.7 (file version 0.2026.828.517) -- v4.7+ engine
12:09:09.474 [feed] adapter: NVIDIA GeForce RTX 5080 vram=15977 MB
12:09:09.561 [feed] NVSDK_NGX_D3D12_Init -> 0xBAD00001 (FeatureNotSupported)
12:09:09.561 [feed] NGX would not initialise on this device/driver
```
Repeats identically on every Re-enable. ReShade 6.8 loaded, `DLSS 5 Feed 0.12.0` and `DLSS 5 Neural Rendering v0.2026.828.517` both registered, `DLSS5_MV_PROVIDER=3 -> Lumenite_Kernel (enabled)`, provider matches the shader.
**B. Mortal Kombat 11, RTX 5090, driver 616.56** ([issue](https://github.com/faisalkindi/DLSS5oneclick/issues/16))
```
12:40:06.756 [feed] NVSDK_NGX_D3D12_Init -> 0xBAD00001 (FeatureNotSupported)
12:40:06.756 stop...
View Raw Thread
Developer & User Discourse
jlrouzies-fr • Sep 3, 2026
This is an unusually good report — four cases, the working one included, and the ruling-out already done. It let me compare the two call sites properly instead of guessing, so here is what that comparison actually shows, and then a build that answers the remaining question in one run rather than three.
## The two call sites, side by side
| | in-process (fails) | `host64` helper (works) |
|---|---|---|
| App id / project id / engine type / version | identical | identical |
| `InFeatureInfo` | `nullptr` | `nullptr` |
| `InApplicationDataPath` | the add-on's folder = **the game directory** | **`host64\`** |
| process exe dir + working dir | the game's | `host64\` |
| adapter | the **game's**, taken off its D3D11 device | DXGI's **default** |
Exactly one argument to `NVSDK_NGX_D3D12_Init` differs: the application data path. NGX writes its own logs into that folder, and for a game under Program Files it is not writable without elevation the game does not have. Nothing logged that path, n...
## The two call sites, side by side
| | in-process (fails) | `host64` helper (works) |
|---|---|---|
| App id / project id / engine type / version | identical | identical |
| `InFeatureInfo` | `nullptr` | `nullptr` |
| `InApplicationDataPath` | the add-on's folder = **the game directory** | **`host64\`** |
| process exe dir + working dir | the game's | `host64\` |
| adapter | the **game's**, taken off its D3D11 device | DXGI's **default** |
Exactly one argument to `NVSDK_NGX_D3D12_Init` differs: the application data path. NGX writes its own logs into that folder, and for a game under Program Files it is not writable without elevation the game does not have. Nothing logged that path, n...
mrtawsiti3 • Sep 3, 2026
Hi, B here
tried with v0.13.0-beta.1 and still getting same diagnostics error
[dlss5-feed.log](https://github.com/user-attachments/files/31803968/dlss5-feed.log)
tried with v0.13.0-beta.1 and still getting same diagnostics error
[dlss5-feed.log](https://github.com/user-attachments/files/31803968/dlss5-feed.log)
faisalkindi • Sep 3, 2026
Case B's 0.13.0-beta.1 log is in the thread above; here is what it settles and what it leaves.
```
[feed] adapter: NVIDIA GeForce RTX 5090 vram=32187 MB
[feed] private device adapter: NVIDIA GeForce RTX 5090 LUID 00000000:06866936
[feed] NGX init attempt 1/2: data path H:\Games\Mortal Kombat 11\Binaries\Retail\ (writable)
[feed] NGX init attempt 1 -> 0xBAD00001 (FeatureNotSupported)
[feed] NGX init attempt 2/2: data path C:\Users\mateo\AppData\Local\DLSS5-Feeder\ngx\ (writable)
[feed] NGX init attempt 2 -> 0xBAD00001 (FeatureNotSupported)
[feed] NGX Core: Installed=1 FullPath=C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_a3944b54ff18b284
```
* **The application data path is not it, at least for B.** Both candidates were writable, one of them the very folder the helper uses, and both returned the same code. The game is on `H:\`, not under `Program Files`, so the elevation angle does not apply here either.
* **One adapter, and it is the right one.** The game's ada...
```
[feed] adapter: NVIDIA GeForce RTX 5090 vram=32187 MB
[feed] private device adapter: NVIDIA GeForce RTX 5090 LUID 00000000:06866936
[feed] NGX init attempt 1/2: data path H:\Games\Mortal Kombat 11\Binaries\Retail\ (writable)
[feed] NGX init attempt 1 -> 0xBAD00001 (FeatureNotSupported)
[feed] NGX init attempt 2/2: data path C:\Users\mateo\AppData\Local\DLSS5-Feeder\ngx\ (writable)
[feed] NGX init attempt 2 -> 0xBAD00001 (FeatureNotSupported)
[feed] NGX Core: Installed=1 FullPath=C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_a3944b54ff18b284
```
* **The application data path is not it, at least for B.** Both candidates were writable, one of them the very folder the helper uses, and both returned the same code. The game is on `H:\`, not under `Program Files`, so the elevation angle does not apply here either.
* **One adapter, and it is the right one.** The game's ada...
faisalkindi • Sep 3, 2026
Two data points from case A (Mafia: Definitive Edition, RTX 5080, driver 616.56), while he re-runs the beta correctly.
He posted a log after "testing 0.13", but it is the previous build:
```
21:51:35.464 dlss5-feed 0.12.1-beta.2 (built Sep 3 2026 19:08:39) attached.
21:51:37.359 [feed] adapter: NVIDIA GeForce RTX 5080 vram=15977 MB
21:51:37.456 [feed] NVSDK_NGX_D3D12_Init -> 0xBAD00001 (FeatureNotSupported)
```
The cause is a packaging assumption, and it may be worth a line in the release notes: he copied `host64\` out of the zip into the game folder and left `dlss5-feed.addon64` alone, because that is where he expected the new files to live. A 64-bit game never loads anything from `host64\`, so the beta's add-on was never in play. I have told him to replace the root `dlss5-feed.addon64` and confirm the first log line reads `0.13.0-beta.1`.
Worth having anyway, from that run:
* **No `D3D12\` folder next to `mafiadefinitiveedition.exe`.** So the Agility SDK angle I raised does...
He posted a log after "testing 0.13", but it is the previous build:
```
21:51:35.464 dlss5-feed 0.12.1-beta.2 (built Sep 3 2026 19:08:39) attached.
21:51:37.359 [feed] adapter: NVIDIA GeForce RTX 5080 vram=15977 MB
21:51:37.456 [feed] NVSDK_NGX_D3D12_Init -> 0xBAD00001 (FeatureNotSupported)
```
The cause is a packaging assumption, and it may be worth a line in the release notes: he copied `host64\` out of the zip into the game folder and left `dlss5-feed.addon64` alone, because that is where he expected the new files to live. A 64-bit game never loads anything from `host64\`, so the beta's add-on was never in play. I have told him to replace the root `dlss5-feed.addon64` and confirm the first log line reads `0.13.0-beta.1`.
Worth having anyway, from that run:
* **No `D3D12\` folder next to `mafiadefinitiveedition.exe`.** So the Agility SDK angle I raised does...
1. **The same machine, same file set, native-DLSS path: works.** He installed into *Stellar Blade* (ships its own DLSS, so the add-on hooks the game's device and no private session is opened) and neural rendering runs with no errors, before/after screenshots posted at https://github.com/faisalkindi/DLSS5oneclick/issues/6#issuecomment. So NGX, the driver, the `renodx-dlss5.addon64` 4.7 build and `nvngx_dlssnr.dll 310.8.SF-v2` are all healthy on that PC.
2. **A different installer reproduces the failure in the same game.** He tried rakanki911's DLSS5 Swapper on Mafia 1 and got the identical NGX error, so the file layout my installer writes is not the variable either.
That leaves the private in-process D3D12 device as the only thing the failing cases have in common, on three machines whose NGX is demonstrably working for the native path.
If a debug build or a specific `dl...