Wings of Liberty, Heart of the Swarm, and Legacy of the Void, including Starter Editions
Please try the Stater Edition before buying the game to make sure it works on your system (link below). It includes the first campaign (Wings of Liberty) and the Arcade (Mods)
Consider including the following in your test results:
Everything that was tested.
What does not
It only requires a slight configuration to get everything running with optimum performance.
See "Workarounds" section for more details.
I use an ad-hoc 64-bit wineprefix, only for blizzard. For Example:
$ WINEPREFIX=~/.newprefix winecfg
$ WINEPREFIX=/path/to/wineprefix winecfg
(You can also use a Qt GUI for Wine like Q4Wine)
The Windows version used is 10.
if you have the .msi files in ~/.cache/wine/ should be automated when the new wineprefix is created.
winetricks arial d3dx9 d3dcompiler_42 d3dcompiler_43 dxvk
(This is for DXVK you can just install arial I presume).
(Maintainers note: This can also be done via winecfg if using wine-staging)
In Q4Wine you can simply use a Windows explorer and open Battle.net-Setup.exe or using the command line like:
env WINEPREFIX="/path/to/wineprefix" wine C:\\\\windows\\\\command\\\\start.exe /Unix /path/to/wineprefix/dosdevices/c:/Battle.net-Setup.exe
Then, to start Battle.net after setup completes:
env WINEPREFIX="/path/to/wineprefix" DXVK_HUD=full wine C:\\\\windows\\\\command\\\\start.exe /Unix /path/to/wineprefix/dosdevices/c:/users/Public/Desktop/Battle.net.lnk
("DXVK_HUD=full" is for testing purpose, you can remove it)
I'm using the 32-bit flag in battle.net game options.
For 64-bit SC2
With Ubuntu and some other versions of the linux kernel, pthread protection causes SC2 to crash immediately upon start, or after login. To fix this, enter the following command to temporarily disable pthread protection:
echo 0 | sudo tee /proc/sys/kernel/yama/ptrace_scope
pthread protection will be re-enabled upon reboot. To re-enable pthread protection manually, enter the following command:
echo 1 | sudo tee /proc/sys/kernel/yama/ptrace_scope
64-bit drove me crazy to find a solution that would make the game launch, but after all the effort to understand the problem; I still chose to use 32-bit because it had less lag for me.
What was not tested
You can find useful information here:
Kernel: 5.4.0-48-generic x86_64
Desktop: KDE Plasma 5.19.5
Distro: KDE neon 20.04
Intel Core i7-4790
GeForce GTX 1080, NVIDIA 450.66 from Ubuntu PPA
FPS 80-120 in the tutorial 2560x1440 all Ultra (maxed settings).
|Operating system||Test date||Wine version||Installs?||Runs?||Used|
|Show||Fedora 33 x86_64||Nov 21 2020||5.21||Yes||Yes||Yes||Gold||Steve|
|Show||Artix Linux||Nov 01 2020||5.20-staging||Yes||Yes||No||Garbage||Samuel Vincent|
|Show||Gentoo Linux x86_64||Oct 04 2020||5.18-staging||Yes||No||No||Garbage||nva|
|Current||Ubuntu 20.04 "Focal" (+ variants like Kubuntu)||Sep 26 2020||5.18||Yes||Yes||Yes||Gold||Talos|
|Show||Ubuntu 20.04 "Focal" (+ variants like Kubuntu)||Jul 28 2020||5.13-staging||Yes||Yes||Yes||Gold||Thomas Lucero|
|Bug #||Description||Status||Resolution||Other apps affected|
|11674||Dual-core unsupported in WoW and SC2||STAGED||View|
|30853||Wine doesn’t always handle "right alt" properly||NEW||View|
|32342||Multiple applications and games using 'Webkit' or 'Blink' web browser engine crash on startup ('Arial' and 'Times New Roman' font face name validation)||STAGED||View|
|33759||Some applications reset the X color profile||UNCONFIRMED||View|
|42741||Multiple Blizzard games fail to launch (StarCraft I & II, Diablo III, Heroes of the Storm)||STAGED||View|
|44920||StarCraft II crashes on some maps (requires HLSL compiler)||REOPENED||View|
|49476||Overwatch doesn't start on 5.10, 5.11||UNCONFIRMED||View|
|49798||StarCraft 2 hangs on startup since 5.12||RESOLVED||DUPLICATE||View|
|49994||Starcraft2 shows blank screen: DVI-D out of range 89.5Khz, 60Hz||UNCONFIRMED||View|
If using custom gamma settings or using an application that automatically changes gamma (e.g. redshift) then at specific times, your gamma setting may reset for a short time.
To fix this, open the registry editor and navigate to:
Inside the newly created "X11 Driver" add the chain value "UseXVidMode" and set it to "N".
After a Battle.net update or a crash, there are sometimes old processes left running that may interfere with your next launch. These processes can be killed before trying again:
killall -i -r '.exe'
Or you can do this manually (and more safely):
ps x #and then....kill as necessary after you got the process ID in the first column
#of course it doesn't hurt to take a look at the manual for these commands:
You can download the StarCraft II Starter Edition for free via the Battle.net Launcher, which includes the first campaign (Wings Of Liberty) and the Arcade (Mods).
Please test how / if the game works before buying it.
As of October Windows XP is no longer supported