WineHQ
Guild Wars 2 Release Client



Category: Main > Games > Online (MMORPG) Games > Guild Wars 2 > Release Client


NameGuild Wars 2
VersionRelease Client
License Retail
URLhttp://www.guildwars2.com
Votes 75
RatingSilver
Wine Version1.7.14
Free Download Buy Guild Wars 2
Maintainers of this version:
No maintainers. Volunteer today!
Description
Official release client for Guild Wars 2.
Selected Test Results (selected in 'Test Results' table below)

What works
looks like whole game content


What does not
no data


What was not tested
PvP WvW


Additional Comments

Tested on ASUS R500DR-SX030 (AMD A6-4400M APU set on single HD 7520G 512MB, dual graphics with HD 7470M 1024MB gives much worse fps) using PlayOnLinux 4.2.1 configured like this:


Wine version-wine-1.7.14[x86]
Arguments-dx9single

GLSL Support-enabled (game does not work on disabled)
Direct draw Renderer-opengl
Video memory size-512
Offscreen rendering mode-fbo
Render target mode lock-disabled
Multisampling-disabled
Strct Draw Ordering-disabled

Mouse warp override-force

note: best run on separate X server (few more fps)

overall performance: very low
Test Results
DistributionTest dateWine versionInstalls?Runs?RatingSubmitter
CurrentUbuntu 13.10 "Saucy" amd64 (+ variants like Kubuntu)Mar 09 20141.7.14 Yes Yes Silver S1LV3R6 
ShowFedora 20 x64Jan 27 20141.7.11 N/A Yes Silver KiXaM 
ShowArch Linux x86_64Oct 25 20131.7.1 No, but has workaround Yes Silver kaldyr 
ShowFedora 19 x86_64Jul 27 20131.6 Yes Yes Bronze KiXaM 
ShowArch Linux x86_64May 13 20131.5.28 Yes Yes Gold an anonymous user 


Known bugs
Bug # Description Status Resolution Other apps affected
11674 Dual-core unsupported in WoW and SC2 NEW View
29872 Guild Wars: Character graphic is corrupted NEW View
30511 Guild Wars 2 launcher crashes with "assertion m_ioCount failed" NEW View
31442 Guild Wars 2 freezes on text input fields UNCONFIRMED View
31628 Guild Wars 2 Low Performance/Not using all CPU cores UNCONFIRMED View
31952 Guild Wars 2: Graphical bug causing horizontal lines on world UNCONFIRMED View
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
32153 Guild Wars 2: Input gets stuck UNCONFIRMED View
32586 Guild Wars 2: Installation window is hidden UNCONFIRMED View
33053 Support for dvorak programmer layout. UNCONFIRMED View
33479 Guild Wars 2: Raw input is broken NEW View
34144 Guild Wars 2: Crash if minimized UNCONFIRMED View
34342 Chronic crash of Guild Wars 2(out of memory) UNCONFIRMED View
35118 Guild Wars 2 runs slow UNCONFIRMED View
35852 Sound plays too fast, alsa underruns UNCONFIRMED View

 
Known Issues
  • Mouselook
    • Worked great in early betas
    • Broke in beta 3, requiring the raw3 patch -- which was still imperfect
    • raw3 patch is included in Wine 1.5.13, but is still imperfect
    • There is a patch to fix our one remaining issue with mouselook attached to this bug report.  Included in 1.5.14 - so mouselook is completely fixed.
    • It's broken again as of 1.5.29.
  • Trading Post, Gem Store, Etc
  • Performance
    • While you should be able to get acceptable performance with a relatively powerful system, you may be stuck unable to engage in all aspects of the game, as of the time of this writing. Unfortunately, the game has issues running well on linux for a multitude of reasons, and there’s no one great solution - just a bunch of minor suggestions that can help some.
  • Patching
    • While you shouldn’t notice this outside of the initial installation (because patches are rarely large enough to trigger this), the patcher crashes every few thousand files. The best solution right now is to either just work on other things on your computer while GW2 is patching and monitor it manually, or use a script (there should be a few linked in the comments).

 
Getting a Version of Wine That Runs GW2

Guild Wars 2 runs well enough on Wine versions 1.5.13 and later (mouselook did not work at all on 1.5.12 and earlier), but you still can't access the trading post or gem store without patching wine, and you still can run in to issues where mouselook will be bound to a box (you'll hit a sort of "wall" as you're turning the camera and you'll have to release and re-press the right mouse button to turn any farther).

There are two methods to getting a copy of Wine that fixes those issues.

The Easy Way

