actually I meant to ask for wine-1.7.33-x86_64-1alien. Luckily I have wine-1.5.5-x86_64-1alien, but that tells me I have a 64-bit installation and can't be ran with a 32-bit wine server if I downgrade back to 1.5.5... if I stay at wine-1.7.51-x86_64-1alien then I get a little further, which is weird as I originally installed and ran using wine-1.5.5-x86_64-1alien.

here's the weird thing... I installed Diablo and ran the game with no problems using wine-1.5.5-x86_64-1alien. I don't recall if I tried running the game to test whether the game ran or not with wine-1.7.33-x86_64-1alien, but coinciding with updating to wine-1.7.51-x86_64-1alien and the updates to Battle.net I can no longer run the game! After starting the game from the command-line, all I see is the window for Battle.net and it's all white. In the command-line window all I see is a spam of

Tried clicking all over in the white box to see if I could trigger the game somehow, but no dice. My command line to start wine is

My wine-1.5.5 package contained a purely 32bit wine installation. Starting with wine-1.7.14 I switched to compiling a "wine64 'shared installation" meaning you get both 32bit wine and 64bit wine executables. Microsoft calls this WoW64, meaning your 64bit Slackware with wine >= 1.7.14 will be able to run both 32bit and 64bit Windows programs.
What probably happened is that the 64bit Wine has installed 64bit binaries (Windows DLLs etc) into your WINEPREFIX. That means you can not go back to using the 32bit wine-1.5.5 without cleaning out your WINEPREFIX first.

I found this in the Wine AppDB: "To solve the "err:d3dcompiler:compile_shader HLSL shader parsing failed" error install "d3dx9_36" with winetricks." Perhaps you have to re-install that when switching to the mixed 32bit/64bit Wine.

Note: starting with 1.7.51 I am using the wine-staging patch set from http://wine-staging.com/ . Several other distributions are already doing that, and a previous Wine related post here in LQ mentioned that games run better with the staging patches applied.

Another note: my future wine packages will also have the wine-d3d9 patch set if mesa was compiled with support for "d3dadapter" (which is true for slackware-current). See https://wiki.ixit.cz/d3d9 . You will not be affected by this either way, at the moment.

2 members found this post helpful.

is there an easy way to clean out the WINEPREFIX of the 64bit binaries so that I can see if 1.5.5 works with the updated Battle.net?

I've installed "d3dx9_36" with winetricks successfully, yet I am still getting the same messages about "err:d3dcompiler:compile_shader HLSL shader parsing failed"

Last night I was able to get into the game itself by clicking randomly within the white Battle.net window, however now I can't reproduce it! I have a feeling the mix of 32/64 bit binaries may be the cause as to why the Battle.net window is completely blank, but I can't be sure.

Just in case you weren't aware (although, you always seem to be more aware than most), wine-staging will be integrated into WineHQ. I'm not sure how it will all play out in providing wine to end-users, but it's good to see that they aren't operating separately anymore.

http://www.wine-staging.com/news/201...tegration.html

rm -r

okay, so here we go... I moved my WINEPREFIX to re-create from scratch. downgraded to wine-1.5.5 and am installing Diablo again...

1. removed WINEPREFIX, ran WINEPREFIX=$HOME/.wine-diablo3/ setarch i386 -3 winecfg
2. set to Windows 7
3. ran WINEPREFIX=$HOME/.wine-diablo3/ setarch i386 -3 winetricks vcrun2008
4. ran WINEPREFIX=$HOME/.wine-diablo3/ setarch i386 -3 wine /run/media/dimm0k/D3C1.0.0/Diablo\ III\ Setup.exe
4a. battle.net installs, but when setup tries to launch it for login credentials it exits with the message "The application failed to start because it could not find or load the Qt platform plugin 'windows'. Reinstalling the application may fix this problem."
4b. changed back to Windows XP, setup runs battle.net and allows me to login. update to battle.net begins and pressing "Start Install" results in another crash. see screenshot attached.
4c. pressing "Close" brings up another battle.net update window... "Updating Battle.net..."
4d. during this the download of the game commences and after the complete download the "Updating Battle.net..." remains.
5. ran WINEPREFIX=$HOME/.wine-diablo3/ setarch i386 -3 wine "c:\Program Files\Diablo III\Diablo III.exe" -opengl, which results in the same crash message as the attached screenshot previously.
6. if I change back to Windows 7 in winecfg, I get the "The application failed to start because it could not find or load the Qt platform plugin 'windows'. Reinstalling the application may fix this problem."

any suggestions??

Attached Thumbnails

 

Have you tried without the "-opengl" switch?

just tried... same exact exit as with it on! I'm not sure what else this could be...

On Slackware64, with the WoW64 wine package installed, why not try what happens if you omit the "setarch i386 -3" from your commands?

attempted that right now and no dice =( revised my previous post to include a screenshot of the error message. attaching another screenshot of the white battle.net window I've been referring to.

Attached Thumbnails

 

Is Battle.net using any anti-cheat software with Diablo 3?

Anti-cheat software has nothing to do with it if you are not cheating. I have never been banned or had issue with playing any games using wine because of anti-cheat software in many years of gaming. I contacted Blizzard some years ago to clear up another issue assuming I may have been banned because I was using wine. They told me that I would never be banned or blocked for playing their games under wine.

------------------------

Anyways, I am running stock Slackware64-current with multilib using wine 1.7.51 with staging patches.

Diablo 3 has been performing perfectly for a month now. Prior to upgrading wine, it was performing perfectly on wine 1.7.49-50. The only issue I ran into was the Battle.net app reporting something about a secondary log on service (I posted about this a while back in this thread). This issue seemed to have resolved itself after an update to the Battle.net app by Blizzard.

I may be wrong about this, but it's been my experience that you need to reinstall some applications when you upgrade wine or when you change the wine environment.

Here is what I am using to launch Diablo 3:

I have my winecfg set to Windows XP. In my Libraries tab (of winecfg) I have two overrides, they are shown in the attached screenshot. Everything else is left at default settings. I forget why I have those overrides- probably something I found in a bug report on wine hq.

Attached Thumbnails

 

The -opengl switch works for application only, not the launcher.
About the white screen picture you have posted, it could be a bug with wine directx.

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

The workaround may be temporarily setting wine version to XP

1 members found this post helpful.

*d3d10 (builtin,native)
*d3d11 (disabled)
*d3d9 (builtin,native)
*d3dx10 (builtin,native)
*d3dx11 (disabled)
*d3dx9 (builtin,native)
*dbghelp (builtin,native)
*msvcm80/90 (builtin,native)
*msvcp80/90/100/120 (builtin,native)
*msvcr80/90/100/120 (builtin,native)
*vcomp/90/100/120 (builtin,native)
*wininet(builtin,native)

*atl80/90/100/120(native,builtin)

Try this settings. switch between native and builtin.

1 members found this post helpful.

Yes, this is the bug I encountered. That's why I forced diablo to run opengl and I use WinXP as the environment. It's important to remember that battle.net will use the directx version you install with winetricks and override with winecfg. Try different directx versions and overrides. I am pretty sure though that if you use my previously mentioned settings, diablo and battle.net will function properly.

1 members found this post helpful.