Dungeon Siege 1 and 2 (+ Legends of Aranna and Broken World) fail to start

[fearedbliss]

Hey @FunkyFr3sh,

I got around to testing a bunch of my other old games installed from their original discs (on Windows 10 22H2). For this round it's the following:

• Dungeon Siege 1 (Version 1.11.1)
• Dungeon Siege 1: Legends of Aranna (Version 1.50)
• Dungeon Siege 2 (Version 2.0)
• Dungeon Siege 2: Broken World (Version 2.30)

I'm bundling them in one ticket since the issues seem similar, but I can split them up if anything.

For Dungeon Siege 1 (and Legends of Aranna), I can play the game without cnc-ddraw, and everything seems to be working (mouse cursor, graphics, etc).

For Dungeon Siege 2, the game opens up fine without cnc-ddraw, but there is no mouse cursor. So this may be something that also would need to be adjusted in cnc-ddraw once we can get a fix.

As for the specific errors, DS1 and DS2 both have a video config program (DSVideoConfig, DS2VideoConfig) and their main executables (dungeonsiege.exe, LOA.exe, dungeonsiege2.exe (there are two separate dungeonsiege2.exes in two different folders - the original and the Broken World version)).

I'm able to get some logs automatically generated from the cnc-ddraw experimental debug build when I run the DSVideoConfig or the DS2VideoConfig. If I open the main executable: dungeonsiege.exe, it also generates output, but if I open the dungeonsiege2.exe it doesn't generate any output. I suppose output may be generated once we can get some more parts of it working.

Let me know if you have any questions and I can try to answer or provide more data if possible. Attached are my collected logs and a screenshot from Dungeon Siege 1.

I also found this post on steam talking about some tricks people were doing to get some of the video stuff to work (I didn't have to do this for my version of DS1 but it may reveal some stuff about the internals of the game): https://steamcommunity.com/sharedfiles/filedetails/?id=780048558

cnc-ddraw-DS2VideoConfig-1.log
cnc-ddraw-DS2VideoConfig-1-BrokenWorld.log
cnc-ddraw-DSLOA-1.log
cnc-ddraw-DSVideoConfig-1.log
cnc-ddraw-dungeonsiege-1.log

[LuKeSt0rm]

Game uses Direct3D - cnc-ddraw only supports DirectDraw (software renderer)

You could try: https://github.com/elishacloud/dxwrapper

[fearedbliss]

Hey @LuKeSt0rm, I'm familiar with cnc-ddraw and it being only a DirectDraw implementation. Even if Dungeon Siege does support Direct 3D (similar to Diablo II supporting both DirectDraw and Direct 3D), it seems that there may be a DirectDraw implementation in these older games due to my logs. It's clear that there are DirectDraw bindings in the game and it's trying to look for them. Assuming some fixes are implemented, it seems it may be possible to get the game running through the DirectDraw codepaths.

Assuming it is not possible, I'll give dxwrapper a shot. But given I've worked with @FunkyFr3sh before on getting a few other games to run (Baldurs Gate 1+2, Fallout 1+2, and some stuff regarding Diablo II), I think there may be something here.

[elishacloud]

It's clear that there are DirectDraw bindings in the game and it's trying to look for them.

Yes. Direct3D sits on top of DirectDraw. At least it does on DX1-7. So you will always see DirectDraw bindings in older Direct3D games.

[fearedbliss]

Thanks for that clarification @elishacloud, I wasn't aware of that. Although I think it would still be worthwhile to do a bit more investigation to confirm that indeed that is what is going on here (as mentioned regarding Diablo II, D2 implements DirectDraw, Direct3D, and Glide, where you can access the DirectDraw layer directly). It may be possible here that Dungeon Siege 1/2 are exclusively Direct3D games and is going through the layering that you mentioned, I'm just not 100% sure about that atm. If that is the case, I'll be happy to close this issue :).

[LuKeSt0rm]

Dungeon Siege definitely does not have a DirectDraw (software) mode like D2

[fearedbliss]

Thanks for that @LuKeSt0rm. I'll give a DxWrapper a try and report back before closing.

[MicahMoo11]

The old comment was removed because I made a mistake and gave context of information for why it works.

This should fix the no mouse cursor bug, although only NT 4 and windows 7 was tested with cnc-ddraw.
DungeonSiege2_fixed_files.zip

this below will force d3d9.dll to software rendering it is advised to use GDI 2.1 or OpenGL 2.1 for proper support.
SwiftShader v3.0.0.5003.zip

DungeonSiege2_cnc-.zip

Playing this with CNC-Draw is quite possible, but it is strongly not advised. Unless you are on Pentium 2 & 3 or very old graphics that do not have d3d9.dll or hardware from the early 2000s or late 20s?? or virtual machine virtualization with no 3d graphics acceleration like Windows 98 unofficially working with FunkyFr3sh, or somewhat supported NT 4 still away.

Yes on Windows 7 it does say 7 fps, however with old systems like before xp it is showing 35 fps. This you really need direct3D support, like https://github.com/elishacloud/dxwrapper/releases/tag/v1.3.7700.25, with older 20?? hardware for new hardware I advised https://github.com/narzoul/DDrawCompat/releases/tag/v0.6.0 dispute Vista & 7 having tons of issues.

I'm just showing this, as my mistake was that I thought it was ddraw.dll not realizing that SwiftShader wrapper was working with FunkyFr3sh / cnc-ddraw. I will be tested other d3d8.dll and d3d9.dll to make sure this mistake does not come back. For that, I apologize. I hope in the future it will be possible for FunkyFr3sh can somehow manage to work with SwiftShader as some people have no other option. at the end of the day this is on the developer or other people seeing this to decide.

I Apology from Wright Micah.