Version patched by GOG for Windows 10

Application Details:

License: Retail
Votes: 1
Latest Rating: Bronze
Latest Wine Version Tested: 6.13

Maintainers: About Maintainership

Free Download Store Page

Test Results

Old test results
The test results you have selected are very old and may not represent the current state of Wine.
Selected Test Results

What works

The only thing that works out-the-box is to install the game either by a offline package or using the GOG Galaxy 2.0, and open the GOG's launcher.

Changing the GOG's DirectDraw wrapper setting also works perfectly fine. Require to pass a dll override on winecfg to use this tool instead the built-in ddraw.dll given by Wine.

However playing the game are only possible until the introduction videos, then simply crashes like on other reports.

What does not

Since the Wine 4.x branch the game are unplayable using normal Wine. No matter using the GOG wrapper or the built-in DirectDraw, either Diablo or Hellfire will simply crash few seconds after starting gameplay.


Like on previous reports, the dgVoodoo2 combined with DXVK solves the problem to play with the original engine. On Extra Comments, a post on Vogons explains to solve partially some issues.

 Alternatives like Tchernobog or DevilutionX are perfectly fine for single play with the original Diablo.mpq package file. Hellfire support are currently under implementation.

What was not tested

I don't play anything beyond single player. Using some tweaks with the dgVoodoo2 wrapper, some adventurous users can now fiddling with multiplayer.

Hardware tested


  • GPU: Nvidia
  • Driver: open source

Additional Comments

To play Diablo and Hellfire with the original engine require to delete the GOG's wrapper and install the last dgVoodoo2 wrapper version, and then installing DXVK, making a double conversion between DirectX 3 until DirectX 11 as intermediate stage to the native Linux Vulkan drivers.

It requires to edit manually the dgVoodoo2.conf file by any text editor and fill the following lines, by changing as follows:

WindowedAttributes = borderless, fullscreensize

AppControlledScreenMode = true

DisableAltEnterToToggleScreenMode = false

DeferredScreenModeSwitch = true


Optionally, override the screen output to our native monitor screen, and override the anisotropic filtering to 16x, and multi-sampling to 8x, that can be done with the bundled dgVoodoo2 Configuration Applet.

Finally with winecfg, made the overrides to all DXVK and dgVoodoo2 dlls, and set a Virtual Desktop with a resolution that matches the resolution selected on dgVoodoo2.conf.

With this settings the menu are now visible (but with several issues), and requiring to move the mouse cursor to refresh the screen contents. At least it's better than a black screen.

Once selected a character or loaded a saved game, the game starts without problems and everything works as expected.

selected in Test Results table below
Operating systemTest dateWine versionInstalls?Runs?Used
ShowFedora 34 x86_64Aug 17 20216.13Yes Yes NoBronzeDan 
ShowUbuntu 19.10 "Eoan" (+ variants like Kubuntu)Mar 22 20205.4No, but has workaround No YesGarbagePer Christian Henden 
CurrentDebian GNU/Linux 10.x "Buster" x86_64Feb 16 20205.1-stagingYes No YesGarbageNosferatu Arucard 
ShowDebian GNU/Linux 10.x "Buster" x86_64Feb 04 20205.1-stagingYes No YesGarbageNosferatu Arucard 
ShowUbuntu 19.10 "Eoan" (+ variants like Kubuntu)Feb 01 20205.0-stagingYes No YesGarbageNosferatu Arucard 

Known Bugs

Bug # Description Status Resolution Other apps affected
46803 Diablo 1 crash UNCONFIRMED View

Show all bugs