WineHQ

Guild Wars 2

64-bit Guild Wars 2 client officially released May 17, 2016. This is the ideal client to be using and should be considered the default client.

Application Details:

Version: 64-bit Client
License: Retail
URL: http://www.guildwars2.com
Votes: 1
Latest Rating: Silver
Latest Wine Version Tested: 6.14

Maintainers: About Maintainership

Link Play For Free Link Guild Wars 2 Wiki 64-bit Client Information Link 64-bit Client FAQ Forum Post Free Download Guild Wars 2 64-bit Setup Executable

Test Results

Selected Test Results

What works

I updated versions and ran for an hour or so.  No crashes, connection trouble, mouse control problems, or frame rate issues.  (I did not experience the mouse control issues others had with 6.6, so YMMV)  

What does not

Frame rate problems without the dxvk patch.

Workarounds

I was using the dxvk 1.8.1 patch.

What was not tested

Installer.  Did not exhaustively test all game modes.  Just an hour or so of play on ~10 or so PVE maps.

Hardware tested

Graphics:

  • GPU: Nvidia
  • Driver: proprietary

Additional Comments

selected in Test Results table below
Operating systemTest dateWine versionInstalls?Runs?Used
Workaround?
RatingSubmitter
ShowopenSUSE Tumbleweed (rolling release)Aug 15 20216.14Yes Yes NoSilverKosstAmojan 
CurrentFedora 33 x86_64Apr 26 20216.7-stagingN/A Yes YesGoldframed 
ShowFedora 33 x86_64Apr 12 20216.6-stagingN/A Yes YesGoldframed 
ShowArch Linux x86_64Apr 11 20216.6-stagingYes Yes NoGarbageDeandre Thomas 
ShowopenSUSE Tumbleweed (rolling release)Mar 31 20216.5No Not installable NoGarbageKosstAmojan 

Known Bugs

Bug # Description Status Resolution Other apps affected
32010 Guild Wars 2 updater uses always 100% of a CPU core UNCONFIRMED View
32152 Guild Wars 2: Missing sound and game crashes on time adjusting UNCONFIRMED 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
41962 Guild Wars 2: Mouse acts if raw input is broken if The Forest is opened in window mode UNCONFIRMED View
42145 Guild Wars 2 crashes on some configurations UNCONFIRMED View

Show all bugs

HowTo / Notes

Game Data Updating and Integrity Checking/Repair

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-64.exe or 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:

  • For initial installations, -image is recommended so you don't have to worry about streaming data during gameplay
  • If you've had your Gw2.dat for a while, it's a good idea to run -repair on it every now and then after updates
  • If you've had to hard-shutdown your computer while GW2 was running, running -repair is highly recommended

Comments

The following comments are owned by whoever posted them. WineHQ is not responsible for what they say.

i experience the same bug as Deandre Thomas
by Joël on Monday April 12th 2021, 13:04
i'm using openSUSE Leap 15.2 with KDE desktop environment and wine staging 6.6

Being unable to rotate the camera makes the game unplayable.

i'm going to attempt filing a bug report (i'm not confident in my skill to perform that).
RE: i experience the same bug as Deandre Thomas
by Joël on Tuesday April 13th 2021, 10:47
i believe it will be fixed in the next release
RE: i experience the same bug as Deandre Thomas
by Joël on Tuesday April 13th 2021, 10:48
forgot the link to the bug
bugs.winehq.org/show_bug.cgi?id=50969
Same Problem. I switched back to 5.17 for playing.
by KosstAmojan on Friday March 19th 2021, 3:44
wine 6.0 to 6.4 has the bug.
No networkconnection possible.
RE: Same Problem. I switched back to 5.17 for playing.
by Lambda on Friday March 19th 2021, 6:45
In my case, going back to wine-staging 6.2 from the winehq repositories worked as well.
Can access login servers error
by Lambda on Wednesday March 17th 2021, 5:42
I just wanted to report that I also have encounter the login error 42:0:9001:4457 on my machine. Fedora 33 / wine-6.3-1.fc33.x86_64 . It worked fine until the latest package upgrade.
RE: Can access login servers error
by KosstAmojan on Friday March 19th 2021, 3:42
Same Problem. I switched back to 5.17 for playing.

wine 6.0 to 6.4 has the bug.
No networkconnection possible.

by Lambda on Sunday January 24th 2021, 14:53
I'm seeing a similar behaviour since about 17.1.2021 - I'm on wine 6.0.1 (staging) (Fedora package wine-6.0-1.fc33.x86_64 ) and get similar lockups with the message close to it in the log:

0120:err:sync:RtlpWaitForCriticalSection section 000000014218F170 "?" wait timed out in thread 0120, blocked by 0000, retrying (60 sec)

