using wine-2.8 packaged by Alien and winetricks-20170614 on Slackware64 14.2, while also having installed corefonts, ie8, and vcrun2015 along with adding d3dcompiler_47 in winecfg. install went fine, however when I start the game I can hear the music playing however my screen is black. any suggestions? running nvidia 375.39 binary drivers as well that was packaged using the SBo script to give the 32/64 bit versions of the driver.

I don't have the game. Are you using the 32 bit exe because the 64 bit supposedly requires directx 11. This site provides a how to: https://appdb.winehq.org/objectManag...sion&iId=29952

FWIW some blizzard games used to support -opengl switch you could add to executable like: 'nice -19 wine game.exe -opengl', not sure if that's still the case with new games.
It bypass the d3dx*>opengl translation layer in WINE, resulting in much better performance.

got everything working! steps involved

update/install multilib (slackpkg update && install) - this was key!
WINEPREFIX=/mnt/diablo/.wine-diablo3 winetricks corefonts ie8 vcrun2015 d3dx9_36
WINEPREFIX=/mnt/diablo/.wine-diablo3 winecfg
set Windows Version to Windows 7, enable CSMT (staging tab)
WINEPREFIX=/mnt/diablo/.wine-diablo3 wine /tmp/Diablo-III-Setup.exe
WINEPREFIX=/mnt/diablo/.wine-diablo3 wine "c:\Program Files (x86)\Diablo III\Diablo III.exe" -opengl
skip logging into the game client and proceed to the Blizzard App screen
Options > Game Settings > Launch 32-bit client
Play game!

I run wine-staging from SBo (version 2.11), multilib, enable CSMT, use WINEARCH=win32 to launch, and configure wine to use a Windows 10 environment. Be sure you install and launch the game from the Battle.net application. Depending on how new your hardware is, you may need to upgrade to Slackware-current for better graphics support. I usually only install vcrun2008 and everything works fine.

Edit: You do not need the OpenGL switch anymore.

Edit2: The in game store doesn't work, so if you want to buy the new necromancer patch, buy it from the Battle.net site by logging into your account.

1 members found this post helpful.

thanks for your info and edits! should definitely make this couple of wine and Diablo much easier to deal with. the only issue I have with the Battle.net/Blizzard App is if I log into it I get some weird stuff, one being that the Diablo screen no longer shows anything, not even the PLAY button. if I log out, then that appears again. does this happen for you as well?

You need to run in Windows XP mode or in Windows 10 mode for the Battle.net app to show everything.

I install Diablo by installing the Battle.net app like so:

Change to csmt and windows 10 mode. Then install stuff with winetricks:

Launch the Bnet setup executable:

Let Battle.net install and launch itself. Log into your account. Exit the app and restart Battle.net with this command:

Then download Diablo. Once everything is downloaded, launch Diablo using the "Play" button. I like to run it all from a terminal window for debugging purposes because sometimes when there is an update to a package in Slackware that also has a Multilib counterpart, I have to build a compat32 package. The alternative is to wait for AlienBOB to push out a multilib update. If for some reason the game (or any of Blizzard's games) is not launching, remove the following from the wine command to debug the process:

The last part may or may not be necessary. I read somewhere that suppressing debug and fixme messages speeds up wine a tad bit.

1 members found this post helpful.

Does this mean access to opengl backend is now denied, or simply that it now works regardless of which backend is used?

I think wine defaults to an OpenGL backend. I may be wrong, hopefully someone can shed some light to confirm. I have a built-in Intel graphics card in my laptop and forcing -OpenGL doesn't seem to change performance with the switch or without it. I am talking strictly about diablo 3. Other games may have a different outcome.

Easy way to test it would be blacklisting all d3dx* dlls in winecfg and then passing -opengl to game executable (not launcher executable) on command line.
There may be an alternative somewhere in launcher configuration, where the launcher passes the specified command line switch to game executable.
It's the game engine part used by Mac client where d3dx is unavailable, not an internal part of WINE. I know WINE's supposed to default to opengl, but I'm interested in whether or not the launcher now enforces directx backend, i.e. whether or not the devs restriced the opengl backend to Mac client.

A recent update to the Blizzard app may require you to disable the d3dcompiler_46 library in winecfg. This will allow you to see all elements in the application. Some people say the filed ticket is a duplicate ticket, others says disabling the library fixes things, others say its another issue altogether. This is not always needed, but is discussed in the following wine hq tickets:

https://bugs.winehq.org/show_bug.cgi?id=42000
https://bugs.winehq.org/show_bug.cgi?id=38845

YMMV. Happy gaming!