32-bit Guild Wars 2 client used when 64-bit system requirements are not met or the client is forced to with the
-32 command-line argument. It is recommended to use the 64-bit client when possible.
* Dungeons, fracals
* World Bosses and Events (temples, ...)
* Crafting, including at the mystic forge
* Other "ordinary life" aspects (explorable zones, ...)
What does not
* Change of clothes is corrupted, unless wine is compiled from CSMT tree at https://github.com/stefand/wine, but the tree is still at wine 1.7.18 at the time of writing this report (which is also fine with GW2)
* WvW and World Events almost unplayable because of too poor
performances + occasional crashes. Same experience while killing some
champions (in particular during guild bounty). Also worse / more
frequent than in previous releases (back 4-5 releases). But I really
think it is actually due to the Megaserver update, that emphasizes the
already known limits of Wine towards running GW2.
What was not tested
* PvP, but I think it works fine (as fine as the rest anyway)
* I still revert an old commit that broke the mouse view to 180Â°: git revert --no-edit 76bbf106a28c4caa82873e8450bde7d4adc765bf, but I did not test this release without the revert* game installation, but since updates are fine, I assume install should work too
* I used to have a lot of loading issues in dungeons, especially in Ascalonian Catacombs, but this has been a lot better for a few Wine releases. * Starting the game with or without -dx9single makes little difference to me, even with CSMT patches. * CSMT patches themselves make a visible, although much less impressive than what is advertised, difference to me. * I have the feeling performances are best just after starting the game + when there are fewest sprites moving around (players or NPC). Having low or high options makes no difference when few characters are around, performances are not too bad. * However, I decreased the options regarding the rendering of characters, but to no avail in World Events (now overly large since Megaserver update). * I have taken the habit of restarting the game now and then, to avoid crashes at a bad timing and to get back to better performances. * CPU to performance now give smaller advantage compared to previous releases, which is good because it means more gets done by the GPU; on the other hand, it is now mostly beneficial, but not enough, when in large events though.
|Operating system||Test date||Wine version||Installs?||Runs?||Used|
|Show||Solus||Dec 04 2017||2.21||Yes||Yes||Yes||Gold||Victor Roux|
|Show||Elementary OS Loki||Jul 30 2017||2.12-staging||Yes||Yes||Gold||Brendon|
|Show||Linux Mint 18.1 "Serena" x86_64||Jul 11 2017||2.12||Yes||Yes||Gold||Marosh|
|Show||openSUSE Tumbleweed (rolling release)||Apr 05 2017||2.4||Yes||Yes||Gold||Jon|
|Show||Linux Mint 17.3 "Rosa" x86_64||Mar 10 2017||2.3||Yes||Yes||Platinum||Cory|
|Bug #||Description||Status||Resolution||Other apps affected|
|31839||Mouse jumps to the upper left corner of the screen||UNCONFIRMED||View|
|31952||Guild Wars 2: Graphical bug causing horizontal lines on world||NEW||View|
|32010||Guild Wars 2 updater uses always 100% of a CPU core||UNCONFIRMED||View|
|32058||Guild Wars 2 launcher freezes/hangs (unable to launch game)||RESOLVED||NOTOURBUG||View|
|32152||Guild Wars 2: Missing sound and game crashes on time adjusting||UNCONFIRMED||View|
|33053||Support for dvorak programmer layout.||UNCONFIRMED||View|
|33759||Some applications reset the X color profile||UNCONFIRMED||View|
|34342||Chronic crash of Guild Wars 2(out of memory)||NEW||View|
|40299||Guild Wars 2: Graphic shows through the ground||UNCONFIRMED||View|
|40300||Guild Wars 2: Mouse gets temporary invisible on the Launcher||UNCONFIRMED||View|
|40843||Guild Wars 2: Game crashes on uninstalling||UNCONFIRMED||View|
|44315||Buffer maps cause CPU-GPU synchronization (Guild Wars 2, The Witcher 3)||NEW||View|
PlayOnLinux and PlayOnMac users can ignore this entire note - PlayOn* already does all of this for you!
At this point, you have installed Wine and you're ready to install the game.
First, let's figure out how to manage wine prefixes.
Wine Prefix Setup
You really should get used to wine prefixes. If you're installing everything to the default prefix (~/.wine) you're missing out on the ability to use optimal settings (and wine versions) for each game you own. PlayOnLinux/PlayOnMac asks you if you want to create a new prefix when you install something, it's so simple that I'll not explain how to do it.
If you're on linux Q4Wine is a great application which offers a GUI for wine. You can of course manage prefixes but also do a lot of other cool things.
Here is how to create a new prefix with q4wine:
Once you're more familiar with the interface, follow these steps to set up a prefix for GW2:
Of course if you know other ways to manage wine prefixes you can do so.
Install the Game
Your options are:
Installing using the launcher:
Installing using the CD:
This is pretty darn simple, but you're going to install the entire game by patching, so it will take longer.
Installing using existing installation's files:
Here's several things you can do to get better performance/correct problems:
Out-of-memory errors are more common on the 32-bit version of the Guild Wars 2 client. It is highly recommended to use the 64-bit client if possible.
You can fully download all of the game data and any future updates required for Guild Wars 2 by appending
-image as a command-line argument to the Guild Wars 2 executable (
Gw2.exe). An example can be found below:
WINEPREFIX=~/'Wine Prefixes/Guild Wars 2' wine 'Gw2.exe' -image
You can also check the integrity of the game data archive by appending
-repair as a command-line argument (this can take longer than 5-10 minutes to complete):
WINEPREFIX=~/'Wine Prefixes/Guild Wars 2' wine 'Gw2-64.exe' -repair
For quick guidelines:
-imageis recommended so you don't have to worry about streaming data during gameplay
Gw2.datfor a while, it's a good idea to run
-repairon it every now and then after updates
-repairis highly recommended