DLSS5-Feeder 1.18.0 beta 1 was released on September 29, 2026, featuring a new 64-bit auxiliary mode that allows running NGX outside the game process. The change targets cases where the process itself fails to initialize DLSS, with the project's already validated example being Bloodborne on shadPS4.
The update is experimental and community-driven. It does not turn shadPS4 into an official NVIDIA DLSS 5 implementation, but creates a new route to feed Neural Rendering in scenarios previously blocked by the emulator process.

Bloodborne running via shadPS4. Image: shadPS4 project.
DLSS5-Feeder 1.18.0 gets 64-bit helper
Until now, the external helper was especially important for 32-bit games. Version 1.18.0-beta.1 adds the file dlss5-feed-helper.addon64. With it, a 64-bit game or emulator can deliver its frames to the dlss5-feed-host64.exe, while NGX runs in the auxiliary process.
According to the official notes, Bloodborne on shadPS4 is the known case that motivated the change. Inside the emulator, NVAPI was unable to create the CUDA module required by DLSS. On the same computer, however, the host64 process managed to execute the step.

Screenshot of Bloodborne in Central Yharnam. Image: PlayStation Blast.
Bloodborne on shadPS4 has already been validated
The developer reports that the 64-bit helper ran on Bloodborne on shadPS4 on a GeForce RTX 5080. The host test also completed 300 out of 300 evaluations on driver 617.14 with an RTX 5090 and returned FeatureInitResult: Success.
This does not mean universal compatibility. The release itself marks the Direct3D 10, Direct3D 11, and OpenGL routes of the new helper as untested in-game. Additionally, Direct3D 12 is not part of this route. The mode supports Direct3D 10/11, OpenGL, and Vulkan, and works in DLAA at native size.
Therefore, the new feature is technically relevant mainly for emulators and games where NGX fails within the main process. The log has also become more useful: the Feeder now logs SuperSampling.FeatureInitResult and can differentiate a process failure from a GPU or driver issue.

Bloodborne running via shadPS4 on PC. Image: GameDB.
DLSS5-Feeder 1.18.0 also fixes 32-bit DXVK
The beta also brings a fix for 32-bit Vulkan games via DXVK that load the d3d9.dll twice. Fallout: New Vegas via Mod Organizer 2 appears as an example in the notes. In this situation, ReShade could unload and reload its layer, while the old add-on remained stuck to the first module.
Now the Feeder removes the hooks from the vulkan-1.dll old one, releases the add-on, and allows the new ReShade instance to load it again. The loader test cited by the project failed five out of 13 checks with version 1.17.0 and passed all 13 with this beta.
RTX 20, 30, and 40 still require a modified model
There is an important limitation. The project states that the signed DLL nvngx_dlssnr.dll 310.8.0 and the modified build 310.8.Lecram used by the installer create the neural feature directly only on RTX 50 GPUs. On RTX 20, 30, and 40, DLSS may start, but Neural Rendering does not kick in without a GPU-compatible modified DLL.
Therefore, the release should not be interpreted as official NVIDIA support for DLSS 5 on previous generations. DLSS5-Feeder remains a community and experimental tool, and the project itself warns against fake copies: the official releases page is the designated source for genuine files.
Sources: DLSS5-Feeder 1.18.0-beta.1 and official DLSS5-Feeder repository.
Pingback: DLSS 5 Autopilot 2.0.8 melhora diagnóstico