I wanted to run the original Space Marine with access to DX11, just to use ReShade with R.E.S.T., and get access some of the better shaders that don't compile with DX9. Well, after dropping in the appropriate DLLs, dgVoodooCPL.exe, the CONF, and then starting up the game EXE, the opening company logos all go by, then, as soon as it's going to render the pre-menu hold screen with Titus standing behind the logo, it crashes -- y'know, at the very moment the first time 3D objects are meant to get rendered. As it crashes, it generates a BugSplat report, with a prompt, and all that. So, I've got both the LOG from running dgVoodoo 2 with the debug layer, and the BugSplat DMP file.

When I remove all of the wrapper stuff, the game runs great. And to be clear, I've used dgVoodoo 2 on a few other games, so far, without much trouble. I even got it to run on top of Fallout 1-in-2, which allowed ReShade to work without crashing (you have to use the SFall DDraw.dl, instead of the dgVoodoo one). The speed feels a bit choppy, despite registering at like, 180 fps. It makes no sense.

Anyway, back to WH40kSM. What I've gleaned from each of the debug files:

The DMP file seems to indicate a memory access error:

FAILURE_BUCKET_ID: BAD_INSTRUCTION_PTR_INVALID_POINTER_READ_c0000005_SpaceMarine.exe!Unknown

The LOG file is a bit more peculiar. A lot of repeats of this:

[dgVoodoo] WARNING: Direct3DDevice9 (0F082ED0): Draw*/Clear: Bounds of the current viewport is invalid for the current rendertarget.

Then, right when it crashes, these are the next bits:

Error 20 (this feature has not been implemented yet) in function AVolute::GetProductInfoT::<lambda_c1c69609f385576658f8def701163fcd>::operator ()

(repeated a few dozen times, with the following two lines together, toward the end)

2025-04-24T11:25:36.102 OverCloc bf54 FrameViewTasks.cpp:36 ExecuteAsync SetProcessId processId 0
2025-04-24T11:25:36.102 OverCloc TASK FrameViewTasks.cpp:43 Finish SetProcessId

With that OverCloc in there, does this doubly indicate a memory access issue? Whatever the case, I've attached both files (with the DMP file converted to a TXT). I did try a lot of different settings for the dgVoodoo 2 Control Panel while troubleshooting, but the attached reports are pretty much default, with the only change being the VRAM, which I set at 4096 MB (I tried it as high as 12000). I actually spent hours going over things I found in the debug files, putting snippets in the search engine, etc. It got me nowhere.

I hope that this helps make the wonderful tool you've created even sturdier and more robust. Thanks, by the way!

Oh, and the specs of my rig, just in case it helps:

OS: Windows 10 Pro (Build 19045 - latest)
MoBo: RoG Maximus XI Hero
CPU: Intel Core i9-9900k
GPU: NVIDIA GeForce RTX 3090 Ti (stopped at driver 566.36 for stability)
RAM: 32 GB
No configured overclocking.