Opening credits and cinematic.
What does not
Terrain of main campaign map. Runs, but has alternating strips of black and Rainbowcolored bands across entire map. Units and cities are still visible.
What was not tested
Battle mode and multiplayer
The game runs smoothly enough, but the map graphics make it difficult to see country borders and coastlines. I also tried setting the graphic to low and still had the same problem.
|Operating system||Test date||Wine version||Installs?||Runs?||Used|
|Show||Ubuntu 14.04 "Trusty" amd64 (+ variants like Kubuntu)||Aug 21 2014||1.7.24||Yes||Yes||Garbage||Capitan Pistacho|
|Show||Ubuntu 14.04 "Trusty" amd64 (+ variants like Kubuntu)||May 04 2014||1.7.17||Yes||No||Garbage||Capitan Pistacho|
|Show||Ubuntu 13.10 "Saucy" amd64 (+ variants like Kubuntu)||Mar 08 2014||1.7.14||Yes||Yes||Garbage||Capitan Pistacho|
|Show||Ubuntu 12.04 "Precise" amd64 (+ variants like Kubuntu)||Sep 28 2012||1.4.1||Yes||Yes||Silver||Adam Bognar|
|Current||Fedora 16 x86||Jun 01 2012||1.5.3||Yes||Yes||Bronze||an anonymous user|
Dec 20, 2013 update: ETW and Napoleon are still affected by this bug, and most of the below still applies for all Wine versions to date (latest: 1.7.8). If you're running a 64-bit system, you'll need to compile inside a 32-bit lxc or 32-bit chroot, which takes a few extra steps. More on that here - http://wiki.winehq.org/WineOn64bit
September 28, 2012
ETW (and NapoleonTW) are affected by this bug - http://bugs.winehq.org/show_bug.cgi?id=18490, which causes crashes when loading a battle map.
To play battles in ETW (and NTW), you will need to: download and unpack new wine source code, apply a patch, compile the code, install the patched wine, and finally â€“ remember not to overwrite wine the next time Update Manager or whatever pops up. Itâ€™s not as difficult as it sounds, but it requires a bit of terminal work (and coffee):
a) Download the wine source code: available at http://www.winehq.org. Both the stable and development releases (at present, 1.4.1 stable and 1.5.13 development) will work. Download the packed â€˜.tar.bz2â€™ file to your PC.
b) Unpack the code: there are several ways to do this. One is to open a terminal, navigate to the directory where the .tar.bz2 file is located, and type: â€˜tar xjf winename.tar.bz2â€™. Another way (likely easier for beginners) is double-click the .tar.bz2 file icon to open it in the Archive Manager, then drag the enclosed directory (e.g. wine-1.5.13) to a directory on your PC.
c) Apply the patch: Normally, thereâ€™s a terminal patch command to enter (patch -p1 < nameofyourfile.whatever), but this is such a simple patch itâ€™s as easy to manually edit the one file and be done with it:
i. Inside the directory you just pulled out of the .tar.bz2 file, navigate into the /dlls/wined3d/ subdirectory and open the â€˜context.câ€™ file in a text editor.
ii. Ctrl+F and search for this line: if (!(hdc = GetDC(swapchain->win_handle)))
iii. This page - http://bugs.winehq.org/attachment.cgi?id=46160&action=diff
lists the edit youâ€™ll need to make (replacement text in blue, additions in green). On the left, the original; on the right, what your edited lines should look like when itâ€™s finished.
iv. Save the context.c file and exit.
d) Compile the patched wine source code and install wine: Most of what you need to know is located here - http://www.winehq.org/docs/wineusr-guide/installing-wine-source, but generally:
i. Open a terminal and navigate to the top-most directory in the directory you unpacked (e.g. /wine-1.5.13/)
ii. Type: â€˜./configureâ€™ to begin. If youâ€™ve never compiled source before, youâ€™re likely missing some required development libraries, which will be needed for the next step. Find out which libraries youâ€™re missing by: reading the terminal output after the â€˜./configureâ€™ command is completed, or (again after the â€˜./configureâ€™ command is complete), navigate to /wine-1.5.13/include/ and open the â€˜config.hâ€™ file to see whatâ€™s missing.
One easy way to install any missing libraries is via Synaptic Package Manager (which you might also have to install, depending on your distro). Basically, the process here is: run â€˜./configureâ€™, determine which library is missing, open Synaptic and install the library, close Synaptic and run â€˜./configureâ€™ again. You might need to perform this step several times as the â€˜./configureâ€™ command checks for each library it needs, but eventually the terminal output will come out clean and youâ€™ll be ready to move to the next step.
Edit: An easier method for the above: 'sudo apt-get build-dep wine' to install dependencies, and then './configure'
iii. Type: â€˜make dependâ€™. This shouldnâ€™t take very long.
iv. Type: â€˜makeâ€™. Now is the time to go get a coffee. :) This can take anywhere from 5 to 30 minutes, depending on your CPU. If this is your first time, relax, it really is doing things, wait it out and eventually youâ€™ll be returned to the command prompt (and hopefully with no errors).
v. Type: â€˜sudo make installâ€™ and enter your password to install the wine package.
vi. Type: â€˜wine --version' to confirm the new version of wine installed correctly.
vii. Type: â€˜winecfgâ€™ to initialize the new version.
Iâ€™ll keep this updated as necessary. Many thanks to user naur for creating the patch. Unfortunately, you'll need to re-do this patch/compile procedure every time you update wine.