I've noticed that in Documents\My Games\Fallout3\RendererInfo.txt the game reports d3d9 driver name as a dll (nvldumd.dll for native Nvidia, nvd3dum.dll for DXVK and nv4_disp.dll for Intel Bypass), but for dgVoodoo2 it reports "dgVoodoo DirectX Wrapper" instead. It also reports my actual GPU name instead of GeForce 9800 GT that I selected in the dgVoodooCpl.

Sorry. But this game needed ENB. Because ENBoost and CTD and Memory patch. You NEED it anyway, whether you want it or not. Like Skyrim LE. There is no point for the wrapper author to support these games.

mitradis wrote on 2025-05-31, 19:41:

Sorry. But this game needed ENB. Because ENBoost and CTD and Memory patch. You NEED it anyway, whether you want it or not. Like Skyrim LE. There is no point for the wrapper author to support these games.

Not my case - it's not a memory crash and I don't use any texture mods.
The game works just fine natively, with DXVK, or when I pair d3d9.dll from Intel Bypass Package (tricks the game into believing it's running on a GeForce 7900 GS) with dgVoodoo2 (rename d3d9.dll to swiftshader-d3d9.dll and Intel Bypass will automatically load it instead of a system d3d9.dll).
I believe it has something to do with GPU detection, something dgVoodoo2 is not reporting correctly.
I prefer to use dgVoodoo2 so I can force DXGI flip model for windowed mode. I could've used DXVK + Nvidia's DXGI swapchain instead, but causes an annoying delay in VATS targeting, and I use VATS a lot.

Seems to me the game is trying to read the GPU vendor as AMD or Nvidia. Unfortunately dgVoodoo2 is only submitting the default name, I think I have seen it in other games.

Nvldumd is probably the system D3D9 driver, while nvd3dum.dll is the DX10+ driver (that also includes Vulkan). Nv4_disp.dll is the old 32bit Nvidia driver for D3D9.