Still a no-go for me, unfortunately, with the 14.6b Catalysts. Software mode works perfectly--still, it would be nice to get a functioning D3d mode for this game. Ah, well...

Thanks so much devilhood, I had stuttering problems in the game and the menu mouse was laggy. All I did was put those 3 files in and boom fixed. :D

Glad I didn't have to do some weird config stuff.

Oh I just noticed with this fix it means I can't alt tab out of the game. A sacrifice that is worth it I think.

OK so I just realised you guys were talking about the varying gameplay speeds rather than stuttering. Now I have the speed problem.. :(

Can anyone compile and upload dlls from most recent version of Wine please?

I tried to use WineD3D_1.6.2 as you directed, but then the game wouldn't run. It ran before, just very slowly, so I removed the WineD3D_1.6.2 and switched to software mode. Works really fast in software mode and well, if this is anything like Diablo II then there's no huge reason to use 3D acceleration anyway.

I would have liked it to work, if only for curiosity's sake, but no harm done.

Maybe a later release of WineD3D would work, after all it's just an OpenGL wrapper for D3D, so it should work just fine.

I'm using Windows 8.1, Radeon HD7950 and Catalyst 14.9 WHQL drivers.

I checked latest Divine Divinity GOG v2.0.0.21 with default settings and WineD3D on Windows 10 x86_64. It seems like software rendering is the fastest. Default Direct3D is terribly slow. I checked different versions of WineD3D and the fastest is WineD3D 1.6.2 (100 fps test on NVIDIA 310M). Also, unchecking "smooth play" will add more performance too. I also found that WineD3D mostly performs better on x86_64 if wine is also x86_64. Even with WineD3D 1.6.2 software rendering is still the fastest but picture is significantly better under Direct3D especially when you have a lot of shadows on the screen like in underground levels. I would recommend to download WineD3D from official website fdossena.com . You need to copy ONLY ddraw.dll libwine.dll wined3d.dll to Divine Divinity installation folder.

I've been trying the files sormy pointed to at www.fdossena.com. But i used the newest version WineD3D.
Runs all perfectly and game has now 200+ FPS, and also loads and saves in no time......perfect to me.

Thx and cheers to sormy.

Did any of you guys need to hex-edit any file in order for WineD3D to work properly?

As for the readme, since DD is a DX6/DX7 game, we should:
-copy ddraw.dll, libwine.dll and wined3d.dll in the game's executable directory
-rename ddraw.dll, but make sure the file name is still 5 characters long (for instance d3dxx.dll)
-use an hex editor (for instance HxD) to replace all references to ddraw.dll with d3dxx.dll (you will have to do this for all .exe, .dll )

You don't need to do that for divine divinity. Just copy files to override them for game.

A simpler solution to the slow performance on Windows 8 and 10 is the following:

https://steamcommunity.com/app/214170/discussions/0/35222218826646571/?ctp=5

It doesn't require adding any files. It simply changes the compatibility setting that is the cause of the slowdown.

Just to be clear, despite the post saying that it's only for Windows 8, I can attest that it also works on Windows 10.

I highly recommend dgVoodoo, it fixed all performance issues in this games as well as some others on Windows 8. Just copy dlls from MS folder (not the Glide one) into game's folder and use Direct3D in games settings.

I tried dgVoodoo and didn't notice any difference, but that was after already applying the "performance patch," so it's possible that it essentially provides the same benefit, just no added benefit.

Even with either fix, though, the Council of Seven part (where you put the orbs in the bowls) would crash and the only workaround was to put the game in software mode. The second time that I did this, I forgot to set it back to Direct3D mode and eventually realized that I wasn't missing much. In fact, I think that playing in software mode is preferable and wish that I'd played it in that from the beginning. It fixed the wonky colors whenever saving and loading and on the savegame thumbnails, which I appreciate. The only drawback that I've seen is that the teleport animation isn't as complete as before. All other effects, like reflections in water and portals opening seemed as nice in software mode as in Direct3D mode, which surprised me. Now, bear in mind that I'm playing a warrior, so I don't use much magic and it's possible that some spells may look different in the two modes. You'll have to test for yourself, but I just want to suggest that people don't dismiss software mode because you assume that it's inherently inferior, as I did. After all, it's mostly a 2D game and was designed for software mode, much like Diablo II, which similarly had Direct3D and Glide modes with questionable benefits.

I've tried dgVoodoo as suggested and I can confirm that I'm able to play @60FPS at any resolution
No graphical issues/corruption, as far as I can tell.

since my last post about tinkering with WineD3D (without benefits) I had also tried DXGL which seemed to work, but randomly caused some so-called "hall of mirrors" effects on background graphics

anyone owning Diablo on gog willing to try to the ddraw wrapper bundled with it?

it seems that DivineDivinity might benefit from it too, and with better performance than those we're able to get from wineD3D or dgVoodoo

just copy this three files from one installation directory to the other:
- ddraw.dll
- dxcfg.exe
- dxcfg.ini

Tried this and so far it seems to work fine using the files you mentioned. Thanks.

I'm glad it helped


however, since posting that message I've discovered a more reliable solution


a user-created tool for switching the rendering mode used by the game
https://www.vogons.org/viewtopic.php?t=35879

- glide mode is not supported by the gog release
- software mode is available in the settings utility, but performs poorly
- direct3d is used by the gog release with varying results and incompatibilities
- directdraw performs very quite good, especially when combined with a ddraw wrapper


my suggestion is to enable the ddraw render mode and use dgVoodoo with it in order to play at 1024x768 stretched to a borderless fullscreen window