For anyone who just wants to play the game, this process is for you. You will probably be a little bit behind, because this method won’t always include all of the most recent patches, but it will get you up and running quickly, and it avoids the pain of patching and compiling from source.

  1. Find the package(s) for your system for PlayOn*. PlayOnMac for OS X users, and PlayOnLinux for everyone else.

  2. Once you've installed PlayOn* (just follow their install instructions), click on the "Install" button.

  3. Search for Guild Wars 2 in the list. Most likely, you will find it in "Testing" (that's where I found it) or "Games".

  4. Once you've found Guild Wars 2, select it and click on "Install".

  5. From here on out, you should be able to follow PlayOn's instructions. Make sure to read *everything*, as it will tell you about several potential issues and what to do if/when they happen.

The Hard Way

For those of us who want absolute control, who want to know exactly what's going on, and who want to help debug patches as they come out. This method is more difficult, but you won't have to wait for PlayOn to include new patches, and you'll have the benefit of helping the Wine developers test patches.

  1. Step one is to git the most recent source code. You want to be bleeding edge, right? Isn't that the whole point of doing this instead of just using PlayOn? Well BE BLEEDING EDGE! Use git! (If you would rather just download the source for the latest released version, that's perfectly fine - you should be able to find the download links).
    1. Make sure you have git installed. Most distros should have it; those that don't, should have it in their repositories. Just install it like you would any other package.
    2. In a terminal, change directory to a folder where you want to keep Wine's source. I chose ~/dev/wine.
      $ mkdir -p ~/dev/wine
      $ cd ~/dev/wine
      				
    3. Clone the wine sources.
      $ git clone git://source.winehq.org/git/wine.git ./wine-git
      			
  2. Alright, so now we have the source code. It's time to get some patches.

    To be perfectly honest, I doubt that I'm going to manage to keep this guide up to date at all times. If you're doing this, then I'm going to assume that you know what you're doing and let you figure a few things out for yourself. The first of which is which patches you need.

    The Wine team will include their patches into git once they have been properly tested, so which patches are needed will change based on when you did your last git clone or git pull (or git fetch/merge).

    Put as simply as possible, go through each of the bugs above. See if the bug report has any patches attached. If it does, read through the most recent comments to see if that patch (or any other fix for the same issue) has been included in Wine git. If not, then it's a patch that you want.

    Patch files are simple text, and will probably just open in your browser like a normal text file. Just copy all of that text to a new text file, using your favorite text editor, and save it somewhere in your Wine development folder.

    As an example, I'm going to show you the steps I took to apply the awesomium patch to my sources.

    1. After finding the patch you want (in my case, this one), copy the text.

    2. Open your text editor (in my case emacs) to the file you want to save the patch as (in my case, ~/dev/wine/awesomium.patch) and paste the copied text.
      $ emacs -nw --no-init-file ~/dev/wine/awesomium.patch
      				
    3. Save the file and quit your text editor (for anyone who decided to just use what I use without knowing what emacs is, the command to save is ctrl+x followed by ctrl+s; the command to quit is ctrl+x followed by ctrl+c).
    4. Patch wine.
      $ cd ~/dev/wine/wine-git
      $ patch -p1 < ../awesomium.patch
      				
      Note that the -p1 argument is telling the patch command to ignore the top level directories of all file paths. This is because the patch I've selected is a diff between the directories "a" and "b" (you can see a/dlls/[...] and b/dlls/[...] at the top of the file). This is how most patch files are, but you might find a couple odd ones out.

  3. Now that you've patched Wine, it's time to configure and install it.

    1. You may need to run some of the scripts in the ./tools folder. Check this in the comments for the patches that you've applied. One specific example was tools/make_requests, which was required for the raw3 patch. It doesn't seem to be necessary with the awesomium patch or the patch that fixes mouselook being bound to a box - but it also doesn't seem to hurt.
    2. Decide where you want this wine installation to live. Personally, I wanted to keep my non-system Wine versions in my home directory, so I install them to ~/.wine-versions.

    3. Run the configure script, telling it where you want Wine installed. Note that this is where Dependency Hell usually sets in - it will tell you that you don't have something installed, you have to install it, then run this step again, then it tells you you don't have something else installed, etc. Hint: you will probably need to look for the -dev or -devel packages from your distro.
      $ ./configure --prefix ~/.wine-versions
      				
    4. Make. Side note, this is where your *other* Dependency Hell issues will show up - but they're usually more minor than during configure.
      $ make
      				
      Phew. That one was tough.
    5. Install. If you chose a directory that is *not* in your home directory, you will need super user permissions (sudo or su) for this step.
      $ make install
      				

 
Setting Up GW2

PlayOnLinux and PlayOnMac users can ignore this entire note - PlayOn* already does all of this for you!

At this point, you have your GW2 version of Wine and you're ready to install the game.  The first thing you should know is that the installer from the disc doesn't work very well.  It can be used, but considering that none of the graphics show up (at least, last I checked), you might be better off just copying the Gw2.exe file from the disc and letting the patcher install the game.

But first, let's figure out how to manage wine prefixes.

Wine Prefix Setup

I don't really care how you manage your wine prefixes, but you really, really, really should get used to using prefixes.  If you're installing everything to the default prefix (~/.wine) then you're missing out on the ability to use optimal settings (and wine versions) for each game you own.

Now, on the other hand, managing prefixes manually can be very tedius.  PlayOn* handles multiple prefixes for you - but this guide isn't for PlayOn* (honestly, it's dead simple and handles prefixes without asking you for any real details, so it doesn't need a guide).  Personally, I use q4wine for this.  I'm sure there are other applications out there that do similar things.

