if you put dgvoodoo in its not even creating a d3d8 ddi, its on the dx12 ddi.

Squall Leonhart wrote on 2025-05-18, 16:57:

if you put dgvoodoo in its not even creating a d3d8 ddi, its on the dx12 ddi.

I get a stack overflow error on using dgVoodoo2 here.

Irrelevant

Find the broken software on your computer that is preventing Direct3D from working.

PS: DX samples can only be run from the SDK install path due to hard path definitions for materials, your zip is unusable.

Squall Leonhart wrote on 2025-05-18, 17:29:

PS: DX samples can only be run from the SDK install path due to hard path definitions for materials, your zip is unusable.

Ah, so that explains why most of these don't work for me either.
Volumetexture and text3d are working though and running in dx8 mode according to Afterburner.

Seems like a lack of installation. I think I installed it in the exact same place on my last Windows installation, so I assumed a direct extraction would work.
However it is funny how sharangad and I have the exact same problem, and, did the exact same mistake 😂.

Well then I can continue testing any D3D8 app now with dgVoodoo2 until I found out where the issue was emerging from

BEEN_Nath_58 wrote on 2025-05-17, 06:16:

DX8a SDK demos hang and crash even before dgVoodoo2 initialises. Even viewer mentions on nvwgf2um.dll. I had a few tests here: Direct3D8 Nvidia regression? (+ some DOS rant)

dgVoodoo does not touch D3D8 so it must be some other error, probably at driver level. What about an earlier driver version?
As far as I know, starting with Vista (the WDDM model) D3D8 driver calls are (mostly) mapped to the same DDI as D3D9, so "removing D3D8 support" alone without removing D3D9 wouldn't be easy on driver side. Btw, DirectX DDI is not an API separated by DX versions but a big (ever growing) common function table that the driver should implement and all DX versions make their calls into it.

Dege wrote on 2025-05-18, 19:20:

BEEN_Nath_58 wrote on 2025-05-17, 06:16:

DX8a SDK demos hang and crash even before dgVoodoo2 initialises. Even viewer mentions on nvwgf2um.dll. I had a few tests here: Direct3D8 Nvidia regression? (+ some DOS rant)

dgVoodoo does not touch D3D8 so it must be some other error, probably at driver level. What about an earlier driver version?
As far as I know, starting with Vista (the WDDM model) D3D8 driver calls are (mostly) mapped to the same DDI as D3D9, so "removing D3D8 support" alone without removing D3D9 wouldn't be easy on driver side. Btw, DirectX DDI is not an API separated by DX versions but a big (ever growing) common function table that the driver should implement and all DX versions make their calls into it.

Thanks for the reply, we latee found out this specific issue is rather related to installation directory.

For the other main issue, it's like something just disabled HAL. Can't be sure how that's possible as you said, it's all connected to d3d9 which is working fine on it's own. Just d3d8 in the middle is the problem.

To mention, the Reference API is still available, but I can't see HEL either (if it existed)

there is no "d3d8 in the middle" the Runtimes of 8 and 9 are both fully implemented but have a lot of shared code (hence the unfortunately breakage of freelancer spot lights), both translate at the ddi for usage with d3d10+ hardware.

Squall Leonhart wrote on 2025-05-18, 23:15:

there is no "d3d8 in the middle"

I meant it as a contrast...

i just post this link https://www.bbc.com/future/article/20250516-t … ndows-computers this is somehow related to the topic.

You try search "d3d8.dll" in registry? As i say. No result must be. Something might be redirecting the call.