I'm on my second playthrough and both times, I could not save within the cave. As long as the game doesn't crash, though, it's really not an issue.

The white noise happens to me a lot. If I do nothing, after a while the game will crash. Closing the game and reopening seems to fix that but sometimes, a reboot is needed.

PS- I do not have Win8; still have Win7 (thank God!)

Hem.. "cave" is a bit generic, there are a lot of caves in this game. Can you be a little more specific ?

I have windows 7 (thank God, too!) 64bit, and the game never crashed a single time to me.

The white noise - do you mean that irritating sudden "hiss" ? - is a known issue with multicore cpus; if you set affinity to run the game on a single core, the noise issue will not bother you anymore.

Using Win 9x compatibility mode gave me some other issues. Divinity runs perfectly without any compatibility setting (I had only "disable high DPI scale" flag set) and the easiest and cleanest way to run it on a single core it's to create a bat file on the same directory where you installed the game the game (where there's the div.exe), name it divinity_singlecore.bat and then open it with a text editor (notepad is ok) and copy/paste this single line:

START "DIVINITY" /normal /affinity 0x1 div.exe

then save it and run the game clicking on the bat file instead of the executable (you can also create a link to the bat on your desktop and click on it to launch the game. And since default BAT icon is awful and anonymous, I suggest to change the icon with the same one used by the game)

As DD is the next game on my play list I have a quick question - I've never written a bat file before and after doing a quick Google search this is what I've come up with;

@echo off
START "DIVINITY" /normal /affinity 0x1 div.exe

Is this all that is needed to make the bat file work?

Thanks in advance.

As Raze said.. yes, it's absolutely so darn easy : )

@echo off is not necessary at all, it simply tells the CLI to not display any of the commands while the bat file is processed ( useless in this case, since the CLI window will automatically close after execution ;) )

to explain the command in detail...

"DIVINITY" is a name of your choice, that the Window and the process you're launching will display;

/normal is the process priority;

/affinity 0x1 is a binary mask - hex format - that specify what core (or cores) to use to run the process (e.g. : if you use 0x2 it will run on the second core only, 0x4 on the third.. 0x8 on the fourth... and so on ;) )

Hope everything will be fine; the game worked flawlessy from start to end for me, without any crash at all... and I never heard that irritating static noise a single time..

I think that this solution with the BAT file (without tampering with compatibility or ALT-TABbing everytime you launch the game) is absolutely the best and the cleanest - Have fun with this awesome and amazing game ; )

Thanks :)
Thank you for your detailed explanation - I remember playing this back in the day and loved it then so am looking forward to a revisit :)

I had a problem with lag, just like OP described. Low fps, extremely long loading times. And it annoyed me since I did just get a pretty good computer and the game is ancient.
Bat file some here proposed didn't work.

Ultimately what did resolve the problem for me was going to the game directory, opening "configtool.exe" and under "new rendering system" switching from "Direct 3D" to "Software". Works like a charm now.

That's what I did too!

It sounds like setting the processor affinity is to correct crashing not the lag issue, which requires either using the software rendering (easiest) or something that will translate the older graphics APIs to a newer API.

Instead of the .bat file I ended up modifying the shortcut and wanted to mention this method here since it took a bit of fiddling. This keeps the icon and lets you easily pin to the taskbar or start menu.

On Windows 10, right click on the game icon under the start menu, click on more and open file location. Right click on Divine Divinity and select properties. You will need to confirm some actions as administrator; if it gives you an error about needing permissions close properties and try again since sometimes it seems to get confused and doesn't ask for some reason.

From the properties select Advanced and select "Run as administrator". It will seem to work but not actually set the affinity if it isn't run as administrator. Then change the target field to (all one line):

cmd.exe /c cd "c:\gog games\Divine Divinity" & START "Divine Divinity" /normal /affinity 0x1 "div.exe"

Where "c:\gog games\Divine Divinity" should be the path to the game directory and can be copied from the "start in" field below that doesn't work when running as administrator for some reason. If you typo something you can change that /c to a /k and it will keep the command window open so you can read error messages.

If you pinned the shortcut it doesn't seem to update the pinned version immediately so unpin and pin again after changing properties.

After doing this if you want to fiddle with compatability settings you can do that with the properties of the div.exe file in the game directory, however I don't think any changes are needed.

To verify that it is actually setting the affinity, start the game, hit the windows key and open the task manager, click the details tab, right click on div.exe and click "set affinity". It should only have CPU 0 selected.

Great ddrawcompat fixed all my issues running the steam version. no compatibility work arounds with that version either just runs great. Game loads in 3 seconds and no lag.

Thanks, I changed the setting to SOFTWARE from D3D and now my game loads in about 2 seconds, compared to 30-50 seconds with D3D enabled.

You can also try my guide and have smooth fps in D3D.

https://www.gog.com/forum/divinity_series/divine_divinity_smooth_fps_using_dgvoodoo_2_guide/post1

Not sure about the software renderer, but on my system it was still pretty choppy and it's also possible it misses more advanced graphical effects as often software renderers were given as a last ditch compatibility effort by game developers.