Warcraft III

What works

Out of the box:

• Movie rendered and played okay. Sound worked okay.

After Registry changes:

• All singleplayer elements of the game.

After applying patches 3297 and 3689:

• All multiplayer elements, except those listed in the next section.
  

What does not

Out of the box:

• Menu and In-Game rendering was more or less dead. It didn't crash, however textures were not being rendered onto elements (2D or 3D). Multiplayer is a non-starter, hangs when contacting BattleNet.

After Registry changes:

• Rendering under OpenGL is perfect. Naturally, the BattleNet issue still lurks.

After applying patches 3297 and 3689:

• The only thing I can see not working is Joining/Creating Custom games in multiplayer, it hangs when attempting this.
  

Workarounds

What was not tested

I haven't played all the way through the campaigns.

Hardware tested

Graphics:

• GPU:
• Driver:

Additional Comments

All in all, a win in my books. Most problems listed have fixes on this site, which worked fine for me.

Running Warcraft 3 under Wine

by Jesse Allen; the3dfxdude at gmail com

small updates by Jasmine Iwanek

Last updated 2008-07-11

Before you get started

This HOWTO only lists information specific to this app. Please keep comments and test reports brief. Please don't post copies of wine logs here! If you have trouble, see other ways of getting help.

Wine+Warcraft 3 Status as of Wine 1.0.0/1.1.1

Known Problems

• D3D8: Direct 3D mode is slow on anything but the lowest settings.
• FreeBSD: could work on version 6.2 or later, but problematic
• quartz: Divx movies have poor playback performance.
• opengl: Resolution bugs, window management bugs. Losing focus will crash the game.

Minimum Requirements

• Video card and driver that supports hardware based acceleration with OpenGL.
• Correct device node permissions to your audio, video, and cdrom.
• winecfg: A drive letter for your cdrom, and running as Win2k, XP or later.
• A REAL COPY OF THE GAME -- The game probably won't work right if you don't have a real copy.
• Linux kernel 2.6 with NTPL or FreeBSD kernel 6.2 (preferably 7) or later.

Recommended Requirements

• Warcraft 3 1.21b or later
• Wine 0.9.18 - 0.9.45. If using later wine, you must patch it--see below.
• Linux kernel 2.6.17+ or FreeBSD kernel 6.2+

**Bad Versions**

Even with patch 1.21b, it's recommended to not use these versions of software because they break the SecuRom copy protection (ie "Please insert disc"):

• Linux vanilla x86-64 kernel: 2.6.9-2.6.15, and versions less than 2.6
• Wine compiled with GCC 4.0.0-4.0.2
• Native msvcrt.dll
• Nvidia video driver compiled against mismatched X11 header files
• Fedora Core 6 kernel package less than 2.6.18-1.2784.fc6, and kernel package "kernel.x86_64 2.6.20-1.2933.fc6".
• FreeBSD

Additionally, FreeBSD kernels less than 6.2 might not work with current versions of Wine at all.

Installing the Game

To default the game to use OpenGL, see the registry import below. This creates HKEY_CURRENT_USER\Software\Blizzard Entertainment\Warcraft III with new DWORD value called "Gfx OpenGL" with the value set to 1. So you may create a file using the text, or use regedit to do the same.

When the game's installed, everything should run as expected.

Running the Game

Use the shortcuts created by the game found in your launcher menus.

Multiplayer Setup

Make sure you have the correct ports open. Open outbound and inbound, TCP and UDP, port 6112, or whatever you set in the game configuration. More Network Ports

If you try to play using the Local Area Network option, and do not see a game hosted from your machine on another or vice versa, and you are in the same subnet, this is likely caused by not having a default gateway. The game relies on sending UDP packets to the broadcast address and Linux will not send them unless there is a default gateway or another rule to handle them. To fix it, there are two methods:

Add a default gateway.
- OR -
Route 255. 255. 255. 255 to your local network.

See Wine Traffic #62 for another description of the issue. This is not considered a bug.

Mouse Automatic Edge Scrolling

When running windowed, if you move the cursor out of the screen and back again, sometimes it stays as the scrolling cursor and not the pointer cursor. Hover the mouse over a unit or building to fix the cursor. This is an oversight in the game itself and not a bug in Wine. Use mouse grab or full screen mode to bypass this problem. You may also disable automatic scrolling and use the middle mouse button or the directional keys (non-keypad) for manual scrolling.

Window managers often have the alt key bound to certain features, especially the alt-click. THIS IS NOT A WINE BUG. If you have problems with the alt key in any way DO NOT REPORT IT. Fix your window manager. I'm not going to list steps for every one because there are too many possibilites. Figure out yourself or ask in a help forum (here is okay... but be warned all I use is TWM). If you are desperate, turn off window manager managed windows in winecfg.

KDE

Go into KDE Control Center, expand Desktop, click window behavior, then click window actions tab. You can turn off the alt-combos. If you want to make window specific settings, click on window specific settings under window behavior on the side.

GNOME

The option to change the key binding is in System Menu -> Preferences Menu -> Windows.

Connect to battle.net to upgrade to the latest version of Warcraft 3 which doesn't need a CD.

If you ever get "Please insert disc", this is NOT a problem with detecting the CD. The protection system is probably still built into the game even though the CD check itself is disabled. Make sure you use version 1.21b or later. If you get this problem after having this version installed, you are likely suffering from a buggy video driver as this is the only known (and proven possible) cause at this point.

DO NOT USE NOCD PATCHES - They are pointless, and won't fix the real problem.

Method 1: Rename the videos

After installing the game, its highly recommended that you browse to your Warcraft III folder and rename the movies folder. Many people crash from the movies because of buggy sound drivers, or simply hang, so you should do this in case you are one of them. You can still play the movies under mplayer (or xine if you so choose)! TutorialIn.mpq is the very first cinematic of the game, and for the rest; *Op.mpq is the cinematic at the start of the campaign and *Ed.mpq is the cinematic and the end. If you wanted to follow the story, it's not hard at all to play the ones corresponding where you are at.

Method 2: Mark the intro as seen

If you don't want to play the campaign, but only want to start Warcraft III without a crash while playing the intro then you can simply mark the intro as seen:

1. Open reedit:
   $ wine regedit
2. Navigate in regedit to HKEY_CURRENT_USER/Software/Blizzard/Warcraft III/
3. Create a key (folder) Misc in the Warcraft III key. You can do so by right clicking the key.
4. Create a DWORD value seenintromovie with the value 0x1
­