[SOLVED] Diablo 3 will not run, alien's wine package

dimm0k · 08-28-2015, 02:39 PM

anyone able to get the CTRL-R to show the FPS in the game? finally got everything running thanks to everyone in this thread, but would like to know the stats performance wise. Also, does the Battle.net launcher keep saying to Update ever couple of launches?

mralk3 · 08-28-2015, 04:51 PM

Quote:

Originally Posted by dimm0k

anyone able to get the CTRL-R to show the FPS in the game? finally got everything running thanks to everyone in this thread, but would like to know the stats performance wise. Also, does the Battle.net launcher keep saying to Update ever couple of launches?

I launch WoW from the game .exe, not from the "Battle.net Launcher.exe" for simplicity.

Code:

wine "C:\Program Files\World of Warcraft\Wow.exe"

mralk3 · 09-03-2015, 11:07 AM

I have Diablo III running well on Wine 1.7.50 using the wine staging patches. Today there were some server outages this morning so I updated wine.

dimm0k · 09-03-2015, 11:23 PM

do the wine staging patches have any effect on the game?

mralk3 · 09-09-2015, 04:46 PM

Quote:

Originally Posted by dimm0k

do the wine staging patches have any effect on the game?

The staging patches allow the game to run whereas the same version of wine without the staging patches did not allow me to run Diablo. World of Warcraft runs fine without the staging patches. Sorry on the late reply.

mralk3 · 09-17-2015, 07:35 PM

Over the last week have had an issue running the Battle.net app. I was not able to launch the Battle.net app to log into the game. It gives a message complaining that the "Windows Secondary Log On Service" needs to be enabled. My work around has been to reinstall the Battle.net app each time I launch Diablo for the day/night. I run "wine uninstaller" from my desktop launcher and remove Battle.net, while leaving Diablo intact. I then launch Diablo from the Diablo executable and the Battle.net App is reinstalled. The game launches from the "Play" button in Battle.net just fine after that. Luckily I have a fast network connection that will download the 250MB Battle.net app in a few seconds.

Here is the related Wine HQ Bugzilla report with a few other solutions.

If anyone else has a better workaround please share!

dugan · 09-17-2015, 07:56 PM

I saw that on Reddit today. I didn't see any real solutions, but the thread is here:

https://www.reddit.com/r/linux_gamin..._requires_the/

number22 · 09-17-2015, 08:43 PM

Work around from internet; just relaunch battle.net launcher app again in same window, ignore first error message, once 2nd battle.net launcher runs, you can safely close this error message from first run.

Windows XP will be dropped from support for all battle.net apps soon, you can try windows 7 in wine.

dimm0k · 09-24-2015, 05:46 PM

I'm having different issues now... haven't played or launched the game in a few weeks since getting it to run perfectly, but recently updated to wine-1.7.51-x86_64-1alien and from the looks of it updates to the game caused issues so now I'm not sure what's wrong. After logging in all I get is a white window with the following code in the command line window

Code:

fixme:hlsl_parser:declare_vars Complex initializers are not supported yet.
fixme:hlsl_parser:hlsl_parse Array.
fixme:d3dcompiler:make_assignment Check for casts in the lhs.
fixme:d3dcompiler:make_assignment Check for casts in the lhs.
fixme:hlsl_parser:hlsl_parse Array.
fixme:d3dcompiler:make_assignment Check for casts in the lhs.
err:d3dcompiler:compile_shader HLSL shader parsing failed.

dugan · 09-24-2015, 05:50 PM

I wonder if it's because when you run the game with Wine 1.7.51 it thinks it's in an environment that can do DirectX 10 or 11. The latest versions of Wine are beginning to support DirectX 11.

What happens if you use the -opengl switch mentioned in post #2?

dimm0k · 09-24-2015, 05:54 PM

dugan, I'm unfortunately already using that... here's my command line

WINEPREFIX=$HOME/.wine-diablo3/ setarch i386 -3 wine "c:\Program Files (x86)/Diablo III\Diablo III.exe" -w -opengl &

dugan · 09-24-2015, 06:11 PM

Quote:

Originally Posted by dimm0k

WINEPREFIX=$HOME/.wine-diablo3/ setarch i386 -3 wine "c:\Program Files (x86)/Diablo III\Diablo III.exe" -w -opengl &

I can't think of any recommendations right now. But I do see that you're following the best practice of creating a separate wine prefix for each application. You might want to check out the project I have to manage that:

https://github.com/duganchen/wine_env

And its SlackBuild

https://raw.githubusercontent.com/du...env.SlackBuild

I also have an equivalent project for the FISH shell (which I use and love):

https://github.com/duganchen/wine_env_fish

and a SlackBuild for it:

https://raw.githubusercontent.com/du...ish.SlackBuild

dimm0k · 09-27-2015, 01:14 AM

thanks dugan for the nice wine_env manager! now, do you have access to wine-1.7.51-x86_64-1alien.txz from alienBob? I'd like to not compile it myself it possible...

dugan · 09-27-2015, 02:23 PM

Quote:

Originally Posted by dimm0k

thanks dugan for the nice wine_env manager! now, do you have access to wine-1.7.51-x86_64-1alien.txz from alienBob? I'd like to not compile it myself it possible...

I don't understand the question.

If you're asking whether my Wine manager supports Alien Bob's Wine package, the answer is of course. Just leave out the wine executable path when you create the bottle.

If you're asking whether I'm currently testing Diablo 3 with Alien Bob's Wine package too, the answer is no.

Alien Bob · 09-27-2015, 05:15 PM

Quote:

Originally Posted by dimm0k

thanks dugan for the nice wine_env manager! now, do you have access to wine-1.7.51-x86_64-1alien.txz from alienBob? I'd like to not compile it myself it possible...

You can download that package from several servers. What is your issue?