is this system using an intel cpu with an igp using the iris and arc xe drivers?

Theres a bug in those where older d3d api's do not see a valid device on subsequent runs.

Squall Leonhart wrote on 2024-11-02, 06:24:

is this system using an intel cpu with an igp using the iris and arc xe drivers?

Theres a bug in those where older d3d api's do not see a valid device on subsequent runs.

No, a desktop Ryzen 7 1700x with 2070 GPU. It was working fine the first time I set it up, following the instructions to copy the DLLs to the DS game directory. Everything went well, I finally tweaked things to my liking. I did not even turn off my PC for the night. Then the next day it stopped working, and DG would not launch. The static resolutions just failed to show up in DX settings tab, and with that DS Video config did not detect any graphics hardware.

Subsequent to this post, I tried it on my laptop which has integrated Intel GPU and discrete Nvidia. In this case, if I chose Nvidia GPU, the static resolutions do not show up and DS would not launch. If I chose the Intel integrated GPU, then the static resolutions would show up and DS would launch and dgvoodoo worked as intended. Even if I chose in Windows system settings to force DG to use Nvidia GPU as well as in Nvidia's GEForce Experience to force Nvidia, still the same. But my desktop only has 1 GPU, and it was working initially, so very puzzling.

Squall Leonhart wrote on 2024-11-02, 06:24:

is this system using an intel cpu with an igp using the iris and arc xe drivers?

Theres a bug in those where older d3d api's do not see a valid device on subsequent runs.

This isn't a bug, it is probably the DWM not detecting the 16-bit modes necessary for the game. Or it is seeing too many video modes.

Also for old games, it will directly show the GPU name or Primary Display Driver, so in this case its using the Nvidia

sc999999 wrote on 2024-11-01, 11:43:

When I removed the dgvoodoo (deleted the provided DLLs), then the graphics card options return (Picture 3) and I can run the gam […]
Show full quote

When I removed the dgvoodoo (deleted the provided DLLs), then the graphics card options return (Picture 3) and I can run the game normally but of course without the benefit of having dgvoodoo.

