All official unmodified Frozen Throne versions without the World Editor.
What does not
What was not tested
CPU: AMD Ryzen 1800X @ stock
GPU: nVidia GTX 1080 (Gigabyte Aromor 8GB)
No winetricks or any other workaround used.
Installed on a clean wine prefix
|Operating system||Test date||Wine version||Installs?||Runs?||Used|
|Show||Ubuntu 19.04 "Disco" amd64 (+ variants like Kubuntu)||Jun 13 2019||4.10-staging||Yes||Yes||Yes||Gold||Tyler Fru|
|Show||openSUSE Tumbleweed (rolling release)||May 28 2019||4.0.1||No, but has workaround||Yes||Yes||Silver||bluewww|
|Show||Arch Linux x86_64||Jun 11 2019||4.8-staging||Yes||Yes||Yes||Silver||mori|
|Show||Manjaro Linux||Apr 10 2019||4.5||No, but has workaround||No||Yes||Garbage||Matombo|
|Show||Arch Linux x86_64||Aug 19 2018||3.14||Yes||Yes||No||Platinum||Ner'zhul|
|Bug #||Description||Status||Resolution||Other apps affected|
|10841||Restore display resolution when focus is lost or on exit||RESOLVED||NOTOURBUG||View|
|20610||xmodmap numpad realigning unrecognized by Wine||REOPENED||View|
|23310||Mouse pointer prevented from leaving virtual desktop window when it shouldn't be||UNCONFIRMED||View|
|23745||warcraft 3 freeze when desktop switching/minimize||NEW||View|
|25031||Warcraft 3 display is upside down||RESOLVED||NOTOURBUG||View|
|29494||Occasional wineserver crashes when playing Warcraft 3||NEW||View|
|31245||xrandr12 warcraft 3 regression||NEW||View|
|31839||Mouse jumps to the upper left corner of the screen||UNCONFIRMED||View|
|33658||Warcraft 3: Crash on missing sound permissions||UNCONFIRMED||View|
|34247||"Program Files" is not locale-specific||NEW||View|
|35651||Warcraft III: Some videos are not played||NEW||View|
|35990||keyboard becomes unresponsive in blizzard games||UNCONFIRMED||View|
|38009||winex11.drv does not set NET_WM_STATE_FULLSCREEN if the display mode was changed||NEW||View|
|39223||Warcraft 3: Game conflicts with other applications||UNCONFIRMED||View|
|39224||Warcraft 3: Sound rustles without -opengl||UNCONFIRMED||View|
|40284||Unable to change resolution for LVDS panels (laptop), on which only one resolution is available (ex. 1680x1050)||UNCONFIRMED||View|
|40894||Warcraft 3: Crash on starting the game||UNCONFIRMED||View|
|45773||Warcraft 3: Game can't be installed via the downloader on non-english languages||UNCONFIRMED||View|
|46517||Warcraft III: Installation fails (trouble launching Battle.net Update Agent)||UNCONFIRMED||View|
There have been substantial changes such as
Patchnotes can be found here
The following command line argument forces d3d9 mode which can fix the issue (1.31.0)
There are two causes for this problem:
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.
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.
ÂÂÂLast updated : 2019-06-04
Several users with ATI Radeon video cards encounter problems when playing. If run in Direct3D mode (e.g. without -opengl switch or registry hack) Warcraft 3 doesn't even start up. If run in OpenGL mode, the console prints these error messages
libGL error: drmMap of framebuffer failed (.............)
libGL error: reverting to (slow) indirect rendering
and the game is extremely slow with corrupted graphics because it uses the MESA Software OpenGL implementation instead of the 3D hardware acceleration of the ATI card.
If you encounter the same problem, have a solution to it or ATI, Wine and WC3 are running fine for you, please describe it in this bug report:
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.
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.
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.
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.
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:
$ wine regedit