I'm aware that it is possible to fix the speed of the game by switching the rendering system to "Software" mode using configtool.exe, but I found a workaround that allows you preserve Direct3D capabilities.

I believe this is only an issue affecting Windows 8 and 8.1 users.

Copy the files ddraw.dll, libwine.dll and wined3d.dll from this archive into your Divine Divinity folder and you're good to go. I tested it with Divine Divinity 1.0062a (setup_divine_divinity_2.0.0.21.exe) and it is working perfectly.

This seems to be a popular fix for a lot of other games available on GOG.

Cheers.

Another possibility is running Divie Divinity in Glide mode (CD release of the game works in this mode, not sure about GoG's). :-)

Thanks for this. Causes the config tool to lock up but it works great. Nice to be able to play in D3D with a normal framerate and not having my character move at Benny Hill speed in software mode.

Wish this had worked for me!...actually, buggy D3d performance has been a hallmark of the game since Day 1 when it shipped...;) I bought the game when it was still boxed and fresh on store shelves, and even then the only way to play the game at a reasonable pace was to run it in software mode...years before 8/8.1, of course.

I'm running 8.1x64 and tried this fix and the game simply locked up and refused to run--couldn't make it into the first screen opening, actually.

Since it was reported here that the files locked up the config.tool, I ran it first and switched to D3d mode from software, installed the .dll's as instructed, and ran the game--which promptly locked up...;) You're *positive* you aren't still running in software mode, I take it...?

I'd like to think I've just overlooked something simple...does anything occur to you...? Thanks. This game still delivers a lot of pleasure.

First, make sure you're running the same version of Divine Divinity as me. I tested it with 1.0062a.
It's a simple process that only requires three files copied over. The config tool does not crash for me, and I can launch directly from it with Direct 3D selected. Software and Direct 3D look noticeably different for me, so I would be able to tell if it isn't working.

The fix might behave differently depending on your hardware configuration, I cannot confirm this because I only have one computer to test it with.

I recommend trying these alternative versions in-case one of them works for you.

WineD3D 1.7.12
WineD3D 1.5.22
WineD3D 1.3.7

I'm not sure if this helps, but I'm running Divine Divinity from a batch file with one processor core specified.

start /affinity 1 div.exe

You can also achieve this using RunFirst.

and my config.div file has been edited to increase the memory limit

// set the memory limit
memory limit 64

Thanks so much for your suggestions...! I think it's great that you got this to work for D3d mode--it's just not working for me at the moment--but I'll keep working at it and get back to the thread if things change. I've never had to set affinity for a single core to get the game to run as it should, but I'll certainly keep that in mind--as it did help me in another game under 8.1x64. I usually run the game with the 64 memory limit, too (might even have tried 128, IIRC...;))

Here's the thing--it's definitely a D3d problem with the Wine files because the game is actually *running* so to speak, it's just not opening a screen, or outputting any sound, but it's resident in the Task Manager all the same when I run it with the Wine files. I have to manually end it as a task to remove it from system memory after it tries to run with the wine D3d config. Unfortunately, config.tool crashes rather hard, and in the process corrupts and destroys the config.div file! (It just disappears! ) Weirdly, with the Wine files when I simply run the game it also starts the config.tool at the same time which promptly locks up in ram as "not responding" whereas the game exe itself seems to be running OK but not outputting anything. As soon as I close the config.tool in ram, the game exe dies as well. Ah, well...

So I'll keep working with this to see if I can get it to work with my hardware--I really think it is great that you looked at this, though, and found a solution that works for you and others. And you are right about this Ddraw problem being present in more than just this older game--I had the same thing happen in Planescape: Torment, which I fixed with acqrit's (sp?) Ddraw fix. Let you know if things start working...

The game wasn't developed or bug tested on a multi-core system. It's hard to say exactly how it could affect the game, but I prefer to eliminate any unnecessary risk :-)

If I remember correctly, I selected Direct 3D with the config tool and made sure the game loaded correctly first, before copying the three files over. Since it has been working with WineD3D, I haven't switched it back to software, but the config tool launches perfectly. Maybe it's the order of events that are preventing it from working for you.

Try it in reverse too, unless you already had it in Software mode to begin with.

What graphics card do you have? Mine is an Nvidia card.

A 2GB 7850...running the 13.12 Catalysts--yes, that could make a big difference, you're right. I'll keep pluggin'...;)