It worked the night before, and then all of a sudden, it stopped working the next day. Reboot, updated video drivers, checked if antivirus has quarantined anything (no it didn't), still doesn't work.

Out of curiosity, I installed everything on virtual machine running windows and dgvoodoo works (static resolutions are available) and DS runs with dgvoodoo working as intended.

Thanks in advance to anyone who may have an idea.

Try running as admin, try enabling the 16 bit colour mode in the Properties tab and/or enable a WinXP+ compatibility mode with Run as admin. Generally this is enough.

Edit: I am not sure if the game is really seeing dgVoodoo2. It should create a device by the name dgVoodoo and not Nvidia.

sc999999 wrote on 2024-11-01, 11:43:

dgvoodoo for Dungeon Siege, working initially then suddenly stopped working […]
Show full quote

dgvoodoo for Dungeon Siege, working initially then suddenly stopped working

Wondering if anyone has experienced the same issue. Using DS to play Ultima 5 Lazarus, got dgvoodoo working for 1 day. Then the next day, it stopped working. First picture shows the error when launching DS.

Then I ran dgvoodoo config again, and noticed that the static resolution options under DirectX tab are no longer available . That is, only 2x, 4x, etc. are shown as options, not the fixed resolutions like 2560x1440, etc.. When running the DS video config, the graphics card options are blank. Picture 2.

When I removed the dgvoodoo (deleted the provided DLLs), then the graphics card options return (Picture 3) and I can run the game normally but of course without the benefit of having dgvoodoo.

It worked the night before, and then all of a sudden, it stopped working the next day. Reboot, updated video drivers, checked if antivirus has quarantined anything (no it didn't), still doesn't work.

Out of curiosity, I installed everything on virtual machine running windows and dgvoodoo works (static resolutions are available) and DS runs with dgvoodoo working as intended.

Thanks in advance to anyone who may have an idea.

Could you plz attach a log from the _dbg version of dgVoodoo, to see if DDraw can enumerate any device at all?
(By the symptoms, you might have set a GPU or display output ordinal in the dgVoodoo config that does not exist on the machine you want to run it on.)
If it turns out not to be a regression bug then I'll move the post into a separate topic.

Debug view log file attached. Thanks.

Dege wrote on 2024-11-04, 08:05:

Could you plz attach a log from the _dbg version of dgVoodoo, to see if DDraw can enumerate any device at all? (By the symptoms, […]
Show full quote

sc999999 wrote on 2024-11-01, 11:43:

dgvoodoo for Dungeon Siege, working initially then suddenly stopped working […]
Show full quote

dgvoodoo for Dungeon Siege, working initially then suddenly stopped working

Wondering if anyone has experienced the same issue. Using DS to play Ultima 5 Lazarus, got dgvoodoo working for 1 day. Then the next day, it stopped working. First picture shows the error when launching DS.

Then I ran dgvoodoo config again, and noticed that the static resolution options under DirectX tab are no longer available . That is, only 2x, 4x, etc. are shown as options, not the fixed resolutions like 2560x1440, etc.. When running the DS video config, the graphics card options are blank. Picture 2.

When I removed the dgvoodoo (deleted the provided DLLs), then the graphics card options return (Picture 3) and I can run the game normally but of course without the benefit of having dgvoodoo.

It worked the night before, and then all of a sudden, it stopped working the next day. Reboot, updated video drivers, checked if antivirus has quarantined anything (no it didn't), still doesn't work.

Out of curiosity, I installed everything on virtual machine running windows and dgvoodoo works (static resolutions are available) and DS runs with dgvoodoo working as intended.

Thanks in advance to anyone who may have an idea.

Could you plz attach a log from the _dbg version of dgVoodoo, to see if DDraw can enumerate any device at all?
(By the symptoms, you might have set a GPU or display output ordinal in the dgVoodoo config that does not exist on the machine you want to run it on.)
If it turns out not to be a regression bug then I'll move the post into a separate topic.

BEEN_Nath_58 wrote on 2024-11-02, 15:17:

This isn't a bug, it is probably the DWM not detecting the 16-bit modes necessary for the game. Or it is seeing too many video m […]
Show full quote

Squall Leonhart wrote on 2024-11-02, 06:24:

is this system using an intel cpu with an igp using the iris and arc xe drivers?

Theres a bug in those where older d3d api's do not see a valid device on subsequent runs.

This isn't a bug, it is probably the DWM not detecting the 16-bit modes necessary for the game. Or it is seeing too many video modes.

Also for old games, it will directly show the GPU name or Primary Display Driver, so in this case its using the Nvidia

sc999999 wrote on 2024-11-01, 11:43:

When I removed the dgvoodoo (deleted the provided DLLs), then the graphics card options return (Picture 3) and I can run the gam […]
Show full quote

When I removed the dgvoodoo (deleted the provided DLLs), then the graphics card options return (Picture 3) and I can run the game normally but of course without the benefit of having dgvoodoo.

It worked the night before, and then all of a sudden, it stopped working the next day. Reboot, updated video drivers, checked if antivirus has quarantined anything (no it didn't), still doesn't work.

Out of curiosity, I installed everything on virtual machine running windows and dgvoodoo works (static resolutions are available) and DS runs with dgvoodoo working as intended.

Thanks in advance to anyone who may have an idea.

Try running as admin, try enabling the 16 bit colour mode in the Properties tab and/or enable a WinXP+ compatibility mode with Run as admin. Generally this is enough.

Edit: I am not sure if the game is really seeing dgVoodoo2. It should create a device by the name dgVoodoo and not Nvidia.

Thanks for your suggestion. Changed the compatibility settings as suggested, still no go. Yes, the device name if dgvoodoo is working properly should be a dgvoodoo emulated device, that I understand. What my screenshot indicated is that there is no devices at all when the dgvoodoo is installed, and thus DG won't launch. When dgvoodoo is removed, then my original display hardware reappears. In a windows virtual machine client, everything works fine, the dgvoodoo emulated device shows up and DG launches.

The puzzling part is that it was working when I was setting things up, tweaking the settings, and I must have exited and relaunched DS a dozen times. Then I turned in for the night. The next day, it doesn't work anymore. Just puzzling, so I wanted to share this here.

sc999999 wrote on 2024-11-05, 14:47:

BEEN_Nath_58 wrote on 2024-11-02, 15:17:

This isn't a bug, it is probably the DWM not detecting the 16-bit modes necessary for the game. Or it is seeing too many video m […]
Show full quote

Squall Leonhart wrote on 2024-11-02, 06:24:

is this system using an intel cpu with an igp using the iris and arc xe drivers?

Theres a bug in those where older d3d api's do not see a valid device on subsequent runs.

This isn't a bug, it is probably the DWM not detecting the 16-bit modes necessary for the game. Or it is seeing too many video modes.

Also for old games, it will directly show the GPU name or Primary Display Driver, so in this case its using the Nvidia

sc999999 wrote on 2024-11-01, 11:43:

When I removed the dgvoodoo (deleted the provided DLLs), then the graphics card options return (Picture 3) and I can run the gam […]
Show full quote

When I removed the dgvoodoo (deleted the provided DLLs), then the graphics card options return (Picture 3) and I can run the game normally but of course without the benefit of having dgvoodoo.

It worked the night before, and then all of a sudden, it stopped working the next day. Reboot, updated video drivers, checked if antivirus has quarantined anything (no it didn't), still doesn't work.

Out of curiosity, I installed everything on virtual machine running windows and dgvoodoo works (static resolutions are available) and DS runs with dgvoodoo working as intended.

Thanks in advance to anyone who may have an idea.

Try running as admin, try enabling the 16 bit colour mode in the Properties tab and/or enable a WinXP+ compatibility mode with Run as admin. Generally this is enough.

Edit: I am not sure if the game is really seeing dgVoodoo2. It should create a device by the name dgVoodoo and not Nvidia.

Thanks for your suggestion. Changed the compatibility settings as suggested, still no go. Yes, the device name if dgvoodoo is working properly should be a dgvoodoo emulated device, that I understand. What my screenshot indicated is that there is no devices at all when the dgvoodoo is installed, and thus DG won't launch. When dgvoodoo is removed, then my original display hardware reappears. In a windows virtual machine client, everything works fine, the dgvoodoo emulated device shows up and DG launches.

The puzzling part is that it was working when I was setting things up, tweaking the settings, and I must have exited and relaunched DS a dozen times. Then I turned in for the night. The next day, it doesn't work anymore. Just puzzling, so I wanted to share this here.

The log says that dgVoodoo cannot query the supported resolution list from the display output

100000050	65.33289337	[436908] [dgVoodoo] ERROR: DDBase (00DB1998): Cannot query supported resolutions on display output 0, list is empty.	
200000051	65.33290863	[436908] [dgVoodoo] ERROR: DirectDraw (03B06DD8) Initializing failed: Cannot query supported resolutions on output device 0.	
300000052	65.37889099	[436908] [dgVoodoo] ERROR: DirectDrawCreate/DirectDrawCreateEx: creating DirectDraw object has failed.	

Do you see resolutions in the Cpl application?

Edit: Ok, according to your screenshots, there are no resolution there as well. Then in any other DX11 application?
I remember somebody else also had this problem and his/her driver turned out to be incompatible with Win11 AFAIR.

Dege wrote on 2024-11-05, 17:05:

The log says that dgVoodoo cannot query the supported resolution list from the display output […]
Show full quote

sc999999 wrote on 2024-11-05, 14:47:

BEEN_Nath_58 wrote on 2024-11-02, 15:17:

This isn't a bug, it is probably the DWM not detecting the 16-bit modes necessary for the game. Or it is seeing too many video m […]
Show full quote

This isn't a bug, it is probably the DWM not detecting the 16-bit modes necessary for the game. Or it is seeing too many video modes.

Also for old games, it will directly show the GPU name or Primary Display Driver, so in this case its using the Nvidia

Try running as admin, try enabling the 16 bit colour mode in the Properties tab and/or enable a WinXP+ compatibility mode with Run as admin. Generally this is enough.

Edit: I am not sure if the game is really seeing dgVoodoo2. It should create a device by the name dgVoodoo and not Nvidia.

Thanks for your suggestion. Changed the compatibility settings as suggested, still no go. Yes, the device name if dgvoodoo is working properly should be a dgvoodoo emulated device, that I understand. What my screenshot indicated is that there is no devices at all when the dgvoodoo is installed, and thus DG won't launch. When dgvoodoo is removed, then my original display hardware reappears. In a windows virtual machine client, everything works fine, the dgvoodoo emulated device shows up and DG launches.

The puzzling part is that it was working when I was setting things up, tweaking the settings, and I must have exited and relaunched DS a dozen times. Then I turned in for the night. The next day, it doesn't work anymore. Just puzzling, so I wanted to share this here.

The log says that dgVoodoo cannot query the supported resolution list from the display output

Copy code to clipboard

100000050	65.33289337	[436908] [dgVoodoo] ERROR: DDBase (00DB1998): Cannot query supported resolutions on display output 0, list is empty.	
200000051	65.33290863	[436908] [dgVoodoo] ERROR: DirectDraw (03B06DD8) Initializing failed: Cannot query supported resolutions on output device 0.	
300000052	65.37889099	[436908] [dgVoodoo] ERROR: DirectDrawCreate/DirectDrawCreateEx: creating DirectDraw object has failed.	

Do you see resolutions in the Cpl application?

Edit: Ok, according to your screenshots, there are no resolution there as well. Then in any other DX11 application?
I remember somebody else also had this problem and his/her driver turned out to be incompatible with Win11 AFAIR.

dgvoodoo did work initially, then failed working for some reason. I tried dgvoodoo with DS2, same thing.

I updated Nvidia drivers, doesn't work. I haven't tried uninstalling drivers altogether and reinstall that way though.

sc999999 wrote on 2024-11-05, 20:21:

Dege wrote on 2024-11-05, 17:05:

The log says that dgVoodoo cannot query the supported resolution list from the display output […]
Show full quote

sc999999 wrote on 2024-11-05, 14:47:

Thanks for your suggestion. Changed the compatibility settings as suggested, still no go. Yes, the device name if dgvoodoo is working properly should be a dgvoodoo emulated device, that I understand. What my screenshot indicated is that there is no devices at all when the dgvoodoo is installed, and thus DG won't launch. When dgvoodoo is removed, then my original display hardware reappears. In a windows virtual machine client, everything works fine, the dgvoodoo emulated device shows up and DG launches.

The puzzling part is that it was working when I was setting things up, tweaking the settings, and I must have exited and relaunched DS a dozen times. Then I turned in for the night. The next day, it doesn't work anymore. Just puzzling, so I wanted to share this here.

The log says that dgVoodoo cannot query the supported resolution list from the display output

Copy code to clipboard

100000050	65.33289337	[436908] [dgVoodoo] ERROR: DDBase (00DB1998): Cannot query supported resolutions on display output 0, list is empty.	
200000051	65.33290863	[436908] [dgVoodoo] ERROR: DirectDraw (03B06DD8) Initializing failed: Cannot query supported resolutions on output device 0.	
300000052	65.37889099	[436908] [dgVoodoo] ERROR: DirectDrawCreate/DirectDrawCreateEx: creating DirectDraw object has failed.	

Do you see resolutions in the Cpl application?

Edit: Ok, according to your screenshots, there are no resolution there as well. Then in any other DX11 application?
I remember somebody else also had this problem and his/her driver turned out to be incompatible with Win11 AFAIR.

dgvoodoo did work initially, then failed working for some reason. I tried dgvoodoo with DS2, same thing.

I updated Nvidia drivers, doesn't work. I haven't tried uninstalling drivers altogether and reinstall that way though.

An update.

I used Display Driver Uninstaller (DDU) to scrub the Nvidia drivers cleanly from the system, and then reinstalled them (without GEForce experience as I usually include) fresh. dgVoodoo now works fine, DX tab shows all the static resolutions, DS video config tool shows both dgvoodoo emulated video as well as the NVidia card, and DS can launch properly.

I'll just have to keep using it and see if something goes wrong with the drivers again.

Thank you to all those who provided suggestions. I was not going to scrub the Nvidia drivers clean and reinstall them, but felt I owe it to all of you who tried to help to do at least that much.

Thanks for clarifying this issue! It might be useful for others in the future.

This was probably damaged monitor information, or an incomplete removal of a virtual display (or some other fluff that can happen on modern disconnected standby displays, such as TV's)
3DMark has had this issue in the past (EnumDisplayDevicesA() failed) and removal of the monitor in device manager and then refreshing it resolves it there. https://steamcommunity.com/app/223850/discuss … 2404648/?ctp=59