Problem Running With Crossover after Feb 22 Update
Wika Sham
As title says, After the update I have been unable to run guild wars. It updated and everything as soon as it was done loading, it opens the window and automatically closes. Tried restarts, making a copy of it, and creating a new bottle. Anyone know what could be causing this problem?
RELOAD911
I've been having the same problem with Wine.
Hennu
Hey,
Having same problem, that the gw.exe doesnt let the game run. I have windows xp. Reinstalled gw, also moved the gw.dat file from laptop, on which it works even after the update, but the desktop comp keeps getting the error. Contacted support too. I've checked firewall as well that it allows it.
Error log keeps logging this error:
App: Gw.exe
Fatal error (2): Exception
When: 2/23/2012 17:57:29
File: u:\code\arena\core\platform\windows\exe\error\exee rror.cpp(419)
Anyone figured this out yet?
EDIT: I am not using crossfire/crossover btw, but the result is same, window loads, shows 100% fast and then closes automaticly and keeps logging that in the ArenaNet.log file. (Before the security update worked fine)
Having same problem, that the gw.exe doesnt let the game run. I have windows xp. Reinstalled gw, also moved the gw.dat file from laptop, on which it works even after the update, but the desktop comp keeps getting the error. Contacted support too. I've checked firewall as well that it allows it.
Error log keeps logging this error:
App: Gw.exe
Fatal error (2): Exception
When: 2/23/2012 17:57:29
File: u:\code\arena\core\platform\windows\exe\error\exee rror.cpp(419)
Anyone figured this out yet?
EDIT: I am not using crossfire/crossover btw, but the result is same, window loads, shows 100% fast and then closes automaticly and keeps logging that in the ArenaNet.log file. (Before the security update worked fine)
Schnellburg
Try disabling Crossfire. I know somewhere I was reading that GW was never designed to run with more then 1 gpu and that might be the issue. I know when I run with SLI enabled, I seem to run into issues every so often.
K A O S Theory
Quote:
Try disabling Crossfire. I know somewhere I was reading that GW was never designed to run with more then 1 gpu and that might be the issue. I know when I run with SLI enabled, I seem to run into issues every so often.
|
Anyways, if crossover isnt working, I have been using a program called wineskins for quite some time now. It takes more time to set up, but its free. I just loaded it up and it is working so far.
Also, I pre-made an app for guild wars in the Community Works section.
Sorry I cant be of help with crossover.
Wika Sham
@ K A O S, thanks for the recommendation, I'll look into it
Mnokey
Wika Sham
Having a bit of a problem trying to do this command line arguments on a mac...anyone have an recommendations?
RELOAD911
Wikia Sham, I fixed it! With WineBottler for OS X, here's what I did:
I located my Guild Wars.app file (built by WineBottler or in your case that would be Crossover, they are both very similar), opened it (RMB -> Show Package Contents), went through folder Contents. There's a plist file there, named Info.plist. Open it with TextEdit or any other text editor. Somewhere at the top there's <key>WineProgramArguments</key> key. Below it, the string that contains <string>-windowed</string> (there might be no -windowed in your case, could be empty or contain anything else). Add -oldauth so it looks like <string>-windowed -oldauth</string>. If there is -newauth key, remove it!
I imagine this would be a little different if you've got linux, but the basic idea is the same - locate the app-specific settings file and modify the line that is responsible for command line arguments.
Let me know if this works for you.
I located my Guild Wars.app file (built by WineBottler or in your case that would be Crossover, they are both very similar), opened it (RMB -> Show Package Contents), went through folder Contents. There's a plist file there, named Info.plist. Open it with TextEdit or any other text editor. Somewhere at the top there's <key>WineProgramArguments</key> key. Below it, the string that contains <string>-windowed</string> (there might be no -windowed in your case, could be empty or contain anything else). Add -oldauth so it looks like <string>-windowed -oldauth</string>. If there is -newauth key, remove it!
I imagine this would be a little different if you've got linux, but the basic idea is the same - locate the app-specific settings file and modify the line that is responsible for command line arguments.
Let me know if this works for you.