Talk:Guild Wars on Wine
Wine 1.3.0[edit]
It work. :) Did not had time to test more then start Gw and load to guild hall tho. --Bob 05:25, 5 August 2010 (UTC)
My PC blew up[edit]
Okay, you know that grease you put between the processor and the heat sink? Apparently it's not okay to replace it with toothpaste. Long story short, my windows PC is down and until I can find a new one I need to use Wine. Everybody says GW works "flawlessly" on it, so I figure I must be doing something wrong. When I log in, the screen gets all warbly and looks like a bunch of glass tiles, there are graphical distortions everywhere and even though I'm getting 60+ frames per second, the scene still doesn't move smoothly. I've got the (cruddy) official ATI drivers installed, but it's as bad with those as it is with the generic open-source mesa driver. –Jette 03:47, 12 August 2010 (UTC)
- Let's start with some versions: What version of Linux (name and number), of Wine, and of video drivers? I'm going to assume for my sanity that you're joking about how you blew up the windows PC. - Tanetris 04:06, 12 August 2010 (UTC)
- Yeah, I was joking. I've got Fedora 13 installed here, wine-1.2 and Catalyst v 10.7. Appears to be the latest, but I could be wrong. –Jette 04:33, 12 August 2010 (UTC)
- There are 2 possible problems in this situation that I can think of:
- Your graphics drivers are not installed or up-to-date (but I think Catalyst v 10.7 is the latest but I'm an nVidia guy so I'm not entirely sure).
- Your winecfg hasn't been set to support DirectX8.
- Unfortunately Guild Wars is one of those programs where an older Direct X version may be required to run it, and thankfully Wine comes with all of their latest. So try this command to load up Guild Wars:
WINEDEBUG=-all wine "C:\Program Files\Guild Wars\Gw.exe" -dx8
- If that works, but you don't see a login screen or if it's still as bad as you describe it, try it with "-noshaders" as such:
WINEDEBUG=-all wine "C:\Program Files\Guild Wars\Gw.exe" -dx8 -noshaders
. --Than 22:03, 13 August 2011 (UTC)- Wine 1.2.what? 1.2.3 is the current latest stable version (or you could get the latest development version, which is 1.3.26 atm, but that's up to you). A quick glance through the WineHQ AppDB page mentions a similar problem with an ATI video card being resolved by unchecking "Allow Pixel Shader" in winecfg (under the Graphics tab), so you might also try that before screwing around with command line arguments. - Tanetris 22:29, 13 August 2011 (UTC)
- I appreciate you trying to help, but you misread the date. I posted this almost exactly a year ago, not yesterday. I got a PC to run Winderp on again since then. –Jette 01:19, 14 August 2011 (UTC)
- Well...crap. LoL. Surprising that you still visit the Wiki though. ^.^ Oh well, if anything use the latest Wine (1.3.26). Stable is 100% working, and "unstable" sounds dangerous but is still fine. Anyways, we hope you change to a Linux distro soon because Slackware kicks ass. ^^ Than 03:59, 15 August 2011 (UTC)
- There are 2 possible problems in this situation that I can think of:
- Yeah, I was joking. I've got Fedora 13 installed here, wine-1.2 and Catalyst v 10.7. Appears to be the latest, but I could be wrong. –Jette 04:33, 12 August 2010 (UTC)
Guild Wars and OSX[edit]
So I've been using WineBottler[1] (essentially wine + a frontloader/configuration program) to run Guild Wars under OSX 10.6 and it has been super-smooth; the only concession I made to performance was turning off vsync. However, there is one issue that's come up, and my digging (specifically on the CodeWeavers/Crossover site[2]) uncovered it's a driver-workaround issue that only seems to crop up in certain EOTN zones. Turning "Texture Quality" in Options/Graphics to "Medium" seems to have resolved the issue for me, and it's probably best to have it at that setting while you're adventuring in EOTN zones (dungeons in particular). If you're using default OSX hotkeys you'll probably also want to disable the Exposé and Dashboard hotkeys (F9-F12) at least while you're playing. --nunix
Chat window input bug[edit]
This may or may not be a wine bug but seeing as it doesn't appear anywhere else I'll assume it is.
At semi-random, when changing workspace or otherwise changing focus away from the game, the chat window will stop accepting input. Pressing shortcuts to change channel, auto reply, etc all work fine, including the slash shortcut. Beyond that any attempt to type into the input fails. All other keyboard input works fine so this may be a GW error, but I doubt it appears in windows as I couldn't find anything about it through google.
Zoning appears to fix this problem.
Other than this the game performs (Almost) flawlessly. Is there something in GW a newbie like myself may have missed that could be causing it? Debian squeeze, 9500gt, wine 1.3.16, gnome, compiz
- I'm unfamiliar with Compiz and think Gnome is crap, but your first step needs to be isolating the cause. It could be a Wine bug or a bug with some other software in your system. First, try using Control-Alt-1 to switch to your first terminal. This will make your windows and stuff disappear, but it won't close anything; it'll all be there when you get back. Wait a few seconds, then switch back to your desktop with Control-Alt-(terminal X is using). On my system and most others I've used, that equates to Control-Alt-7 (and it won't hurt anything if you get it wrong; just keep trying numbers). Then, see if GW input still works.
- If it doesn't, it probably has nothing to do with your desktop environment or silly 3-D effects. If it does still work, trying running GW in an alternate X environment. Gnome is like a cancer; it spreads and infects every aspect of your poor system, so you'll have to kill gdm (Gnome Display Manager) to run anything else. Unfortunately, like a vampire, gdm comes back if you just kill it, so you have to go through some convoluted process to tell it to stop. I think it's something like
# /etc/init.d/gdm stop
but as I said I don't use it, so I don't know. Then you can use some age-old window manager that lacks Compiz or other silliness. That's an essay in itself, so just Google it and figure it out. For testing purposes, I suggest "twm" because it's installed on basically everything. It lacks nice shiny things like start menus, so you'll have to run GW via wine via the command line. After you get it running, switch to terminal one (Ctrl-alt-1), wait a minute, then switch back to make sure it's still working. If it's still working, then you can solve your problem by running two X servers at once, and can switch between them using Ctrl-alt-7 and ctrl-alt-8, or something. This is even more complicated than the original twm thing, and, again, requires an entire article to elaborate on. Google it.
- Isn't Linux fun? –Jette 19:54, 24 May 2011 (UTC)
- I find your distaste for gnome amusing. I've dabbled with openbox and kde but it seems better for me.
- Anyway, Switching tty didn't effect it, but it was pure luck that I was able to discover this as I said this bug appears randomly. I still believe it's a problem with the window manager not releasing text focus (The GW window has focus but some other window is taking the textual input) I suspect firefox to be the cause, will post back if this bug occurs again.
- Firefox could be it. A friend of mine said Firefox was stealing input on his Windows PC some of the time, though it didn't have anything to do with GW. If you think it's a problem with the window manager, maybe try another one to see if it improves. There are a number of relatively lightweight ones out there that I think get associated with the display manager automatically in Gnome.
- Anyway, Switching tty didn't effect it, but it was pure luck that I was able to discover this as I said this bug appears randomly. I still believe it's a problem with the window manager not releasing text focus (The GW window has focus but some other window is taking the textual input) I suspect firefox to be the cause, will post back if this bug occurs again.
- I don't really have a problem with Gnome so much as desktop environments and titanic software suites in general. –Jette 20:43, 26 May 2011 (UTC)
- I'm pretty sure it's firefox, consider this closed unless I bring it back up. (By the way, the gnome package itself isn't installed here cause I stripped certain packages from it ;D)
- Gnome is a metapackage. Debian's packaging system is kind of weird. My point was that if you like even one program, you have to install pretty much all of them. I like evince more than mupdf when I need to use the PDF reader one-handed for... various reasons, but I have to keep 200MiB+ of useless Gnome libraries and other junk installed just to get the reader to run. –Jette 01:15, 27 May 2011 (UTC)
- I'm pretty sure it's firefox, consider this closed unless I bring it back up. (By the way, the gnome package itself isn't installed here cause I stripped certain packages from it ;D)
- Well yes but this applies to all systems (Except maybe gentoo)
- Problem: It's not firefox. Just got this problem and killing firefox didn't help.
- Gentoo has the same problem, I'd imagine. It probably has it worse, since you have to download all the requisite libraries and other associated content to compile them, an act which tends to be recursive. I never understood that whole thing, it just seemed like masochism to me. I like their USE flags and some of the other features they have, but the "hurr source only!" ideology is downright self-flagellant.
- I haven't tried to play GW on Wine in months, since I have a working Windows PC to play games on. Have you tried updating (or, alternately, rolling back) anything related to the problem? I remember X got updated this one time and sometimes windows wouldn't accept keyboard input when I swapped, and that was with real X programs. Fake X programs in Wine are probably even more buggy. The only answer I can think of is to run a separate X server that you can swap to without "losing focus." It will take some extra memory, but nothing that a decent PC can't handle. –Jette 20:56, 29 May 2011 (UTC)
- No, I'm new. And other than this bug and wierd-looking shadows there have been no bugs that pop up more than once a week.
- Problem: It's not firefox. Just got this problem and killing firefox didn't help.
Cr48 (Chromebook pilot machine)[edit]
I installed fusionos as a test from neowin on my CR48 Chrome Pilot chromebook after trying to get GW with ubuntu and with the tips here it appears like it might actually function enough that I can possibly play. I know its too low of a machine to ever do something like a DoAsc but I will probably be able to do a VQ or something that doesn't require much thought. Thanks! Devi Talk 15:15, 3 June 2011 (UTC)
Can't load GW on Wine since 23 Feb 2012[edit]
Recently, I've been unable to load Guild Wars using Wine on my Mac. The initial loading screen appears and the load bar reaches 100%, but then the program just terminates without any messages. I've tried to load the game several times and restarted the Mac several times. Random Weird Guy 10:30, 25 February 2012 (UTC)
- There was a recent authentication change, which might have something to do with it, although that seems unlikely. ANet doesn't support Wine or other non-Windows platforms in any way, so your best bet is reporting it to the Wine people. An "ArenaNet.log" and/or "Crash.dmp" file might appear in your Guild Wars folder, which you should include with your report. I don't know what OS your version of Wine is set up to emulate, so on Windows XP, it's "C:\Program Files\Guild Wars"; on Vista and Windows 7 it's "%USERPROFILE%\Documents\Guild Wars". Crash.dmp is a minidump file, ArenaNet.log contains various debugging information. Neither of them contain any personally identifiable information. –Jette 15:35, 25 February 2012 (UTC)
- Same problem on Linux since the same date (debian testing, nvidia drivers, tried crossover and wine).
- ArenaNet.log says:
- App: Gw.exe
- Fatal error (2): Exception
- When: 2/24/2012 09:58:04
- File: u:\code\arena\core\platform\windows\exe\error\exeerror.cpp(419)
- ---- --The preceding unsigned comment was added by User:86.66.211.2 .
- I got the exact same error in the log. Random Weird Guy 16:09, 25 February 2012 (UTC)
- With the recent "security changes" the client will now extract and load a DLL into the game directory. Make sure that the client has access to write the directory that it is running from or try launching with the old auth argument. 85.195.86.54 16:57, 25 February 2012 (UTC)
- The client should have write access, since it has written crash logs. I'm using winebottler (only free thing that seems to work on mac) and have no idea how to use the command line arguments with it. Random Weird Guy 20:47, 26 February 2012 (UTC)
- Same issue, once every run my GW shortcut wouldn't work and I had to restart, but since the update I had not been able to run it at all. The screen turns black and doesn't respond. When it used to work, the screen turned white first before showing me the game, and I had to click the screen to be able to enter my password (just giving all the info I can, since I'm a Wine-noob and dunno what's important and what not). With the -oldauth argument it worked first try. Cheers for the tip :). Helgan Iceglow 12:30, 27 February 2012 (UTC)
- How do you get it to work with TexMod? Random Weird Guy 18:56, 27 February 2012 (UTC)
- I wasn't aware that TexMod worked on Linux since it works via DirectX. Short answer: you can't. But, you might be able to use the uMod program, which supports TexMod files as well as command-line options. Should be available somewhere on Guru, I think some of the developers hide around there. It also doesn't "leak" textures and launches substantially faster. –Jette 21:20, 27 February 2012 (UTC)
- I've been able to run TexMod before the update on my Mac via Wine, I'm not really familiar with the coding of TexMod though.. Random Weird Guy 21:36, 27 February 2012 (UTC)
- I wasn't aware that TexMod worked on Linux since it works via DirectX. Short answer: you can't. But, you might be able to use the uMod program, which supports TexMod files as well as command-line options. Should be available somewhere on Guru, I think some of the developers hide around there. It also doesn't "leak" textures and launches substantially faster. –Jette 21:20, 27 February 2012 (UTC)
- How do you get it to work with TexMod? Random Weird Guy 18:56, 27 February 2012 (UTC)
- Same issue, once every run my GW shortcut wouldn't work and I had to restart, but since the update I had not been able to run it at all. The screen turns black and doesn't respond. When it used to work, the screen turned white first before showing me the game, and I had to click the screen to be able to enter my password (just giving all the info I can, since I'm a Wine-noob and dunno what's important and what not). With the -oldauth argument it worked first try. Cheers for the tip :). Helgan Iceglow 12:30, 27 February 2012 (UTC)
- The client should have write access, since it has written crash logs. I'm using winebottler (only free thing that seems to work on mac) and have no idea how to use the command line arguments with it. Random Weird Guy 20:47, 26 February 2012 (UTC)
- With the recent "security changes" the client will now extract and load a DLL into the game directory. Make sure that the client has access to write the directory that it is running from or try launching with the old auth argument. 85.195.86.54 16:57, 25 February 2012 (UTC)
- Same problem, same error code. Ubuntu 10.04, Wine1.2, i was able to login after installing wine1.3, but i did it in about the worst way i could have. Long story short, wine no longer appears as installed in synaptic but software center has 1 wine installed (either dummy or the binary, i cant get both installed as installing one removes the other) and i've had trouble completely removing it, etc. Anyway, 1.3 is an issue because when i ran gw with 1.3, the in game windows do not appear unless interacted with, and even then its only parts of the window or nothing. No health bars for party, no chat window, its not playable. 98.164.158.241 21:52, 27 February 2012 (UTC)
- I got the exact same error in the log. Random Weird Guy 16:09, 25 February 2012 (UTC)
It's fixed now, it works fine on Wine without having to use command-line stuff. Random Weird Guy 21:37, 2 March 2012 (UTC)
ArenaNet dropping Guild Wars support for older Windows versions[edit]
http://www.neoseeker.com/news/18616-arenanet-dropping-guild-wars-support-for-older-windows-versions/
What about wine ? --The preceding unsigned comment was added by 90.37.185.137 (talk).
- Wine has never been supported. It may or may not continue to work, there's no way for us to know until the relevant game updates arrive. Tub 17:14, 17 March 2012 (UTC)
- Older versions of Windows in this context means Windows that is clearly and unambiguously DOS-based. Windows 2000 saw the introduction of "NT," a term that means nothing and never did. At first I thought it was a marketing sham, but apparently there is a difference between NT and running DOS with a graphical shell. As long as you haven't ordered Wine to run in ancient emulation mode, Wine shouldn't be affected. If anything it
might work better after they toss out the 20-year-old backwards-compatibility codenothing will change, improvements require programmers. Ha! –Jette 18:06, 17 March 2012 (UTC)
- Older versions of Windows in this context means Windows that is clearly and unambiguously DOS-based. Windows 2000 saw the introduction of "NT," a term that means nothing and never did. At first I thought it was a marketing sham, but apparently there is a difference between NT and running DOS with a graphical shell. As long as you haven't ordered Wine to run in ancient emulation mode, Wine shouldn't be affected. If anything it
Empty login screen[edit]
OpenSuSE 12.1 (x86), Wine 1.5.3 (won't work properly with win XP mode both win 7), latest fgrlx (HD5770), KDE 4.8 (KWin disabled for gw window), GLSL - enabled (same problem with disabled) DD render - OpenGL, Offscrren render - backbuffer. After loading I have only blank screen, without UI. Like this: http://img26.imageshack.us/img26/3560/13170468.png Any ideas? --X10Dead 13:33, 22 May 2012 (UTC)
I had the same issue, but by running "wine Gw.exe -dx8 -noshaders", the problem was solved. --68.231.25.33 02:34, 24 July 2012 (UTC)