q4wine

You're on your own with installing q4wine.  Most likely, you have it in your repositories.  If you don't, you should probably start at the q4wine website.

Once you have it installed, start it up and look through the UI a bit.  Open up the q4wine settings and try to customize it to your liking.

Once you're more familiar with the interface, follow these steps to set up a prefix for GW2:

  1. Open the "Prefixes" tab.
  2. Click on the wand icon to create a new prefix.
  3. These are the settings that I changed when creating my prefix:
    1. General Tab
      1. Name: Guild Wars 2
      2. Prefix Path: /home/user_name/.guildwars2
        1. Obviously, you should replace "user_name" with your system user name here.  Also, using ~ to represent your home directory doesn't work - the path needs to be absolute.
      3. Architecture: win32
    2. Wine Paths Tab
      1. NOTE: My install path for the manual installation of Wine is ~/.wine_versions/wine-git.  This is the path that I will be using here.  Replace it with whatever you used (again, using an absolute path).
      2. Bin: /home/user_name/.wine_versions/wine-git/bin/wine
      3. Server: /home/user_name/.wine_versions/wine-git/bin/wineserver
      4. Loader: /home/user_name/.wine_versions/wine-git/bin/wine
      5. Libs: /home/user_name/.wine_versions/wine-git/lib
  4. Switch to the Programs tab.
  5. Under your new prefix, there should be a "system" folder.  Click on that, then double click on "winecfg".  Set your Windows version to Vista.
  6. In the same "system" folder, you can see a "regedit" program.  Open that.
  7. Look for the key: HKEY_CURRENT_USER->Software->Wine->Direct3D.  If it doesn't exist, create it.  Then select the Direct3D key.
  8. Right click in the panel on the right and select "New->String Value".  Your string value should be named "VideoMemorySize", and its value should be the amount of dedicated RAM (in MB) your video card has (mine has a gigabyte, so I set the value to 1024).

If you would rather manage your wine prefixes manually, I'm going to assume that you know how to do it.  If you don't, you probably should study it for a while, because it's very easy to forget certain steps when running games in custom prefixes.  Setup and installation are easy, but it takes about three extra steps to run the game, and it's very easy to forget one of those.  This is the reason that I use q4wine.

Install the Game

Your options are:

  1. Install from disc by blindly clicking on a blank window.
  2. Install using the patcher, after either copying it from the disc or downloading it.

Installer From Disc

These steps are fairly simple, but require you to blindly mouse around until your cursor changes.  Installing using the patcher is simpler, but will take a bit longer, since you have to patch some more.

  1. Insert and mount the disc.  This can be done through q4wine, if you're using that - they even have a screenshot showing the mount options.
  2. Run the setup file.  You can see the "Run..." option for q4wine (used to run a file once without making a launcher for it) in the same screenshot above.
  3. Unless things have changed recently, the window that pops up will be blank.  However, your mouse cursor will change when you mouse over the "Install" button.  So move your mouse around the window until your cursor changes to a hand, then click.
  4. Another window will pop up, asking you where to install the game to.  Make your selection.
  5. Once you've chosen your installation location, the blank window will ... well, still be blank.  But it will be installing the game!  So just give it a while.  It should either eventually crash or show you some kind of success dialog.  If it's still sitting there after more than a half hour, it's probably done and you can safely kill it.
  6. Launch the file named Gw2.exe in your installation directory (in q4wine, you can make a "Games" sub-directory for your prefix, click on the sub-directory, then right click in the blank space and select "New" to add a launcher for the game - see the same screenshot as above for reference).  The launcher will start to patch.
  7. Here's the fun part: the patcher crashes every (roughly) 10,000 files!  You get to sit there, waiting for an error message, running the game multiple times over the course of 15GB of data.  Each time it crashes, you will need to start it again.  The progress bar will reset to 0%, but you should notice the number of files remaining decreasing each time.

Installing From Patcher

This is pretty darn simple, but you're going to install the entire game by patching, so it will take longer. 

  1. Find the file Gw2.exe.
    1. The installer disc should have this file somewhere, although it might be hidden in compressed files (*.cab or something).  I haven't checked as of the time of this writing.
    2. You can probably download it from the Guild Wars 2 website, at least in their forums or something.
    3. If you have a friend who has the game, ask them to send it to you.  Heck, you can just copy the entire game directory from them so that you're already all patched up.  Honestly, this is the best option if you can do it, but it's 15GB of data, which can be hard to copy across systems.  My suggestions: SSH, 16+GB flash drive (formatted something that supports files larger than 4GB [so not vfat/fat32]), or external hard drive (again, formatted something that supports files larger than 4GB).  Personally, when I transfered my copy to a friend's (Windows) computer, I formatted NTFS and zipped my GW2 folder to a 16GB flash drive - it fit with a couple hundred MB to spare.
  2. Put the Gw2.exe file in the directory where you want to install GW2.
  3. Follow steps 6 and 7 above.


 
