It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
Oh yes, you can run Divine Divinity on your Mac, even on an antiquated GMA 950 MacBook like mine. It just takes a healthy amount of persistence, some digital elbow grease, and a desire to play one of the best underrated CRPGs ever made. It's a lot of steps, but I tried to be as thorough as possible to help anyone interested in playing this gem on their Mac:

1. Download Wineskin Winery (current version as of this writing is 1.7), from http://wineskin.urgesoftware.com/tiki-index.php?page=Downloads - make sure it lives in /Applications

2. Open Wineskin Winery - click on the “+” button to install a new WINE engine (For my system I’ve used the latest version as of this writing, WS9Wine1.5.13AMDSpeedHack).

3. Click on “Create New Blank Wrapper” in Wineskin Winery, and select the WINE engine version you just downloaded and installed in Step 2. Name it “Divine Divinity”.

4. Wait several minutes for the Wineskin Wrapper to be built; you will get two dialog boxes asking if you want a Gecko package and a Mono package installed; click Cancel for both (Divine Divinity doesn’t need HTML rendering or .NET compatibility, so neither Gecko nor Mono are required).

5. Once the process is finished, navigate to ~/Applications/Wineskin where your new Divine Divinity application wrapper lives. Double click it to launch it; this will launch right now the Wineskin utility located inside the wrapper. In the future, once the game itself is installed, double clicking the wrapper will launch the actual game.

6. In the Wineskin utility, click on “Install Software”. Navigate to the location where you downloaded the Divine Divinity GOG installer, and open it. This will launch GOG’s installer for Divine Divinity. You can skip the installer’s built-in file integrity check to save time.

7. In the installer itself, uncheck the option to install the extra PDF reader to save on drive space. Click that you’ve agreed to GOG’s terms and conditions and hit install.

8. Once the installer finishes, exit it. DO NOT click on the option to immediately launch the game, as there still is some work that needs to be done to make the game functional.

9. When the installer exits, Wineskin will put up a dialog box saying that it has detected some new .exe files. Make sure you select “div.exe”, and click on OK.

10. The game is now fully installed in your Wineskin wrapper, but in order to work in WINE, the in-game renderer needs to be switched from Direct3D to DirectDraw. The configuration tool included with the game does not allow for that, but an older version of the configuration tool, included with older demo versions of the game, do allow for this switch. Therefore, from a demo version of Divine Divinity downloaded from Fileplanet, I’ve extracted an older version of the Divine Divinity configuration tool. You can download it here: https://www.box.com/s/65286zcn43eop254zs4a

When you have downloaded the file (oldconfigtool.exe.zip), extract it into Divine Divinity’s install folder: right-click/control-click on your Divine Divinity compatibility wrapper, and select “Show Package Conents”. Go to the alias named “drive_c” and navigate to drive_c/Program Files/GOG.com/Divine Divinity - make sure that you DO NOT overwrite the existing configtool.exe file.

11. Now we are going to make a mini-app which will give us easy access to the Divine Divinity configuration app we just installed. Back in the WIneskin utility, go to the Tools tab (if you do not see it, click on the “Advanced” button), and click on Custom EXE Creator. Give it the name “Configuration Tool Old”. Navigate to /Program Files/GOG.com/Divine Divinity/oldconfigtool.exe

We also need to do the same for the existing, newer config tool (which we need to use to configure the game’s resolution); the file name, in the same folder, is configtool.exe; name it “Configuration Tool New” to prevent confusion. Make aliases of these files and place them wherever you wish to make access to these tools easier.

12. One last thing to do is install Xquartz, available here: http://xquartz.macosforge.org/landing/ - after you have installed Xquartz, go to the Options tab in Wineskin and select “Force use of system installed Xquartz instead of using built-in WinekinX11”. This avoids some nasty screen tearing and redrawing issues that may occur otherwise.

13. Finally, before running the game, launch the “Configuration Tool Old” file to set the game to use DirectDraw, NOT Direct3D; the older configuration tool will not let you change screen resolutions; to do this, use Configuration Tool New to launch the newer configuration tool to change resolutions.

14. If you are in Lion and observe screen corruption/artifacting issues with this game, there are two things you can do:
a) Go to the Wineskin utility application in your Divine Divinity wrapper (use the “Show Package Contents” command to access it). Go to Advanced > Tools > Winetricks and under “settings” run ddr=gdi (to undo this, run ddr=opengl). This will allow play in full screen without visual corruption, but it may lead to reduced performance.

Or:

b) Play in a virtual desktop: go to Set Screen Options in Wineskin Advanced (or select Set Screen Options in Wineskin’s main menu). Select the Radio Button labelled “Override”, and select “Virtual Desktop”. Set it to 1024x768, or to the resolution you have set in the newer config tool for the game. This guarantees no visual corruption or screen tearing, and guarantees the game running at full screen; you will however lose the ability to play in full screen.
I have not tested it myself, but the AppDB at WineHQ indicates that DirectDraw may not be necessary any longer.

http://appdb.winehq.org/objectManager.php?sClass=version&iId=18392

Of course, YMMV depending on your specific Mac/setup.
Nope, the test crashes for me when I try the Direct3D renderer. Tested Wine 1.5.14 and Crossover Wine 11.2.0 (the Crossover fork of Wine, not the actual Crossover product). Software renderer works fine as well for those who might have trouble with DirectDraw.
avatar
gammaleak: I have not tested it myself, but the AppDB at WineHQ indicates that DirectDraw may not be necessary any longer. http://appdb.winehq.org/objectManager.php?sClass=version&iId=18392 Of course, YMMV depending on your specific Mac/setup.
I really wish that were true, since Larian took DirectDraw rendering out of Beyond Divinity (which I would really like to play on WINE), but from my testing, Direct3D still doesn't work, even on WINE 1.5.14.
avatar
rampancy: I really wish that were true, since Larian took DirectDraw rendering out of Beyond Divinity (which I would really like to play on WINE), but from my testing, Direct3D still doesn't work, even on WINE 1.5.14.
According to the link I posted the Platinum rating (and D3D functionality) applied to Wine 1.4 and 1.5.2

