Blizzard hotfixes the latest version and it works in Wine again
Install the latest Wine Staging
The current staging has patches in it to make running StarCraft possible. You can install the latest staging from:
Run the installer inside of a new Wine prefix like $HOME/sc-prefix and install the game there. Do not start the game after the installer is done. Hit x to close the installer when it’s finished.
Before you run it, run wineconfig on your StarCraft prefix.
env WINEPREFIX="$HOME/sc-prefix" wine winecfg
You can use the the system version of wineconfig if you’d like. Select Windows 2003 version. This makes StarCraft run, Windows XP and Windows 10 don’t seem to work on my machine.
As of staging 3.7, I no longer need that work-around, both 32 and 64 bit prefixes work without it.
Then make sure you have the correct dependencies. On Ubuntu 32 bit prefix I needed to install:
$ sudo dpkg --add-architecture i386
$ sudo apt-get update
$ sudo apt-get install libgl1-mesa-glx:i386 libasound2:i386 libasound2-plugins:i386 libc6:i386 libncurses5:i386 libstdc++6:i386 libxtst6:i386 libldap-2.4-2:i386 libfreetype6:i386
An Arch user reported he needed lib32-mpg123. You might possibly need other packages as well.
You can create a shortcut like:
env WINEPREFIX="$HOME/sc-prefix" wine StarCraft.exe
that runs inside the StarCraft folder. That way you can run using a shortcut instead of having to manually open a terminal every time.
If you don’t want the launcher to launch modify the shortcut to
env WINEPREFIX="$HOME/sc-prefix" wine StarCraft.exe -launch
If you encounter issues with StarCraft, there are two entries in Wine DB for the latest versions:
You can check each issue for workarounds. I list some of them here.
If Blizzard launcher has buttons you can’t click or see, change the version of the launcher to Windows 2003. It’s the Battle.net.exe executable inside of Blizzard App folder (not inside the StarCraft folder itself). This will give you a message that your Windows version is not supported, so you can change it back if you don’t need it.
Difficulties logging in, 6:3 Error
If you can’t log in to the Battle.net app, on the log-in screen you will see styled boxes on top. Those do not work. Use the white boxes below them. You won’t be able to see what you’re typing, but you will be able to log in if you type into them and hit the Enter key. If you are logged in, you won’t get 6:3 Error.
When running Ubuntu 17.04 I encountered an issue with Battle.net menus being slow. I downgraded to 16.04 and the issue mostly disappeared. Sometimes I have to restart the game to fix it again, but that’s not as bad as having to wait for more than 30 seconds for each menu.
Game Stuck Under Overlay
I’ve had the game stuck in a dark overlay when I pressed F10 to bring up the menu. I was able to get out of it by pressing Alt+Q during a game. This brings up the quit game modal, so I could select cancel. Selecting cancel brought me back to the game.
Performance in StarCraft: Remastered
My computer only could do 106 FPS in Remastered and 300 in SD. When I loaded up OBS, I could only hold barely above 60 FPS. OBS itself could only hold a pitiful 24 FPS.
What I did was downgrade to kernel version 4.04 and for some reason I can get 300+ FPS in Remastered and stream at 1440p in OBS at 60 FPS (although that requires too much bitrate for Twitch). Your mileage may vary. I’m not even using AMDGPU Pro drivers (I downgraded to install them and found out I didn’t need to).
Lag in ladder games
Make sure to forward port 6112 on UDP.
Ctrl+5 doesn’t work
Ctrl+5 is a shortcut in fcitx for Reload configuration in Global Config (check Advance Option). Not a StarCraft bug per se, but international users keep running into it.
Real Time Lighting
Currently StarCraft doesn’t detect that I have more than 2.2GB of VRAM, so this feature can’t be enabled from inside the game.
Appendix: How to Install from source
Use https://github.com/wine-compholio/wine-patched so you don’t have to apply staging patches manually.
$ git clone https://github.com/wine-compholio/wine-patched
and then follow this guide to compile it
Note that you don’t need to run the `clean` command on a freshly created folder.
After you finish building the 32 bit Wine you don’t need to install it system-wide, just make the shortcut point to the correct version of Wine.