Making GW2 Run Well

At the time of this writing, Guild Wars 2 just plain doesn't run as fast in Wine as it does in Windows.  You can get halfway decent performance out of it, but, especially in large events and WvW, you will simply get (often significantly) better performance in Windows.

However, You can make things a little better for yourself. Feel free to tinker and comment - I will include other suggestions here, as well as whether or not they worked for me.

  1. I've found that I get the best performance when setting the Windows version to Vista in winecfg. I'm not sure why this is, and I'm not sure that everyone will have the same experience as me. Some people in the comments have mentioned that XP gives them better performance. Please post your findings in the comments.

  2.   If you use SLI, turn it off. I've tried multiple SLI modes and, while some of them help in certain areas of the game, all of them cause performance drops in others - and we're going for steady FPS over small bursts of high FPS, here (right?).  Furthermore, just setting SLI to "on" or "auto" actually cuts performance down like mad.  I went from a steady 25 FPS down to 5 when I allowed the nvidia drivers to choose for me.

  3.   One of the biggest areas where Windows users have a huge advantage over us Wine users (actually, this seems to be almost the entirity of our problem) is multi-core processing. GW2 is built to take advantage of quad core processors. GW2 running in wine for some reason ignores multiple cores and only makes use of one.

    So what can we do about this? To be honest? Spend money or overclock. Again, your mileage will probably vary here; but with my Phenom II x4 965 CPU, I gain about 5-10 FPS per 200 MHz increase in core frequency. I managed to run my CPU at 4.0GHz for around 30 minutes before my computer crashed (stock clock is 3.4 GHz) and I was getting 45-50 FPS in normal play, 30 FPS in large events and WvW (I didn't get very far, though ... that was not a stable overclock).

    So in the end, your best bet is a CPU upgrade or bumping up your core clock speed. But if you do buy a CPU upgrade, just remember that the speed of a single core is more important than how well all the cores work together (i.e. intel CPUs will dominate here).

  4. Somewhat related to the above point, you should make sure that your CPU is using the "Performance" frequency scaler. How you do this will be dependent on how you install your kernel, which graphical interface you use, and which distro you're on.
    • Custom kernel: If you build your own kernel, you can find the settings for your default CPU frequency scaler here (in menuconfig or xconfig):
      Power management and ACPI options
       -> CPU Frequency scaling
         -> Default CPUFreq governor
    • E17: If you're using the Enlightenment DR17 window manager, there is a module called "cpufreq" which shows you (using a speedometer) the current speed of your CPU, assuming you have the right ACPI libraries installed. Put the gadget on your desktop or in a bar and you can click on it to set your frequency governor (I don't remember if it's right or left click - I haven't bothered to get it working because I just set the default governor when building my kernel).

    • Debian: The debian team apparently has a guide to set this up.

    • Gentoo: As usual, Gentoo's wiki article on the subject goes very in depth.

    • Arch: May as well toss in the Arch linux wiki article on the topic, too.

    • If none of these work for you, use your google skills. Something like " cpu frequency scaling" should get you some results.

  5. NVIDIA Driver Version 310.14+
      If you have nvidia drivers version 310.14+, you can force a flag for threaded optimizations. It's currently in *early* beta, and will only work with pthreads. This means that we will be enabling a very early, still-in-development feature of nvidia's drivers, and that we will have to trick Guild Wars 2 into using pthreads. It doesn't appear to solve world hunger, but I am noticing more stable performance (situations that lower me below 20 FPS are very rare, now). 

    To enable threaded optimisations, we're going to have to set a bunch of environment variables before we kick off the game. This is easy on the command line:

    $ export WINEDEBUG=-all # debug output really screws things with threaded optimisations, so turn them off
    $ export LD_PRELOAD="libpthread.so.0 libGL.so.1"
    $ export __GL_THREADED_OPTIMISATIONS=1 # Note: Here (and in all other places where this flag is used), the word "optimisations" can also be spelled "optimizations".  The original spelling of the word works for me, but the American spelling is what's in the documentation for the drivers, and there have been reports that the original spelling doesn't always work.
    $ cd /path/to/GW2/
    $ /path/to/wine/version/bin/wine ./Gw2.exe -dx9single

    In q4wine, you will need to follow these steps:
    1. Open the "Prefixes" tab.
    2. Right click on your Guild Wars 2 prefix.
    3. Click on "Edit Prefix Settings".
    4. Open the "Advanced" tab.
    5. You should see a long string with plenty of percent symbols. You're going to want to add a couple of options before "%WORK_DIR%". Namely, add the following, making sure there's a space between the final "1" and "%WORK_DIR%": LD_PRELOAD='libpthread.so.0 libGL.so.1' __GL_THREADED_OPTIMISATIONS=1
      Your final line should look something like this:
      %CONSOLE_BIN% %CONSOLE_ARGS% %ENV_BIN% %ENV_ARGS% /bin/sh -c "LD_PRELOAD='libpthread.so.0 libGL.so.1' __GL_THREADED_OPTIMIZATIONS=1 %WORK_DIR% %SET_NICE% %WINE_BIN% %VIRTUAL_DESKTOP% %PROGRAM_BIN% %PROGRAM_ARGS% 2>&1 "