I have a MacBook Pro 5,3 (Intel Core 2 Duo & GeForce 9800M GT). I just installed the new Divine Divinity installer using Wineskin with Wine 1.5.2 and D3D works flawlessly.

So, like I said originally, YMMV. Maybe ATI cards in new Macs still have issues?

I'm downloading Beyond Divinity right now to test that out.
Post edited October 17, 2012 by gammaleak
avatar
rampancy: I really wish that were true, since Larian took DirectDraw rendering out of Beyond Divinity (which I would really like to play on WINE), but from my testing, Direct3D still doesn't work, even on WINE 1.5.14.
avatar
gammaleak: According to the link I posted the Platinum rating (and D3D functionality) applied to Wine 1.4 and 1.5.2 I have a MacBook Pro 5,3 (Intel Core 2 Duo & GeForce 9800M GT). I just installed the new Divine Divinity installer using Wineskin with Wine 1.5.2 and D3D works flawlessly. So, like I said originally, YMMV. Maybe ATI cards in new Macs still have issues? I'm downloading Beyond Divinity right now to test that out.
D3D works for you!? Huh! Well then, it could very well be a hardware issue, as my test rig is a GMA 950 MacBook with 10.6.8. I still find it odd that D3D works on your setup and not mine, as the game is certainly old enough that it should run just fine on my system without any special coddling.
As an FYI, Beyond Divinity also works with Wineskin/Wine 1.5.2. I wouldn't be surprised if later versions of Wine also worked.

Note that Beyond Divinity was much more touchy than Divine Divinity. It crashed on me once during character creation. It also didn't like to have the intro movies interrupted once they got going (but interrupting them right away seemed to work alright).
avatar
rampancy: my test rig is a GMA 950 MacBook with 10.6.8.
Unfortunately Intel graphics cards are notoriously finnicky and don't work in a ton of test cases where they ought to be just fine. It's quite strange.
Post edited October 18, 2012 by gammaleak
D3D is broken on my early 2009 iMac with an Nvidia GeForce 9400 as well. I get a white screen and then the generic Wine crash dialogue. As long as the Software Renderer works I don't really care though, performance is perfect for me.
OK, I have tried a downloaded wrapper from the Porting Team and creating one via this thread all to no avail.

Is there anywhere I can download a working Wrapper for this game ?
@rampancy

Thanks, man!

Your step-by-step instructions on how to run Divine Divinity on Mac OS X actually worked! Kudos!

My specs:
Mac OS X 10.8.3
iMac 27-inch, Late 2012 (2560x1440 screen)
Wineskin engine WS9Wine1.5.26
Divine Divinity GOG version 1.0.2 English

I followed all of your steps (1.-13.) and it resulted in black upper half of screen so I did step 14a too ("ddr=gdi") and then it worked flawlessly.

Some observations:

- after completing step 14a ("ddr=gdi" winetrick) I switched back to WineskinX11 (unselected "Force use of system installed Xquartz instead of using built-in WineskinX11") which resulted in unchanged good graphics but avoided loading that separate X11 application that was bothering me a bit and all continued to work well

- i used the new configuration tool to switch to 1600x900 resolution. that seemed the best balance for getting more screen estate (for putting automap and inventory) but preserving discernible objects and readable fonts

- it is possible to play this games without the old configuration tool and without Xquartz when selecting "Software renderer" in the new configuration tool (instead of "Direct3D") and when selecting "Use Mac Driver instead of X11" inside "Screen Options" of the "Wineskin" tool: graphics were fine BUT i experienced an annoying mouse twitching bug so that was not an option.

Now continuing to enjoy the game (I am a Divine Divinity newbie) and waiting for the "Original Sin" kickstarter game to be released (hoping for native Mac version) :-) ...
avatar
rampancy: 14. If you are in Lion and observe screen corruption/artifacting issues with this game, there are two things you can do:
a) Go to the Wineskin utility application in your Divine Divinity wrapper (use the “Show Package Contents” command to access it). Go to Advanced > Tools > Winetricks and under “settings” run ddr=gdi (to undo this, run ddr=opengl). This will allow play in full screen without visual corruption, but it may lead to reduced performance.
Thank you, that solved the tear red on screen on moving :D
It all worked. Now it doesn't flicker anymore. Running OS 10.7.5 on a MacBook from late 2008. Thank you open source community.
For High Sierra, os 10.13.6, Wineskin Version WS9 Wine2.22, I first did this
"launch(ing) Wineskin.app, going to Set Screen Options, and uncheck the Auto Detect GPU for Direct 3D option, and the wrapper should work normally."

In order to install the executable, I had to open the Wineskin app inside the wrapper, click advanced, browse to the c: folder where I had placed the gog executable, then click "test run" to start the installer.

After it installed, the GOG games folder was outside of the program files folder in the wineskin wrapper, so I dragged it in there.

Then I went back into the Wineskin app, clicked advanced again, and changed the file to "div.exe" inside GOG games/Divine Divinity.

Then I followed the rest of the steps. I installed Xquartz, but checking the box to force it made things worse.

I used number 14 to solve the visual problems.

i also checked use option key as alt in the wineskin advanced options.

Thanks!
Post edited October 15, 2019 by bananaquiet