Wine64 fails battle.net client install while Wine32 works fine
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: Slack64-Current, Windows 11, EndeavourOS
Posts: 97
Rep:
Wine64 fails battle.net client install while Wine32 works fine
Hello all,
Running Slack64 14.2 multilib.
Tried running both Alien and SBo 64 and 32 bit wine packages. Both install fine, but when installing battle.net client to run Diablo 3 and Starcraft 2, the client fails to install every time on 64 and sometimes ends up crashing Wine entirely. Killing and terminating is the only way to get it to bring back up the installer. I tried some other software such as Steam and iTunes, they all worked fine.
I have tried multiple settings in winecfg, changing windows type, disabling and overriding libraries as listed by various forum posts to no avail. After the 64bit install I tried the 32bit but it kept crashing and at this point I was so deep in mucking up my system and had plenty of dependency problems with other programs; which I later found out was an issue with using 32bit libs instead of the 64bit, I decided to do a fresh 14.2 install from scratch.
Installed 32bit wine, the latest nvidia driver, installed battle.net, Diablo 3 and it works like a charm except for an issue that is apparently only caused on a 32bit system. Its infuriating. Not sure if this is a slack problem or a wine problem. Any help or literature would be helpful.
Did you ever get any error messages? I'm not really a wine guru (haven't needed to use it in years), but error messages can sometimes help decipher what the problem is.
Distribution: Slack64-Current, Windows 11, EndeavourOS
Posts: 97
Original Poster
Rep:
>Did you ever get any error messages?
No unfortunately, however I did manage, possibly was due to last time I hadn't gotten all the way through setting up some dependencies for other software, particularly calibre, to get it installed but it will only launch in 32bit and the 64bit fails giving a d3d error.
>use the 32 bit .msi or "setup.exe" ( man i hated everything being called that )
You are definitely not alone.
>I don't know if 64-bit Diablo III will run under wine. Isn't it DX11?
I know they implemented the update to be capable of DX11, but I thought it was optionally run.
But I do have Battle.Net installed with Wine64 and can play Diablo III again, though still only in 32bit.
But I do have Battle.Net installed with Wine64 and can play Diablo III again, though still only in 32bit.
What's going on? I was playing a bit and didn't notice anything out of the usual. I'm using stock WINE 2.0 that was released yesterday. Kanai's Cube loads slowly in Act 5, but it's done that for the past few patches. (It's fine in every other act.)
Distribution: Slack64-Current, Windows 11, EndeavourOS
Posts: 97
Original Poster
Rep:
Specifically, what happens is only during multiplayer, in town, with multiple people in town on my screen. If all of those happen, which is usually after a (G)rift, vault or bounty runs, the inventory stalls displaying anything. I can hover over the blank spaces where I know there are items and the desc displays fine, but the item, both in inventory and equipped, fail to display for an varying amount of time. It eventually catches up, like rubberbanding lag, and shows items, but the moment I exit and reenter the inventory it does the same thing.
Yeah, I think that might be a problem with Diablo III. I generally go to another outpost to sell, craft, salvage, or use the cube when playing in multiplayer. If you get the 64-bit version working, I'd love to know.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.