Initially, before copying the Wine files over, I had been running in software mode, so I ran config.tool and put the game into D3d mode, and fired it up, just to make sure that was OK. It was...so I copied in the files and the rest is as I related earlier...

BTW, I meant to ask you...when you load a saved game, do the Wine .dlls speed that up as well, I mean to a level close to the speed at which the software mode loads a game? Even with the latest version of the game, in D3d mode that red loading bar at the bottom of the screen just crawls, comparatively, in D3d mode. It also sort of hangs for a few seconds halfway there, and then continues to creep towards the fully loaded, end position before the saved game fully loads. By contrast, the software mode save game load zips through and seems almost instantaneous...that in itself even years ago was almost enough to put me off of using D3d in the game--and of course the in-game D3d performance clinched it. I feel as though the D3d fix with the Wine .dlls might also be allowing saved games to load much faster, too, and wanted to ask about it. Thanks!

Actually, if you'll check Raze's posts, he isn't shy about recommending software mode for DD over D3d regardless of 3d card, and as a matter of fact your nVidia card wouldn't handle the stock D3d in DD any better than my AMD card--otherwise, you wouldn't have to go to the Wine .dlls in the first place, right?...;) So, really, in this case your nVidia card doesn't seem any more or less compatible than my AMD, since the game's standard D3d doesn't perform well on either card...LoL....;) Quite truthfully, I have a ton of old games and have difficulty with none of them. Your situation is almost the opposite of mine, however--in 2002 I owned a 9700P and it's been AMD/ATi ever since (Before that, strictly 3dfx.) I've never had a reason to to buy nVidia--at least, AMD has never given me one. But, this is all neither here nor there...

It could be the case that something else I'm running is interfering somehow in the case of the Wine .dlls--I don't know, but I'll find out eventually, I'm sure. For me and most everyone else, software mode is perfectly adequate and the IQ differences between D3d software mode and D3d accelerated hardware mode are very slight in this game. Still, if I can get the Wine .dlls to work, I will--and I appreciate the post and the info!

I understand what you're saying, and you definitely have a point. I also agree that software mode is perfectly adequate.

I was trying to highlight that WineD3D (and many other wrappers, even the ddraw fix bundled with Arcanum) seem to be more compatible with Nvidia cards. I'm not entirely sure "why" this is the case, but it's something I have been experiencing specifically with Windows 8.1.

Last year I was using a computer with an AMD card, and I was pulling my hair out trying to get some of my old games to work properly.
I don't want to use an inferior OS just to play old games. Now I have my Nvidia set up, I find that games require much less effort to fix.

Lol...;) Scout's honor...;)....I have no trouble with older games and I own a bunch of 'em...some are 25 years old...

But here's is what worked for me and many other people in Planescape: Torment, and what I'm working with now to try and solve this problem in DD for myself. (If possible...;))

http://www.shsforums.net/topic/48732-ddraw-fix-for-slowdownsstuttering/

Sound somewhat familiar? From what I've seen in experimenting with the Wine dll's you linked for me (thanks), your current nVidia drivers do seem more compatible with the *Wine3d* dll's than my Catalysts--at least, the ones you linked for me, no doubt about that! But the Wine3d files used in the above linked fix worked perfectly for me in Planescape Torment. As soon as I'm done testing I'll get back to the thread and let you know how things went. It'd be nice to have a more or less universal fix for D3d games like this game as was done for PST, and several other like-engine D3d games.

Thanks again for the thread, though! It got me thinking again about an issue I had placed completely on the back-burner. Hopefully this will be simple--we'll see...!

Hi! I tried the WineD3D 1.7.12 version and it works suuuper now, the only real 'issue' though is that I can't alt-tab out of the game as the game maintaines its focus and so I can only see actually the task bar. So it's impossible to open another window as it jumps straight back to the game. I discovered that the WineD3D 1.5 one let's me to alt-tab out of the game but with the 1.7 i get more performance. I recently discovered that there's a new 1.7.14 or so out and maybe it fixes the impossibility of alt-tabbing out of the game. So if it wouldn't be too costly for someone to upload the newest version of WineD3D. I would be very grateful ;)

eeeex

Thank you so VERY much. I have tried everything to get this game working. Applying WineD3D 1.3.7 finally did the trick. Thank you very much.