|
Edit: Liquipedia article has updated infos: http://wiki.teamliquid.net/starcraft/Playing_Starcraft_on_Linux
Well, after scraping information on the web, here is a guide to run SC:BW on Linux, running it on fullscreen, updated and battle.net compatible. Also, this method circumvents a bug that makes the keyboard unresponsive after joining a multiplayer game.
Here is what you will need:
- PlayOnLinux; - SC:BW Digital Download. - If you want a fixed 4:3 aspect ratio, a video driver that responds to xrandr commands (nouveau and intel were tested). Proprietary drivers might work, but the aspect ratio should be configured elsewhere;
1 - First of all, install PlayOnLinux on your distro and method of choice. It is needed because it offers a wine version that is somewhat compatible with battle.net.
2 - After installing, go to Tools>Manage Wine Versions. Install version 1.5.1-Starcraft_battlenet.
3 - Wait for the downloads and installation to finish, then go back to PlayOnLinux main screen and select Install, then on the lower left select "Install a non-listed program" > "Install a program in a new virtual drive" > select a name, "scbw" is fine > Check "Use another version of wine" then select version 1.5.1-Starcraft_battlenet > 32 bits windows installation > browse to the SCBW digital download installation file "Installer.exe".
4 - Install normally, on C:\Program Files\Starcraft, then select "Exit Installer".
5 - Now PlayOnLinux will give you options to select the executable. Select StarCraft.exe and then finish.
This basic installation will give you a usable SC:BW, but there is a bug regarding keyboards and active screens. To fix that, we gonna run wine and SCBW on another X server entirely. You can update the game connecting to battle.net before the next steps.
Create a new file called scloader with these lines:
* #!/bin/bash * xrandr --output HDMI-4 --set "scaling mode" "Full aspect" & * xinit ~/.PlayOnLinux/wine/linux-x86/1.5.1-Starcraft_battlenet/bin/wine ~/PlayOnLinux\'s\ virtual\ drives/scbw/drive_c/Program\ Files/StarCraft/StarCraft.exe -- :1
The first line just tells the system that this is a bash script.
The second line is for maintaining aspect ratio (so the screen doesn't stretch), entirely optional. You should replace --output HDMI-4 with your connected display (check with xrandr --prop).
The third line is what creates a new X server. You must replace any path changes for wine 1.5.1 and your StarCraft installation.
Save the file, and make it executable (chmod +x scloader). Now, running this script will bring a new X server on your main screen, and you can just swap to your previous desktop with Ctrl+Alt+F1~F8.
One thing missing: sound. You must add your current user to the audio group: "sudo adduser _username_ audio". You must reboot (or relog) for this change to take effect.
I hope this helps! Obs: submitted to liquipedia, reviewers welcome.
|
|
TLADT24917 Posts
Sounds great. Good work!
|
|
Canada11355 Posts
I currently run both ICCUP launcher and SC:BW on an ubuntu laptop(an ancient one at that) using only wine and it all runs flawlessly. I will try this method soon and see if it is significantly different. Will report back this week probably
|
Is this an advertisement for PlayOnLinux?
I've been running Starcraft on Linux with pure wine for a long time now, and got it working on battle.net with only a bit of effort. Is there something in more recent versions of wine that makes it not work with battle.net? Or what's the point of this thread?
Also, a word of warning: BW in wine can only see other computers running BW in a LAN if they are also running Linux with wine. Basically, if you want to play BW at a LAN party, either have all computers run Windows, or all computers run Linux, don't mix them. (This applies for Diablo 2 as well, when you trick it into connecting to other computers via LAN by specifying local IP addresses.)
|
I tried different wine versions, the most recent being 1.7.22 (only black screen with nouveau, works with intel) on fedora 20, but they all show graphic glitches on battle.net on the menu and buttons. You could use any wine version really, but the best one I found was the one provided by POL. It applies a patch made by someone on the wine bug tracker.
The keyboard bug was solved on my setup by running the game on a separate X server. I guess your mileage may vary between distros and this bug won't happen.
So no, I'm not advertising. The point is to have this documented somewhere, and avoid frustration for someone new.
|
The colour palette on battle.net will always be messed up, but that's not really a good reason to install software that might not be in the repository of your distro, in my opinion.
It also helps to install a few extra MS fonts (can't remember which, but the information is out there), so that the text is displayed with the correct size and in the correct location on the screen when on battle.net.
Not sure about the keyboard bug. Either I didn't have it, or it was something that was solved by alt-tabbing from and then back to the SC window.
Either way, I think that newcomers would be better served by looking for solutions for their problems on WineHQ's AppDB (namely at http://appdb.winehq.org/objectManager.php?sClass=application&iId=72 , or, more specifically, here: http://appdb.winehq.org/objectManager.php?sClass=version&iId=149 ).
|
On August 11 2014 14:16 GeLaar wrote: Also, a word of warning: BW in wine can only see other computers running BW in a LAN if they are also running Linux with wine. Basically, if you want to play BW at a LAN party, either have all computers run Windows, or all computers run Linux, don't mix them. (This applies for Diablo 2 as well, when you trick it into connecting to other computers via LAN by specifying local IP addresses.) This is a complete nonsense. For the whole life I've never had any problems with LAN (UDP) under wine. It always worked alongside with different distributions, configurations and operating systems. I always play LAN games under wine with my friends who run it in windows. Maybe you're experiencing a network priority issue in windows. Though I don't know about LAN (IPX) connection, it's useless now anyway.
|
Now can you do this for Diablo2 also? XD
|
Regarding the whole topic about running BroodWar under wine.
In most cases you don't need anything specific to run it. Just install stock wine (PlayOnLinux is not needed) and start BroodWar or iCCup Launcher. It should work out of the box so to speak.
However those who don't use proprietary video driver or have a pretty old video card can experience some problems (Yes, video card matters here, despite the game being old, wine uses OpenGL capabilities of your card for it's directdraw implementation). In case of lags try wmode plugin from iCCup Launcher. If it doesn't suite for you, you can either configure a second graphical server to easily switch between desktop and BroodWar in 640x480 or install proprietary driver (nvidia/ati) if your card is not 10 years old or so.
Maybe I will write a more complete guide that will cover these rare cases when BroodWar doesn't run well out-of-the box in some configurations.
|
On August 12 2014 03:55 Mistakes wrote: Now can you do this for Diablo2 also? XD Sorry, I mentioned only BW. Haven't tried Diablo2.
|
I will not try any linux BW fixes without the written approval of the dark archon
|
On August 12 2014 03:50 AleXoundOS wrote:Show nested quote +On August 11 2014 14:16 GeLaar wrote: Also, a word of warning: BW in wine can only see other computers running BW in a LAN if they are also running Linux with wine. Basically, if you want to play BW at a LAN party, either have all computers run Windows, or all computers run Linux, don't mix them. (This applies for Diablo 2 as well, when you trick it into connecting to other computers via LAN by specifying local IP addresses.) This is a complete nonsense. For the whole life I've never had any problems with LAN (UDP) under wine. It always worked alongside with different distributions, configurations and operating systems. I always play LAN games under wine with my friends who run it in windows. Maybe you're experiencing a network priority issue in windows. Though I don't know about LAN (IPX) connection, it's useless now anyway.
I have experienced this problem first-hand with BW on LAN (UDP), and upon googling it found that it is a known issue. But good to know that it doesn't affect everyone.
Edit: On second thought, I'm not 100% sure whether it was both games, or just D2. So feel free to disregard what I said about BW.
|
United States10328 Posts
I can usually run BW / iCCup through Wine on Ubuntu (from 10.04 all the way to 14.04 now), barring some weird problems with my install. I haven't tried Diablo 2 though (I just play that using Daemon Tools on dual-booted Win7, heh)
|
On August 12 2014 16:55 ]343[ wrote: I can usually run BW / iCCup through Wine on Ubuntu (from 10.04 all the way to 14.04 now), barring some weird problems with my install. I haven't tried Diablo 2 though (I just play that using Daemon Tools on dual-booted Win7, heh)
That's a shame. D2 runs very smoothly in wine. In fact, since they removed the CD check, it no longer requires a separate installation on Linux, just the patched game. You could run the D2 you have installed on Windows right now from Linux, and it should work without any problems.
Sorry for getting off-topic.
|
On August 12 2014 20:43 GeLaar wrote:Show nested quote +On August 12 2014 16:55 ]343[ wrote: I can usually run BW / iCCup through Wine on Ubuntu (from 10.04 all the way to 14.04 now), barring some weird problems with my install. I haven't tried Diablo 2 though (I just play that using Daemon Tools on dual-booted Win7, heh) That's a shame. D2 runs very smoothly in wine. In fact, since they removed the CD check, it no longer requires a separate installation on Linux, just the patched game. You could run the D2 you have installed on Windows right now from Linux, and it should work without any problems. I can confirm this.
For BW however I only use VirtualBox with WinXP inside because I haven’t seen any BW working properly under wine (e.g. wrong aspect ratio, broken bnet menus, launcher not working etc.). I might try it again in the near future but I am not very optimistic.
|
OK, I updated the wiki page with more info. More suggestions are welcome!
|
I followed the guide. All steps 1-5 work good. But motherfrigger is asking for a CD. Other issue is, upon installing Brood War, motherfugger warns me that it requires Starcraft to be installed. Bitch don't work.
|
|
|
|