Pitfalls that everyone falls into when trying to tune their performance:

  1. -dx9single isn't as huge of an issue as its name implies. Believe me, I made the same mistake. But we can technically run GW2 without the -dx9single flag; it just causes massive instability. And it turns out that there really just isn't much of a benefit.

 

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

Current best results on gentoo?
by Paul on Thursday March 27th 2014, 14:00
Hi,

what wine version with what patches gives the best results on gentoo currently? (And where can I get these patches?) I can't find the CSMT patches for any wine version greater than 1.7.1, but I read that there are some.

[post new] [reply to this]

automate recover from loader crash
by Oded Arbel on Tuesday March 25th 2014, 18:11
Lately the loader has been unreasonably crashing for me, so I wrote this small script to monitor for crash and relaunch automatically. This script works with the PlayOnLinux launcher and also takes care of the annoying POL "wine seems to have crashed" dialog, but it should be fairly easy to modify it for other set ups. Also note that this script relies on xwininfo, which may not be installed by default - check your distribution for installation instructions.

You'd need to edit the POLshortcut variable to be the name of the shortcut for the game in your PlayOnLinux set up.

#!/bin/bash
POLshortcut="Guild Wars 2"
( while true; do
sleep 1
if (xwininfo -tree -root | grep -q '"Gw2.exe": ("Gw2.exe" "Wine")'); then
killall Gw2.exe
kill $(ps axfwww | grep playonlinux/python | grep -v grep | awk '{print$1}')
killall nc
fi
done ) &
pid=$!
while true; do
/usr/share/playonlinux/playonlinux --run "$POLshortcut" && break
done
kill $pid

[post new] [reply to this]

State of the game
by J V on Sunday March 23rd 2014, 17:55
tl;dr:
Textures are low, shadows and reflections are off. Rest of the settings are as high as you want.
Performance is lower than windows, but playable.


Patches:
* CSMT patches: github.com/stefand/wine
Fixes bug 29872 (Graphical corruption in preview/changing gear)
Nearly doubles fps
Might hog CPU more than you like

* git revert 76bbf106a28c4caa82873e8450bde7d4adc765bf
Fixes mouse walling


Tweaks:
* dx9single flag (eg `wine Gw2.exe -dx9single`)
Fixes invisible launcher
CSMT performance improvement doesn't take effect without it

* Patcher crash
Patcher crashes every few thousand files. Just keep restarting it till it's done


Ingame settings:
* Textures: Low
Workaround for the 32bit Gw2 bug. Gw2 leaks memory like a sieve held upside down.
If it goes over 4G ram usage on a 32bit system it will crash.
Anet's solution is to tell people to get a newer system or lower their textures.
Since wine triggers this bug in both 32bit and 64bit builds we have no choice in the matter.

* Shadows, reflections: None
A good double FPS in certain areas

* Character model limit/quality
Depends on your system.
Mine's fairly beefy and I still prefer lowest/low as a nice balance between performance and quality

* Remaining settings
Maximum quality will work with no performance penalty (Unless by some miracle you are GPU locked)

[post new] [reply to this]

Out of Memory crash
by Txema on Thursday February 13th 2014, 17:55
Is anyone getting this crash?

I've been looking for weeks and today i found this bugs.winehq.org/show_bug.cgi?id=34342

Anet says that it's a problem of 32bits OS (forum-en.guildwars2.com/forum/support/tech/Out-of-memory-crash-1/first#post138013) but i have wine 64bits and Linux 64bits.

Any idea?

[post new] [reply to this]

Change of distro
by Pawel Sarkowicz on Saturday February 8th 2014, 13:37
I recently changed my distribution(to gentoo), having guild wars 2 running fine with playonlinux. But now when I choose my character I get this crash:

*--> Crash = m_pages.x*m_pageSize.x*sizeof(float)*2
File: ..\..\..\Engine\Map\Shadow\Windows\WinShadow.cpp(240)
App: Gw2.exe
Pid: 66
Cmdline: -dx9single
BaseAddr: 00400000
ProgramId: 101
Build: 29675
When: 2014-02-08T19:38:22Z 2014-02-08T14:38:22-05:00
Uptime: 0 days 0:01:58
Flags: 0

Any suggestions?

[post new] [reply to this]

Stefan's build
by Txema on Friday February 7th 2014, 18:22
Anyone knows how to compile wine with the modifications of Stefan (github.com/stefand/wine/) on 64bits?

I get this error:

