I’ve tried with WinE-staging and PlayOnLinux, but I get this.
I tried using native dbghelp dll, but no luck.
I’ve tried with WinE-staging and PlayOnLinux, but I get this.
I tried using native dbghelp dll, but no luck.
No luck yet here either.
Update: I get it to install (partly?), but when I try to run I’m now presented with an unresponsive grey window titled “Warcraft III CDKey Required”. X closes it.
Anyone got it working? or got any further?
If I run wine w3setup.exe -opengl with sudo I get to choose language, but then it fails on agent not being able to connect.
Cmon blizz, fix the installer for us linux users
So I got the game to run… the quick and dirty way I did it was to use Lutris to install Overwatch. It will basically install Battlenet and you can choose to install Overwatch or not, I only want the wine-prefix it created.
I then choose to run an exe from within the prefix, choose the 1.30.2 version installer. It will install successfully and then I also got the grey screen. I moved the windows out of bounds of my screen and back into view which refreshed the content and I could click on Digital version (and not CD-Key). Move out of bounds and back and I can enter my Battlenet credentials. Move out of bounds and back and I can verify my account etc. etc…
Game launched fine, was stuck at 1024x768 but I am sure someone here knows the fix for that
edit: Manjaro 18.x
nvidia 1060
410.x driver
That … is the weirdest solution I’ve seen in, like, 3 years. TYVVVVVVVM.
Happy accidents happen (think penicillin)
hi people.
everything works fine for me.
ubuntu 16.04 & wine-staging 3.13.2
please try this wine-version if you have issues.
Thanks for the lutris tip, got me on the right track.
My problem was that I’m running bumblebee and it doesn’t have vulkan support, new battle net requires some vulkan calls which were crashing it after few seconds. So I’ll just expand on solution by @nlsthzn, this is for nvidia graphic card holders on notebooks
-Battlenet needs to run before launching w3.exe installer, so :
Pretty epic journey, but works (with some fps drops)
Also you get this error when battlenet is not running in the background
Maybe my little trick helps someone (although I’m a little afraid Blizzard will find a way to destroy this workaround too if they didn’t thought of this themselves already…)
If you have access to a windows installation (make a virtual machine with a test version of windows 10 for example) just overwrite your wc3 wine installation with the files of the windows installation.
Worked flawless for me.
Oh and by the way, I use Arch!
With the latest hotfix I get “wrong installation folder” allowing me not to proceed in the installation of the patch. Anyone know how to fix this?
Do you have battle net and warcraft installed in same prefix ? Is the w3 launcher in the correct folder with w3 installation ? Maybe just clean install will work
BTW! If you need to update Wc3 it works the same. Run the Battlenet-App and then Warcraft 3 Launcher within the Battlenet-App prefix and it should work.
I tried your method and It works, moving the window out of bounds makes it refresh, but in my case the installer will not respond to the mouse T.T
Moving the window out of bounds solves it for me, thanks!!
When I try this I still get the connection error and I can’t move the windows out of bounds - it is stuck in my screen.
EDIT: Holymoly - you have to launch the battlenet app before executing the installer. I should rtfm. Thanks all!
!!! THX !!!
this is working!!!
As the installation is running in the background. I have time to write how it worked for me.
this is the only way how I could achieve it.
Thanks to especially this forum and “Anachron” <3 <3 <3
I can confirm that it has been working for me. I googled how to do it, and they said to install wine staging. I did that, then I installed Battlenet app first, then it works great as long as the Battlenet app is running.
I was able to install the game, and update it. There was the black window asking for CD key, but because I saw this same popup on Windows, I clicked in the blackness, knowing where the fields were, and the interactivity still worked – the window was just painting as black instead of visible. But once that’s over, the rest of the actual game works fine.