GPU is AMD Radeon RX 560 (as discrete GPU in a laptop).
Wine-Staging 6 rc5 freeze
by Bart Vaes on Thursday January 7th 2021, 15:58
As the subject says: using Wine-Staging 6.0-rc5 I suddenly get periodic screen freezes that last 3-4 sec or so.
I'm using OpenSUSE Leap 15.2 and for some reason the Wine packages are very old (latest=5.0, a year old but works flawless actually).
I get this output:

bart-at-localhost:~> mesa_glthread=true WINEDEBUG=fixme-all wine64 start /unix "$HOME/Games/Guild Wars 2/Gw2-64.exe"
bart-at-localhost:~> ATTENTION: default value of option mesa_glthread overridden by environment.
Native Direct3D 9 v0.7.0.368-release is active.
For more information visit github.com/iXit/wine-nine-standalone
mesa: for the --simplifycfg-sink-common option: may only occur zero or one times!
mesa: for the --global-isel-abort option: may only occur zero or one times!
fixme:d3d9nine:D3DPERF_GetStatus (void) : stub
0140:err:winediag:MIDIMAP_drvOpen No software synthesizer midi port found, Midi sound output probably won't work.
fixme:d3d9nine:DRIPresentGroup_GetMultiheadCount (0x2077ba0), stub!
fixme:d3d9nine:D3DPERF_GetStatus (void) : stub
0140:err:sync:RtlpWaitForCriticalSection section 0000000142153340 "?" wait timed out in thread 0140, blocked by 0254, retrying (60 sec)
0254:err:sync:RtlpWaitForCriticalSection section 0000000142153000 "?" wait timed out in thread 0254, blocked by 0000, retrying (60 sec)
0124:err:sync:RtlpWaitForCriticalSection section 000000014218DEF0 "?" wait timed out in thread 0124, blocked by 0000, retrying (60 sec)

The last 3 lines get repeated and causes the freeze.

CPU: AMD FX-6300
RAM: 8GiB
VID: AMD Radeon RX 550
wine-staging 5.20 causes the launcher to fill all the memory until the system runs out of memory
by Artemis3 on Saturday November 7th 2020, 0:07
Running with Gentoo, 64 bit profile. Until wine-staging 5.19 all is good. With 5.20, the launcher fills up all your memory causing the dreaded Out Of Memory condition. Downgrading back to 5.19 cures the issue.
GOLD ALREADY!
by Bruno Oliveira on Friday July 17th 2020, 10:37
I have installed with lutris and everything works just fine.
4.10 and the Trading post
by Jen on Thursday June 13th 2019, 23:36
I've tried both 4.10 and 4.10-staging, and every time I try accessing the trading post, I get "net::ERR_FAILED". Anyone else getting this? I didn't get it with 4.9-staging.
BUG: Black Screen
by Ricardo Rodrigues on Wednesday June 20th 2018, 21:55
Hi,

Posting a Bug Report is a pain, so a comment will have to do.

I get a Black Screen when entering the game (after logging in) and this is because I changed the scale in xrandr.

Steps to reproduce:

1. Change scale: xrandr --output DP-2 --scale 0.75x0.75
2. Start the game.
3. Black screen, but game is responsive.

A lot of message errors will appear saying: X11DRV_ChangeDisplaySettingsEx No matching mode found 1440x1620x32 @0! (XRandR 1.2)

Current Solution: HACK

1. Create a script to start the game.
2. Before the command to start, scale back: xrandr --output DP-2 --scale 1x1
3. After the command to start, scale: xrandr --output DP-2 --scale 0.75x0.75
4. Start the game (no black screen)
RE: BUG: Black Screen
by Bruno Oliveira on Friday July 17th 2020, 10:44
you actually don't need a script.
you can create a .xprofile $HOME and /etc/xprofile

content of my xprofile:

xrandr --output HDMI-A-1 --panning 1920x1080 --scale 1.406x1.406
xrandr --dpi 141

The game works just fine for me ;)
vulkan+esync+aco
Gentoo?
by Jeffrey Jensen on Tuesday March 6th 2018, 17:56
Is this confirmed working in Gentoo Stable? I'm having issues getting it launched currently. Haven't messed with it too much yet
Guild Wars 2
by Frank on Monday January 1st 2018, 22:55
I found that this game works perfectly with older versions of wine too, it's all good (from 2.0 and upwards), I'm using Debian Stretch. I worked away all the error messages in the debug output and it works great. I even use the nvidia optimum, all good. Only i found that by switching to Wayland, that the mouse error (that the mouse stops at a certain point which prevents you from looking 360 degrees in 1 move) from long ago is back. In X I don't have this.
RE: Guild Wars 2
by Bruno Oliveira on Thursday November 12th 2020, 13:19
Works flawlessly with proton as well.
This should be PLATINUM!
Back