config.status: creating dlls/acledit/Makefile
config.status: creating libs/port/Makefile
make[1]: Entering directory '/home/chema/git-wine-stefan/libs/port'
make[1]: Nothing to be done for 'all'.
make[1]: Leaving directory '/home/chema/git-wine-stefan/libs/port'
config.status: creating libs/wine/Makefile
make[1]: Entering directory '/home/chema/git-wine-stefan/libs/wine'
version=`(GIT_DIR=../../.git git describe HEAD 2>/dev/null || echo "wine-1.7.10") | sed -n -e '$s/\(.*\)/const char wine_build[] = "\1";/p'` && (echo $version | cmp -s - version.c) || echo $version >version.c || (rm -f version.c && exit 1)
gcc -shared -Wl,-soname,libwine.so.1 -Wl,--version-script=./wine.map c_037.o c_10000.o c_10001.o c_10002.o c_10003.o c_10004.o c_10005.o c_10006.o c_10007.o c_10008.o c_10010.o c_10017.o c_10021.o c_10029.o c_1006.o c_10079.o c_10081.o c_10082.o c_1026.o c_1250.o c_1251.o c_1252.o c_1253.o c_1254.o c_1255.o c_1256.o c_1257.o c_1258.o c_1361.o c_20127.o c_20866.o c_20932.o c_21866.o c_28591.o c_28592.o c_28593.o c_28594.o c_28595.o c_28596.o c_28597.o c_28598.o c_28599.o c_28600.o c_28603.o c_28604.o c_28605.o c_28606.o c_424.o c_437.o c_500.o c_737.o c_775.o c_850.o c_852.o c_855.o c_856.o c_857.o c_860.o c_861.o c_862.o c_863.o c_864.o c_865.o c_866.o c_869.o c_874.o c_875.o c_878.o c_932.o c_936.o c_949.o c_950.o casemap.o collation.o compose.o config.o cptable.o debug.o fold.o ldt.o loader.o mbtowc.o mmap.o port.o sortkey.o string.o utf8.o wctomb.o wctype.o version.o ../../libs/port/libwine_port.a -ldl -lm -o libwine.so.1.0
/usr/lib/gcc/x86_64-pc-linux-gnu/4.8.2/../../../../x86_64-pc-linux-gnu/bin/ld: la arquitectura i386 del fichero de entrada `c_037.o' es incompatible con la salida i386:x86-64
/usr/lib/gcc/x86_64-pc-linux-gnu/4.8.2/../../../../x86_64-pc-linux-gnu/bin/ld: la arquitectura i386 del fichero de entrada `c_10000.o' es incompatible con la salida i386:x86-64
/usr/lib/gcc/x86_64-pc-linux-gnu/4.8.2/../../../../x86_64-pc-linux-gnu/bin/ld: la arquitectura i386 del fichero de entrada `c_10001.o' es incompatible con la salida i386:x86-64
/usr/lib/gcc/x86_64-pc-linux-gnu/4.8.2/../../../../x86_64-pc-linux-gnu/bin/ld: la arquitectura i386 del fichero de entrada `c_10002.o' es incompatible con la salida i386:x86-64
/usr/lib/gcc/x86_64-pc-linux-gnu/4.8.2/../../../../x86_64-pc-linux-gnu/bin/ld: la arquitectura i386 del fichero de entrada `c_10003.o' es incompatible con la salida i386:x86-64
/usr/lib/gcc/x86_64-pc-linux-gnu/4.8.2/../../../../x86_64-pc-linux-gnu/bin/ld: la arquitectura i386 del fichero de entrada `c_10004.o' es incompatible con la salida i386:x86-64
[...]

thanks.

[post new] [reply to this]

Yet Another Wine Build
by Kaede on Sunday February 2nd 2014, 18:51
I just thought I'd throw this out here in case anyone is interested. We maintain a packageless build of Wine with all of the GW2 and CSMT patches included as well as a launcher that works around most coveats and makes editing of the configuration much easier. Since it is based upon wine-multimedia, it also supports PulseAudio.

You can find it at projects.boxedfox.org/winegw2/.

[post new] [reply to this]

Awesomium for 1.7.7?
by Jen on Wednesday December 4th 2013, 8:44
So the latest Awesomium patch I'm seeing is for 1.7.1. Does this mean that they've added said patch into the current versions of WINE and it's not needed anymore?

[post new] [reply to this]

GuildWars 2 on openSUSE 13.1
by rob on Sunday November 24th 2013, 19:08
Tested with openSUSE 13.1 x86_64 and KDE 4.11.2
kernel 3.11.6-4
CPU AMD PhenomII 965
12GB memory
nvidia GTX560Ti

Prerequisites:

Removed noveau driver and installed nvidia 330.20 binaries
Removed Wine 1.7.2, wine-mono, wine-gecko
Added repository to download.opensuse.org/repositories/Emulators:/Wine/openSUSE_13.1/
Installed Wine 1.7.6-293.1, wine-mono 0.0.8-1.2, wine-gecko 2.24-43.1

Used the following script to execute game:

