I was so happy to find your announcement on Diablo 1....
...but then I cry! GOG you were my favourite reseller site but you are more and more unfriendly and lazy, especially here for ten bucks while I run it two years ago on my windows 8 computer with the community works and my cd.

I explain:
1/ ok you don't support linux but you can test it on an ubuntu with wine (should take 1hour max to test and tell) and answer on the forum and cooperate with lutris or similar?

2/ you obtained the right to redeem Diablo 1 from the grave: nice...but only english really??? you can't ask for other languages to the editor?? Again for ten euros??

for ten euros, just disappointed ...I really wanted to buy it (for my son on linux and me on windows) since i receive your email but without the two points mentioned above answered, I will keep my money. Sad 'cause I loved you ...really.

Lots of people have done that through the years--you certainly aren't the only one to have run the game before now...;) There is no native Linux version of this game--Blizzard never made one. If it's so simple to run on Wine/Ubuntu, then you should be able to do it yourself--oh, gosh, you aren't *lazy* are you?...;) GOG, however, can only distribute the game in the manner permitted by the IP holder. GOG does not own the game--the IP holder who has allowed GOG to distribute the game is the owner of the game, and GOG can only distribute a game according to the instructions from the parties who actually own the game. Your son is apt to be very disappointed moving ahead as most games lack a Linux version. That fact is well known. But, your son can do something to help himself--he can use Wine himself (or you can do it for him)--or he can dual-boot with Windows in order to run his games. Problem solved, seems to me.

Wine kinda inherently sucks... I mean, it's amazing piece of software, but let's hope his son will instead learn to code, and do some own great linux game... :) That would be even better.

The game always had issues on wine, would be nice if someone could try the gog version and check if it works. The main menu used to be invisible cause the game layers another window on top of the main window.

If the gog version doesn't work then I might have a look into it and try to make it working with cnc-ddraw.

I wasn't asking you some questions but anyway TY Captain Obvious.
If I ask you the color of the sea, you answer the color of the ground? Give me a favour, keep your Trump-like haughtiness away from my post dude. You have money for windows and english is your native language, well done to you and stay in your narrow-mindedness. There are different people on earth and with different aspirations from yours even if you do not like it. Thank for your instructive answer. I will watch the forum for such return also.

@ped7g: for sure :D He do and you should welcome that next-generation learns computing on gnu/linux rather on closed OS

Actually there are chances to get Diablo running with a native engine under Linux or MacOS.

There are three open source engines that work with the original data files. You can view some examples on Youtube.

Engine #1
Devilution
A reversed engineered engine.
https://github.com/diasurgical/devilutionX

Engine #2
Freeablo
A "modern implementation" of the Diablo 1 engine
https://github.com/wheybags/freeablo

Engine #3
DGEngine
https://github.com/dgengin/DGEngine

You can also try Wine ( https://appdb.winehq.org/objectManager.php?sClass=application&iId=73 ) or Playonlinux.


Best regards
Beeco

PS: I tried it on Playonlinux with wine 4.0, but it didn't work.

Confirming this doesn't work with wine or proton, but its the original Diablo ON GOG so it won't take long.

The game DOES work with wine.
However the main menu doesn't render properly (top left corner is covered by a black box and the menu only updates under your mouse so you have to sweep around to find anything) but other than that the game runs fine. Once you get past the main menu all graphical issues are gone.
You need to set ddraw override to "native, buildin" and launch the game using Diablo.exe in the "dx" directory.

Here is a small clip of the menu issues and the game itself working after you get past the menu:
https://my.mixtape.moe/iaxvdl.webm

Hello @VodkaChicken, could you share with us the steps to make it works ?

Thanks and Regards !

I would like to add that GalaxyHaxs' devilution is an accurate reverse engineering project in the spirit of openTTD and similar projects (unlike the other 2). I 'm quite sure this project will result in near future in truthful and accurate binaries for Windows, Linux, Mac, whatever + community fixes, replacing as the community default the outdated Blizzard binaries - so keep an eye on it.

The family of results is currently here:
https://github.com/diasurgical

the modern builds are here (only for linux currently)
https://github.com/diasurgical/devilutionX/releases

Hello,
Thanks for the pointer i didn't know about this project. I manage to build it, but at launch, the diabdat.mpq isn't found (i double checked, in lowercase and in the same folder as the executable..., i did try to move the executable to gog diablo install folder, same issue).

For the wine part, all the menus are black, but the game seems to work fine.

Diablo was only in english when he was sold in 1996. So don't ask gog to provide something which doesn't exist. If you played Diablo in another language, it was a mod of original game or you played diablo on playstation one.

What differentiates the X version from the in Devilution other if I may ask?


Edit: Nevermind, I think X is a multiplatform version. Too bad I get a directsound error, might be related to a recent change as I see sound files were changed yesterday.

Release 0.1.0 is commit 0d1d55d8dffb8ebb7d82d26060303d1bf1554f47. Alternatively, I built master on the 9th, 75b6992233e550ddc3ad8d2fdf54f4c9e643b537, and it's working well. I haven't seen anything other than the already known issues.
You need to manually copy diabdat.mpq. Oh, I guess you have that from the Wine install. You also need write permissions, for some reason, on it.
Any non-ascii chars in the full path?