#!/bin/sh
# debug output really screws things with threaded optimisations, so turn them off
export WINEDEBUG=-all
export LD_PRELOAD="libpthread.so.0 libGL.so.1"
# Note: Here (and in all other places where this flag is used), the word
# "optimisations" can also be spelled "optimizations". The original spelling
# of the word works for me, but the American spelling is what's in the
# documentation for the drivers, and there have been reports that the original
# spelling doesn't always work.
export __GL_THREADED_OPTIMISATIONS=1
export __GL_THREADED_OPTIMIZATIONS=1
cd ~/Games/GuildWars2
wine ./Gw2.exe -dx9single


GW2 ran decent with the following in-game graphic settings:

Fullscreen 1440x900
Animation: medium
Antialiasing: None
Environment: Low
LOD Distance: Low
Reflections: Terrain & Sky
Textures: medium
Render Sampling: native
Shadows: none
Shaders: Low
Postprocessing: low
Model Limit: medium
Model Quality: medium
All check-boxes unchecked

No additional Wine patching was required for accessing trading post. No "mouse-wall" behavior. Achieved 20-30fps in all world areas with no additional CPU or system optimizations. Note that fps can dip below 20 during WvW zerg encounter or lots of people in Lion's Arch.

[post new] [reply to this]

Wine Registry
by LukeFilewalker on Thursday October 31st 2013, 14:51
Hello;

I have a problem with the wine registry, version 1.5-28, using POL. In HKEY_LOCAL_MACHINE/HARDWARE/Description/System/CentralProcessor, set my AMD FX-6100 3,3Ghz as a Intel Pentium 4, 2,4Ghz. Recognize the six cores, but I don't know if this cause problems with the game, can I fix this, thanks a lot.

[post new] [reply to this]

Launcher Issues
by Erich Fischer on Saturday October 26th 2013, 14:04
Hey Guys,

Before I start, you all are the best! I'd be lost without all your great insight and advice. Now, onward.

I've been having a ton of issue with the launcher lately, all graphics related. Sometimes it would not come up and freeze my screen, other times it would show the initial downloading launcher data page an hang, and on rare occasions it would get to the login/pw an freeze. Each time the X session would lock up, though the virtual terminals could be accessed just fine, and killing the launcher freed up the X session.

My solution: This may be sort of terrible way to go about it, but I opted to just not display the launcher at all. I passed the arguments -email [login email] -password [pw] -autologin -nopatchui so it updates (note, there's no visual way to know when it's updating, and how that process is going, but you can check to see if the .dat file is changing size), and then launches directly in to the game, which for me works fine (well, with all the normal performance issues). Hopefully if anyone else is having this problem this will work well enough for them, as it has me.

[post new] [reply to this]

PPA builds are deliberately behind the latest wine version
by Forest on Wednesday October 16th 2013, 14:05
Some of you may have noticed that my PPA doesn't offer a patched version of the latest wine release (currently 1.7.4). This is because CSMT patches are not available for the latest releases, and I want my latest PPA builds to give the best performance possible in Guild Wars 2. I plan to update my PPA when suitable replacement patches become available, or when command stream functionality makes its way into the official wine distribution. Recent activity on wine-devel hints that the latter is pretty likely to happen before long.

As far as I know, the builds I offer are still the best ones available for Guild Wars 2 on Ubuntu. They live here:
launchpad.net/~foresto/+archive/winepatched/

[post new] [reply to this]

Up to date patches?
by J V on Wednesday September 4th 2013, 7:44
The experimental opengl threading patch here: www.winehq.org/pipermail/wine-devel/2013-September/101106.html

Improves performance in LA with max settings by almost 80%!

Unfortunately this patch applies to 1.7.1, I can't find updated mouse and awesomium patches for this version. Can someone give me a hand?

PS: No more crashing on text entry w/o -dx9single flag any more

[post new] [reply to this]


by kimyung on Monday August 19th 2013, 17:52
Hey all I am having the issues in GW2 Wineskin with white fog/rain and other graphical errors that block my vision. Also the trade post does not work. I have however got the mouse to work properly with a custom engine I downloaded. As for the patches for Trade Post, I am not sure how to use them to make it work, and for everyone talking about ways to increase fps and remove graphic errors by messing with winetricks and stuff I am so noob at it and can;t figure it out for the life of me. Also a new wineksin came out but i tried it and no luck with any of these issues. I use a geforce gt 33m with core i5 2.53 ghz with 4gb ram.

www.facebook.com/InginTipsCaraCepatHamil
tipscaracepathamill.blogspot.com/2013/06/CaraCepatHamil.html

[post new] [reply to this]

Trading Post not working
by Lith Maethor on Monday August 12th 2013, 0:16
I just downloaded the latest source from git, applied the partial awesomium patch (it went through without even a warning), made sure i was using the correct prefix and all that... but the Trading Post still won't show up.

I would appreciate any suggestions...

[post new] [reply to this]

HUNK #3 failed in schannel_gnutls.c
by pfftzo on Tuesday August 6th 2013, 11:58
Following the tutorial above for compiling Wine with the Awesomium-patch I get

HUNK #3 failed in schannel_gnutls.c

when patching.
Hunks 1 and 2 succeed with offset in this file, all the previous hunks are applied completely fine.

[post new] [reply to this]

Assertion: !m_buffs.Find(buffId)
by J V on Wednesday July 10th 2013, 6:59
Assertion: !m_buffs.Find(buffId)
File: ..\..\..\Game\Combat\Cli\CmbtCliBuff.cpp(338)
App: Gw2.exe
Pid: 13
Cmdline: -dx9single
BaseAddr: 00400000
ProgramId: 101
Build: 20681
When: 2013-07-10T11:51:09Z 2013-07-10T13:51:09+02:00
Uptime: 0 days 0:02:17
Flags: 0

Happens every time I'm in the obsidian sanctum after less than a minute.

Any ideas?

[post new] [reply to this]

Can't even start the game anymore
by Sir Robin on Monday July 8th 2013, 7:16
I didn't try running Guild Wars 2 in a while because since a patch sometime around May it kept freezing and rebooting my computer (seemed like overheating, but no other game caused the error).

I upgraded to a newer version of my OS yesterday and tried launching the game to see if it works again, but I don't even reach the launcher: When I start it in PlayOnLinux, I get only the grey "Downloading _ KB" text and some fancy noise that slowly fills the screen if it actually succeeds in downloading something, but almost always it stays at 0 KB and crashes.
When I run it with (unpatched) wine 1.6rc4 (hope I got the number right) without using PlayOnLinux, the only difference is that the launcher picture is actually shown instead of the noise, but otherwise it does the exactly same things.

Could I be missing some non-wine/windows packages needed to run it (that I forgot to reinstall this time)? I'm pretty sure with PlayOnLinux at least the launcher ran out-of-the-box back then.

console-output:

fixme:heap:HeapSetInformation 0x1d7a000 0 0x33fd88 4
fixme:process:SetProcessDEPPolicy (1): stub
fixme:thread:SetThreadStackGuarantee (0x3858e9d0): stub
fixme:wincodecs:PngDecoder_Block_GetCount 0x18d4b0,0x38e8e4c8: stub
fixme:winsock:WS_getsockopt WS_SO_CONNECT_TIME - faking results
fixme:wincodecs:PngDecoder_Block_GetCount 0x18dc28,0x38e8de18: stub
fixme:wincodecs:PngDecoder_Block_GetCount 0x18dc08,0x38e8de18: stub
fixme:win:EnumDisplayDevicesW ((null),0,0x38e80b88,0x00000000), stub!
fixme:wbemprox:wbem_services_CreateInstanceEnum unsupported flags 0x00000030
fixme:wbemprox:enum_class_object_Next timeout not supported
fixme:win:EnumDisplayDevicesW ((null),0,0x38e7fa08,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x38e7f7f8,0x00000000), stub!
fixme:ddraw:ddraw7_Initialize Ignoring guid {aeb2cdd4-6e41-43ea-941c-8361cc760781}.
fixme:devenum:DEVENUM_ICreateDevEnum_CreateClassEnumerator Category {33d9a760-90c8-11d0-bd43-00a0c911ce86} not found
fixme:devenum:DEVENUM_ICreateDevEnum_CreateClassEnumerator Category {33d9a761-90c8-11d0-bd43-00a0c911ce86} not found
fixme:devenum:DEVENUM_ICreateDevEnum_CreateClassEnumerator Category {cc7bfb41-f175-11d1-a392-00e0291f3959} not found
fixme:devenum:DEVENUM_ICreateDevEnum_CreateClassEnumerator Category {cc7bfb46-f175-11d1-a392-00e0291f3959} not found
fixme:d3d:debug_d3dformat Unrecognized 0x434f5441 (as fourcc: ATOC) WINED3DFORMAT!
fixme:d3d:wined3d_get_format Can't find format unrecognized (0x434f5441) in the format lookup table
fixme:imm:ImmDisableTextFrameService Stub
fixme:wtsapi:WTSRegisterSessionNotification Stub 0x4006c 0x00000000
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:avrt:AvSetMmThreadCharacteristicsW (L"Audio",0x447ce9b8): stub
fixme:win:EnumDisplayDevicesW ((null),0,0x38e809e8,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x38e80be8,0x00000000), stub!

[post new] [reply to this]

Can't buy items or post that I want to buy some
by Björn Bidar on Sunday May 12th 2013, 9:33
Like the title says, when I try to buy an item gw2 says there's an error. When I try to post that I want to buy an item it says can't access to the login server. Using wine 1.5.28 on arch linux.

[post new] [reply to this]

Mouse look hits wall in 1.5.29
by dolphinling on Tuesday April 30th 2013, 19:55
With 1.5.29, if I click and drag to rotate the camera, it will at some point stop rotating. After reverting to 1.5.28, the problem is gone. Does anyone else see this?

[post new] [reply to this]

Performance Regression
by Mike on Tuesday April 16th 2013, 17:43
I have been trying the latest Wine with GW2 each time a new release is made. I always return back to to 1.5.14 because the performance is much better. Has anyone else noticed a performance regression with current Wine versus 1.5.14?

[post new] [reply to this]




   << Back

Page loaded in 0.05674 seconds.