Guild Wars 2

so, first off, the whole thing runs really well on my PC.
no issues so far, bar one.

for some reason, overwolf doesn’t seem to work with the 64 bit client, while it worked perfectly well with the 32 bit one. any thoughts?
i tried running the 32 bit version again, and overwolf works perfectly with it.

edit: i figured out the issue. seems overwolf looks for ‘gw2’ to be launched. changing the 4-bit client’s name to that fixed it.

Hi, i’ve just downloaded the 64-bit client and for my surprise it simply doesn’t start the laucher at all.
I’ve put it alongside with the old 32-bit .exe file, then double-clicked but the following error message appears always:

• Crash <—*
  Exception: c000001d
  App: Gw2-64.exe
  Pid: 3188
  Cmdline:
  BaseAddr: 000000013F7A0000
  ProgramId: 101
  Build: 54655
  When: 2015-11-05T18:57:44Z
  Uptime: 0 days 0:00:00
  Flags: 0

• System <—*
  Name: BRUNO-PC
  IpAddr: 192.168.0.5
  Processors: 4 [GenuineIntel:6:12:3]
  OSVersion: Windows 6.1 (64 bit)

• System Memory <—*
  Physical: 5692MB/ 7937MB 71%
  Paged: 13232MB/15874MB 83%
  Virtual: 8388498MB/8388607MB 99%
  Load: 28%
  CommitTotal: 2641MB
  CommitLimit: 15874MB
  CommitPeak: 4768MB
  SystemCache: 1840MB
  HandleCount: 23777
  ProcessCount: 57
  ThreadCount: 800

• Process Memory <—*
  Private: 17MB
  WorkingSet: 12MB
  PeakWorkingSet: 12MB
  PageFaults: 3220

• Memory Category Usage (Inclusive) <—*
  [Category] [Size(MB)] [Count]
  Root 5.69 932
  Uncategorized 5.39 917
  Programmer Data 0.30 15
  File Service 0.29 2
  I/O 0.29 2
  Dictionary 0.00 6
  Collections 0.00 6
  Engine 0.00 2
  Gr 0.00 2
  Gr Texture 0.00 1
  Msg 0.00 2
  Networking 0.00 2
  Gr Umbra 0.00 1
  Services 0.00 2
  HashTable 0.00 0
  Debugging 0.00 0
  BTree 0.00 0
  Subheaps 0.00 0
  RTree 0.00 0
  Threading 0.00 0
  List 0.00 0
  Paged Image 0.00 0
  String 0.00 0
  File Core 0.00 0

• Memory Category Usage (Exclusive) <—*
  [Category] [Size(MB)] [Count]
  Uncategorized 5.39 917
  File Service 0.29 2
  Dictionary 0.00 6
  Gr Texture 0.00 1
  Msg 0.00 2
  Gr Umbra 0.00 1
  Services 0.00 2
  Programmer Data 0.00 1
  Gr 0.00 0
  Engine 0.00 0
  I/O 0.00 0
  Networking 0.00 0
  Collections 0.00 0
  HeightMap 0.00 0
  HashTable 0.00 0
  Debugging 0.00 0
  BTree 0.00 0
  Subheaps 0.00 0
  RTree 0.00 0
  Threading 0.00 0
  List 0.00 0
  Paged Image 0.00 0
  String 0.00 0
  File Core 0.00 0

[DbgHelp.dll is ]
[DbgHelp.dll version 0.0.0.0 (32-bit compatible)]

• Thread 0xb84 <—*

• Trace <—*
  Pc Rt : Args
  00000001`3fc028a0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
  00000001`3fa22901 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
  00000001`3fc076eb 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
  00000001`3fc07621 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
  00000001`3fc00327 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
  00000000`76eaf56d 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
  00000000`76fe3281 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000

• Thread registers <—*
  rax=000000013fa228f0 rbx=0000000000001b6d rcx=0000000141128430
  rdx=0000000000000000 rsi=0000000000000697 rdi=0000000140956848
  rip=000000013fc028a0 rsp=000000000014f9c0 rbp=0000000000000000
  r8=000000000014f9a8 r9=0000000000000000 r10=0000000000000000
  r11=0000000000000286 r12=0000000000000000 r13=0000000000000000
  r14=0000000000000000 r15=0000000000000000
  cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010202

rax-32 000000013FA228D0 480190f0`f1058b48 ccc30190`f0fa0589 480190f0`e1058b48 ccc30190`f1620589
rax 0 000000013FA228F0 05100ff3`28ec8348 1dfcbfe8`00fc43f0 90f0a705`110ff300 ccccc328`c4834801
rax32 000000013FA22910 05100ff3`28ec8348 1dfc9fe8`00fc43c4 90f08f05`110ff300 ccccc328`c4834801
rcx-32 0000000141128410 00000000`ffffffff 00000000`00000000 00000000`00000000 00000000`00000fa0
rcx 0 0000000141128430 00000000`00205500 00000000`ffffffff 00000000`00000000 00000000`00000000
rcx32 0000000141128450 00000000`00000fa0 00000000`00205540 00000000`ffffffff 00000000`00000000
r8-32 000000000014F988 00000001`40a23710 00000001`3fc028a0 00000001`40729de9 00000000`027e77f0
r8 0 000000000014F9A8 00000000`0014f9c0 00000000`0000002d 00000001`40a239e0 00000000`00000000
r832 000000000014F9C8 00000001`40a235f0 00000000`00000000 00000001`02010201 00000000`00001500

• Code <—*
  00000001`3fc02880 f20f5ac0 4883c468 c3e85e8e 00004883 ..Z.H..h..^…H.
  00000001`3fc02890 c468c366 66666666 0f1f8400 00000000 .h.fffff……..
  00000001`3fc028a0 c5f97ec0 448b05c5 f8db0041 23c0413b ..~.D……A#.A;
  00000001`3fc028b0 c00f84fe 010000c5 fa5ae8c4 c1f97ee9 ………Z….~.
  00000001`3fc028c0 490fbaf1 3f4c3b0d e4f7db00 0f8fae00 I…?L;………
  00000001`3fc028d0 00004c3b 0d77f8db 007d454c 3b0d7ef8 ..L;.w…}EL;.~.

• Stack <—*
  00000000`0014f9c0 00000000`00000000 00000001`40a235f0 00000000`00000000 00000001`02010201 ………5..................... 00000000`0014f9e0 00000000`00001500 00000001`3fc004e9 00000001`40941ba0 00000000`c0ca220c ...........?.......….."……
  00000000`0014fa00 00000000`00000000 00000001`3fa228b4 00000000`00000000 00000000`00000000 ………(.?………………..
  00000000`0014fa20 00000000`00000000 00000001`3fa22901 00000000`00001b6d 00000000`00000693 ………).?….m……………
  00000000`0014fa40 00000001`40956828 27b0be67`000000c2 00000000`00001b6d 00000001`3fc076eb (h.........g..'m........v.?.... 00000000`0014fa60 00000000`00001b6d 00000000`00000000 00000000`000005f6 00000001`40956340 m.......................c.@….
  00000000`0014fa80 00000001`3f7a0000 00000001`3fc07621 00000000`00000001 00000000`00000000 ..z?….!v.?………………..
  00000000`0014faa0 00000000`00000001 00000000`00000000 00000000`00000000 00000001`3fc00327 ……………………’..?….
  00000000`0014fac0 00000000`00000000 00000000`00000000 00000000`00000001 00000000`00000001 …………………………..
  00000000`0014fae0 00000006`5c44f47d 00000000`00000000 00000000`00000000 00000000`76eaf56d }.D\………………..m..v….
  00000000`0014fb00 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 …………………………..
  00000000`0014fb20 00000000`00000000 00000000`76fe3281 00000000`00000000 00000000`00000000 ………2.v………………..
  00000000`0014fb40 00000000`00000000 00000000`00000000 00000000`76f29220 00000000`76f29220 ……………. ..v…. ..v….
  00000000`0014fb60 00000000`0014ecb0 00000000`00000000 00000000`00000000 00000000`00000000 …………………………..
  00000000`0014fb80 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 …………………………..
  00000000`0014fba0 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 …………………………..
  00000000`0014fbc0 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 …………………………..
  00000000`0014fbe0 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 …………………………..
  00000000`0014fc00 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 …………………………..
  00000000`0014fc20 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 …………………………..
  00000000`0014fc40 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 …………………………..
  00000000`0014fc60 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 …………………………..
  00000000`0014fc80 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 …………………………..
  00000000`0014fca0 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 …………………………..
  00000000`0014fcc0 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 …………………………..
  00000000`0014fce0 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 …………………………..
  00000000`0014fd00 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 …………………………..
  00000000`0014fd20 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 …………………………..
  00000000`0014fd40 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 …………………………..
  00000000`0014fd60 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 …………………………..
  00000000`0014fd80 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 …………………………..
  00000000`0014fda0 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 …………………………..

END****************************************

I’m using Windows 7 – 64-bit, 8gb RAM.
What is happening?

Leamas.5803:

Nick.8256:

For years I have been going back and forth with support trying to fix these oom crashes and this has fixed everything even with massive overclocks (like i suggested very long ago). Anyways, if you guys are still crashing I would suggest giving asus realbench a shot to test for system stability. Its pretty cool because unlike other tests it will test everything at the same time. Set it to stress test mode, select your installed ram size and let it run overnight for at least eight hours.

http://rog.asus.com/376212014/overclocking/realbench-v2-4-launched-with-x99-support/

Can this be used for non-Asus motherboards?

Definitely. Any board and any video card

To add my two cents, you might also need to redirect any Mouse Software (such as Logitech Gaming Software) to the new .exe file.

Upgrading to Windows 7 SP1 fixed my immediate crashing problem. Thanks!

WesleySnipes.3917:

Menadena.7482:

No mac version? I has a sad.

i cry after every patch when i find out nothing changed

+1 weeping…

‘Beta’ time should end soon.
AND, give us a try for 64-bit client as well, please?

Johan Skold.4708:

Valiant.8016:

Precisely how long will this “beta” period be for?

I would think “beta” is a taboo word with the Mac client being in “beta” status for the better part of 3 years.

I think in general we don’t tend to drop the beta tag until we’re completely satisfied with how it runs. That just hasn’t happened yet for the Mac client, for multiple reasons. I realize it won’t make much of a difference at this point, but we sincerely do intend to get it from being barely an okay experience to at the very least a good one, with the goal being a great one. As all good things though, it will take time.

Hey, that’s great news!
Better, non-Beta, maybe 64-bit(?), for the non-PC GW2 & HoT players?
YES, PLEASE!

Guardian of Angels.9867:

Most curious thing happened, my FPS counter from nVidia Shadowplay doesn’t work in the 64 bit version.

I just checked and it’s still working on the 32 bit version :P

I wonder if this is related to something I ran into last night. MSI Afterburner would not record when I ran the 64-bit client.

Has anyone been able to record gameplay footage while running the 64 bit client?

Ravion Hawk.4736:

Gaile Gray.6029:

I already have the 32-bit client; will I have to completely download the game again?
No. The 64-bit client uses the same data as the 32-bit client. If you already have the game installed, you can follow these instructions to avoid needing to reinstall the game:

• Download the 64-bit client.
• Copy the downloaded program into your Guild Wars 2 game folder.
• Update any shortcuts to the game to point to the new file instead.
  This process will be automatic once we get out of beta.

I would like to remind you that 64bit versions Windows have two “Program Files” folders for a VERY specific reason.

C:\Program Files\ <—————— Programs run from here are run in 64bit
C:\Program Files (x86)\ <—— Programs run from here cause Windows to drop into 32bit

You just told everyone to run a 64bit client from the very same directory that causes Windows to work in 32bit.

Might I suggest that you set the 64bit beta client to do a fresh install to the “C:\Program Files\” folder then just have us advanced users (Desktop Support Tech right here) copy the gw2.dat to the 64bit installation.

You can avoid some bugs right there without having to hunt down the cause.

If that’s a problem, it sounds like some sort of weird Windows thing. I have GW2 located in C:\GW2 and had no issues. People can just move the directory out of C:\Program Files too. No re-install needed.

Chaba.5410:

Guardian of Angels.9867:

Most curious thing happened, my FPS counter from nVidia Shadowplay doesn’t work in the 64 bit version.

I just checked and it’s still working on the 32 bit version :P

I wonder if this is related to something I ran into last night. MSI Afterburner would not record when I ran the 64-bit client.

Has anyone been able to record gameplay footage while running the 64 bit client?

I can confirm that I had to change the name to be able to record with Nvidia Shadowplay.

Johan Skold.4708:

Valiant.8016:

Precisely how long will this “beta” period be for?

I would think “beta” is a taboo word with the Mac client being in “beta” status for the better part of 3 years.

I think in general we don’t tend to drop the beta tag until we’re completely satisfied with how it runs. That just hasn’t happened yet for the Mac client, for multiple reasons. I realize it won’t make much of a difference at this point, but we sincerely do intend to get it from being barely an okay experience to at the very least a good one, with the goal being a great one. As all good things though, it will take time.

I don’t mean to hijack the thread, but…seriously?

TheHeretic.3529:

Chaba.5410:

Guardian of Angels.9867:

Most curious thing happened, my FPS counter from nVidia Shadowplay doesn’t work in the 64 bit version.

I just checked and it’s still working on the 32 bit version :P

I wonder if this is related to something I ran into last night. MSI Afterburner would not record when I ran the 64-bit client.

Has anyone been able to record gameplay footage while running the 64 bit client?

I can confirm that I had to change the name to be able to record with Nvidia Shadowplay.

Thats a rights issue. 64bit code is signed, and windows has a security lock down from 64bit runtimes from being accessed via shared processes if they are located under ‘program files’ and ‘widows\system32’. So that makes sense.

Anet – there are a few things you need to do here

1. Make a proper 64bit installer, have it detect the 32bit .exe and rename it to _old or something. Then have the 64bit installer name the new 64bit client to gw2.exe. This will fix the Laptops with switchable graphics issues reported earlier.

2. have the installer move the game files from “C:\Program files” to “C:\Guild Wars2”, which includes the entire runtime folder and redo all the desktop and start menu shortcuts. Otherwise 3rd party applications will NEVER be able to interact with the GW2 64bit client due to Microsoft NTFS security lockdowns. The only work around is to run the game as an administrator, and that is NOT a proper workaround and very dangerous to the local system if the game client becomes compromised.

3. Since the game client is small and both 32bit and 64bit use the same .dat file, make a new launcher that gives users the option to select 64bit (when a detected supported OS is present) and 32bit (for legacy support/testing). So that users do not need to mess with file names and structures here. Also move the in game settings to be accessible via the launcher and setup system detected limits from here, you can better explain the in game options from this screen. As once in game you can always adjust them after the fact.

I think doing some of this will really help getting users on board with the 64bit client, and you embed 32bit support via a new pre-launcher.

sirsquishy.8531:

TheHeretic.3529:

Chaba.5410:

Guardian of Angels.9867:

Most curious thing happened, my FPS counter from nVidia Shadowplay doesn’t work in the 64 bit version.

I just checked and it’s still working on the 32 bit version :P

I wonder if this is related to something I ran into last night. MSI Afterburner would not record when I ran the 64-bit client.

Has anyone been able to record gameplay footage while running the 64 bit client?

I can confirm that I had to change the name to be able to record with Nvidia Shadowplay.

Thats a rights issue. 64bit code is signed, and windows has a security lock down from 64bit runtimes from being accessed via shared processes if they are located under ‘program files’ and ‘widows\system32’. So that makes sense.

But I wrote above that I have my GW2 installed in C:\GW2 directory. Must be a “run as admin” thing.

Today I renamed gw2-64.exe to gw2.exe as it was indicated that renaming the file should be OK. When doing fractals a bit later I experienced 2 crashes right after each other. In each error report it showed "App: Gw2-64.exe ", despite me having renamed the exe file. So that makes me wonder if renaming the exe file is actually as harmless as one would expect?

hansQ.7985:

I’m having a problem with text and graphics overall becoming blurry when playing on 64bit client. Anyone got a clue what would fix this?

I am having the same issues, text and graphics are blurry and not as sharp as the 32 bit version. Has anyone found na a fix for this? I’ve added the exe in nvidia setting and all but it’s still blurry (I have everything in max settings)

dsdanger.1632:

so, first off, the whole thing runs really well on my PC.
no issues so far, bar one.

for some reason, overwolf doesn’t seem to work with the 64 bit client, while it worked perfectly well with the 32 bit one. any thoughts?
i tried running the 32 bit version again, and overwolf works perfectly with it.

edit: i figured out the issue. seems overwolf looks for ‘gw2’ to be launched. changing the 4-bit client’s name to that fixed it.

thanks for the update, i was having the same issue with nvidia shadowplay/fps, and changing the name fixed it.

Johan Skold.4708:

Leamas.5803:

Has the 32-bit client and OOM been linked to the nVidia driver crash or will the new client not help with that?

*Display driver nvlddmkm stopped responding and has successfully recovered.

The description for Event ID 13 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer. *

That sounds unrelated. If it happens again you should try downloading new nVidia drivers.

I just checked on my nVidia selection from the program management box and you can add the new .exe file to the list of items it will work with.

But on another note Johan, it appears that mumble overlay for chat is not recognized with the new client. Is there a fix or work around for this? I would hate to have to revert to the 32bit just to be able to voice chat with my guild members.

After ive followed the steps to replace the files its make me re download guildwars2…
335,900 files….

Thanks for making this available. Seems good, so far I’ve only tested it in a few fractals and some HoT exploration. I’m looking forward to trying it out on some big meta-event tonight. Fingers crossed that it solves the game crashes I’ve been having since HoT.

lynspottery.6529:

Johan Skold.4708:

Leamas.5803:

Has the 32-bit client and OOM been linked to the nVidia driver crash or will the new client not help with that?

*Display driver nvlddmkm stopped responding and has successfully recovered.

The description for Event ID 13 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer. *

That sounds unrelated. If it happens again you should try downloading new nVidia drivers.

I just checked on my nVidia selection from the program management box and you can add the new .exe file to the list of items it will work with.

But on another note Johan, it appears that mumble overlay for chat is not recognized with the new client. Is there a fix or work around for this? I would hate to have to revert to the 32bit just to be able to voice chat with my guild members.

Ya, you’re right. My current nVidia settings are for the x86 client. The only difference though, should be the Shader Cache, which will be disabled for the x86 client, but not for the x64 client. I didn’t see a need to disable the shader cache for other games. Even with GW2, it’s more of an experiment. The power management change and multi-display mode change I made at the global level.

Apologies.. should of posted this here not in the main sticky …

Downloaded 64Bit client this afternoon and have been seeing some nice increases in FPS, without stuttering and load times reduction for sure.. but at the expense of having massive screen colour blooms randomly shooting out at me.. making it pretty much unplayable at times (and getting more frequent).

My take is that its to do with camera and lighting cos it hits from certain angles when moving and then fills with surrounding colours and particle effects.

Never had any issues except occasional crashing sometimes (had a really bad couple of weeks after the September patch but that seems to off been patched out)

System – Desktop
i7 – 3770k
Win 7 Ultimate 64bit. SP1
ASUS P8Z77-VPro M/B
16GB Ripjaw DDR3 RAM
Nvidia GTX550Ti GPU
GW2 runs off dedicated Mushkin 256GB SSD

Getting a solid 60FPS pretty much everywhere now with VSYNC ON (drops to 40 ish in mass warfare situations, that’s a nice 15-20FPS gain from previous).
Most settings set to medium or High.. I don’t use refection’s or shadows/shaders anyways but pretty much all other options are on so no issues with FPS and no stuttering except when the screen bloom erupts. – Note I have tried turning everything right down and right up .. but same thing happens… had it a lot in Fractals and especially Verdant Brink.

Guess it’s back to downloading the 32bit client again – - 3 more hours of zzzzzz

Bloodstealer.5978:

Apologies.. should of posted this here not in the main sticky …

Downloaded 64Bit client this afternoon and have been seeing some nice increases in FPS, without stuttering and load times reduction for sure.. but at the expense of having massive screen colour blooms randomly shooting out at me.. making it pretty much unplayable at times (and getting more frequent).

My take is that its to do with camera and lighting cos it hits from certain angles when moving and then fills with surrounding colours and particle effects.

Never had any issues except occasional crashing sometimes (had a really bad couple of weeks after the September patch but that seems to off been patched out)

System – Desktop
i7 – 3770k
Win 7 Ultimate 64bit. SP1
ASUS P8Z77-VPro M/B
16GB Ripjaw DDR3 RAM
Nvidia GTX550Ti GPU
GW2 runs off dedicated Mushkin 256GB SSD

Getting a solid 60FPS pretty much everywhere now with VSYNC ON (drops to 40 ish in mass warfare situations, that’s a nice 15-20FPS gain from previous).
Most settings set to medium or High.. I don’t use refection’s or shadows/shaders anyways but pretty much all other options are on so no issues with FPS and no stuttering except when the screen bloom erupts. – Note I have tried turning everything right down and right up .. but same thing happens… had it a lot in Fractals and especially Verdant Brink.

Guess it’s back to downloading the 32bit client again – - 3 more hours of zzzzzz

Gods mate you were suppose to download the 64-bit client, a under 30 MB file and place it in your Guild Wars 2 folder along side the 32-bit client. That’s it. Run either, no muss or fuss and no stupidly long downloads.

Behellagh.1468:

Bloodstealer.5978:

Apologies.. should of posted this here not in the main sticky …

Downloaded 64Bit client this afternoon and have been seeing some nice increases in FPS, without stuttering and load times reduction for sure.. but at the expense of having massive screen colour blooms randomly shooting out at me.. making it pretty much unplayable at times (and getting more frequent).

My take is that its to do with camera and lighting cos it hits from certain angles when moving and then fills with surrounding colours and particle effects.

Never had any issues except occasional crashing sometimes (had a really bad couple of weeks after the September patch but that seems to off been patched out)

System – Desktop
i7 – 3770k
Win 7 Ultimate 64bit. SP1
ASUS P8Z77-VPro M/B
16GB Ripjaw DDR3 RAM
Nvidia GTX550Ti GPU
GW2 runs off dedicated Mushkin 256GB SSD

Getting a solid 60FPS pretty much everywhere now with VSYNC ON (drops to 40 ish in mass warfare situations, that’s a nice 15-20FPS gain from previous).
Most settings set to medium or High.. I don’t use refection’s or shadows/shaders anyways but pretty much all other options are on so no issues with FPS and no stuttering except when the screen bloom erupts. – Note I have tried turning everything right down and right up .. but same thing happens… had it a lot in Fractals and especially Verdant Brink.

Guess it’s back to downloading the 32bit client again – - 3 more hours of zzzzzz

Gods mate you were suppose to download the 64-bit client, a under 30 MB file and place it in your Guild Wars 2 folder along side the 32-bit client. That’s it. Run either, no muss or fuss and no stupidly long downloads.

Huh.. that’s all I have done…
But now I am gunna wipe it all and start fresh – that’s all I meant.

Running a 4K monitor on Windows 7 SP1. With the 32bit client I can use Properties/Compatibility/Disable display scaling on high DPI settings to make the interface display correctly but this option is greyed out on the 64bit client.

A workaround is to put this entry in the registry:
HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers

New String
Key=C:\GuildWars2\Gw2-64.exe <— use path to exe on your system
Value=HIGHDPIAWARE

Boo.5743:

Running a 4K monitor on Windows 7 SP1. With the 32bit client I can use Properties/Compatibility/Disable display scaling on high DPI settings to make the interface display correctly but this option is greyed out on the 64bit client.

A workaround is to put this entry in the registry:
HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers

New String
Key=C:\GuildWars2\Gw2-64.exe <— use path to exe on your system
Value=HIGHDPIAWARE

Or have you tried renaming the gw2-64.exe to gw2.exe ? That also helps for
quite some issues.

Johan Skold.4708:

Gode Fridus.5607:

Today I renamed gw2-64.exe to gw2.exe as it was indicated that renaming the file should be OK. When doing fractals a bit later I experienced 2 crashes right after each other. In each error report it showed "App: Gw2-64.exe ", despite me having renamed the exe file. So that makes me wonder if renaming the exe file is actually as harmless as one would expect?

The name in crash reports is always the original executable name. Otherwise we wouldn’t be able to identify it when we receive the crash report. Renaming the executable is perfectly fine.

OK, Thanks, then I can strike that as possible cause for those two crashes. Guess it would have been to easy if renaming the file back to the original file name would be the solution for this

I am experiencing a massive drop in frames. On the character select I am running between 15 to 22 FPS compared to my normal 50 to 60 frames. This could just be because it is only in the beta stages but here are my specs.

Alienware 17 laptop

Nvidia Gforce 970
intel core i7-4720HQ CPU @ 2.60GHz
16 GB ram
64-bit Operating System (64-bit Windows 8.1)

Absolutely smooth performance even in large scale open world pve events, it feels like it’s running better than the 32 bit version, taking better advantage of the memory in my computer!

Windows 10 pro 64
Xeon X5650
Gigabyte x58
R9 280 toxic
24 gig ram

Besides FotM crashes, 64-bit game client is working with no issues with high graphic settings. Game resources are going over 4GB of memory usage with no crash issues so far.

Thank you for this release. I hope the other bugs get ironed out.

I find the 64-bit client runs much smoother than the 32-bit and has much shorter load times. One thing I notice however is that in the games graphics options “high-res character textures” setting is greyed out and un-checkable.

It crashes at start. The first I see is the crash message.
To not flood i’ll paste this part of the report (is sent)

• Crash <—*
  Exception: c000001d
  App: Gw2-64.exe
  Pid: 5436
  Cmdline:
  BaseAddr: 000000013F420000
  ProgramId: 101
  Build: 54655
  When: 2015-11-06T00:16:19Z
  Uptime: 0 days 0:00:00
  Flags: 0

Jemikwa.2571:

I’ll have to test this on my Windows machine. It’s a shame there isn’t any updates for Mac users though. Crashes and errors have been through the roof this past weekend (usually once every hour or two), even on the most basic of graphical settings. I wish my Windows machine wasn’t worse than my Mac, otherwise I wouldn’t play on my Mac :<

I don’t have too many crashes on my Mac, just the usual MacBook Pro fans screaming like the roar of the engines of a 747. What are you doing that causes the crash? What is your system spec?

I do hope they release a 64bit Mac OS X client though, or any real optimizations.

Got a network error message while on the 64-bit client. Now I can’t load my characters anymore. Everytime I try, I’m getting the same message after I’m on the loading screen for a few seconds. My internet connect is completely fine. I attached a screen shot of it.

Instant crash when i click this exe:
[spoiler=Crash error]—> Crash <—
Exception: c000001d
App: Gw2-64.exe
Pid: 3568
Cmdline:
BaseAddr: 000000013F540000
ProgramId: 101
Build: 54655
When: 2015-11-06T00:46:43Z
Uptime: 0 days 0:00:00
Flags: 0

—> System <—
Name: HYPERION
IpAddr: 192.168.1.100
Processors: 4 [GenuineIntel:6:12:3]
OSVersion: Windows 6.1 (64 bit)

—> System Memory <—
Physical: 4166MB/ 8003MB 52%
Paged: 10777MB/16005MB 67%
Virtual: 8388498MB/8388607MB 99%
Load: 47%
CommitTotal: 5227MB
CommitLimit: 16005MB
CommitPeak: 5692MB
SystemCache: 2924MB
HandleCount: 32925
ProcessCount: 106
ThreadCount: 1400

—> Process Memory <—
Private: 17MB
WorkingSet: 12MB
PeakWorkingSet: 12MB
PageFaults: 3218

—> Memory Category Usage (Inclusive) <—
[Category] [Size(MB)] [Count]
Root 5.69 932
Uncategorized 5.39 917
Programmer Data 0.30 15
File Service 0.29 2
I/O 0.29 2
Dictionary 0.00 6
Collections 0.00 6
Engine 0.00 2
Gr 0.00 2
Gr Texture 0.00 1
Msg 0.00 2
Networking 0.00 2
Gr Umbra 0.00 1
Services 0.00 2
HashTable 0.00 0
Debugging 0.00 0
BTree 0.00 0
Subheaps 0.00 0
RTree 0.00 0
Threading 0.00 0
List 0.00 0
Paged Image 0.00 0
String 0.00 0
File Core 0.00 0

—> Memory Category Usage (Exclusive) <—
[Category] [Size(MB)] [Count]
Uncategorized 5.39 917
File Service 0.29 2
Dictionary 0.00 6
Gr Texture 0.00 1
Msg 0.00 2
Gr Umbra 0.00 1
Services 0.00 2
Programmer Data 0.00 1
Gr 0.00 0
Engine 0.00 0
I/O 0.00 0
Networking 0.00 0
Collections 0.00 0
HeightMap 0.00 0
HashTable 0.00 0
Debugging 0.00 0
BTree 0.00 0
Subheaps 0.00 0
RTree 0.00 0
Threading 0.00 0
List 0.00 0
Paged Image 0.00 0
String 0.00 0
File Core 0.00 0

[DbgHelp.dll is ]
[DbgHelp.dll version 0.0.0.0 (32-bit compatible)]

—> Thread 0xe50 <—

—> Trace <—
Pc Rt : Args
00000001`3f9a28a0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
00000001`3f7c2901 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
00000001`3f9a76eb 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
00000001`3f9a7621 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
00000001`3f9a0327 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
00000000`7787f56d 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
00000000`77ab3281 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000

—> Thread registers <—
rax=000000013f7c28f0 rbx=0000000000001b6d rcx=0000000140ec8430
rdx=0000000000000000 rsi=0000000000000697 rdi=00000001406f6848
rip=000000013f9a28a0 rsp=00000000002efa40 rbp=0000000000000000
r8=00000000002efa28 r9=0000000000000000 r10=0000000000000000
r11=0000000000000286 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010202

rax-32 000000013F7C28D0 480190f0`f1058b48 ccc30190`f0fa0589 480190f0`e1058b48 ccc30190`f1620589
rax 0 000000013F7C28F0 05100ff3`28ec8348 1dfcbfe8`00fc43f0 90f0a705`110ff300 ccccc328`c4834801
rax32 000000013F7C2910 05100ff3`28ec8348 1dfc9fe8`00fc43c4 90f08f05`110ff300 ccccc328`c4834801
rcx-32 0000000140EC8410 00000000`ffffffff 00000000`00000000 00000000`00000000 00000000`00000fa0
rcx 0 0000000140EC8430 00000000`00495ba0 00000000`ffffffff 00000000`00000000 00000000`00000000
rcx32 0000000140EC8450 00000000`00000fa0 00000000`00495be0 00000000`ffffffff 00000000`00000000
r8-32 00000000002EFA08 00000001`407c3710 00000001`3f9a28a0 00000001`404c9de9 00000000`027e7e30
r8 0 00000000002EFA28 00000000`002efa40 00000000`0000002d 00000001`407c39e0 00000000`00000000
r832 00000000002EFA48 00000001`407c35f0 00000000`00000000 00000001`02010201 00000000`00001500

—> Code <—
00000001`3f9a2880 f20f5ac0 4883c468 c3e85e8e 00004883 ..Z.H..h..^…H.
00000001`3f9a2890 c468c366 66666666 0f1f8400 00000000 .h.fffff……..
00000001`3f9a28a0 c5f97ec0 448b05c5 f8db0041 23c0413b ..~.D……A#.A;
00000001`3f9a28b0 c00f84fe 010000c5 fa5ae8c4 c1f97ee9 ………Z….~.
00000001`3f9a28c0 490fbaf1 3f4c3b0d e4f7db00 0f8fae00 I…?L;………
00000001`3f9a28d0 00004c3b 0d77f8db 007d454c 3b0d7ef8 ..L;.w…}EL;.~.

—> Stack <—
00000000`002efa40 00000000`00000000 00000001`407c35f0 00000000`00000000 00000001`02010201 ………5|.................... 00000000`002efa60 00000000`00001500 00000001`3f9a04e9 00000001`406e1ba0 00000000`8b6f40cc ...........?......n…..o..... 00000000`002efa80 00000000`00000000 00000001`3f7c28b4 00000000`00000000 00000000`00000000 .........(|?.................... 00000000`002efaa0 00000000`00000000 00000001`3f7c2901 00000000`00001b6d 00000000`00000693 .........)|?....m............... 00000000`002efac0 00000001`406f6828 27b0be67`000000c2 00000000`00001b6d 00000001`3f9a76eb (ho……..g..‘m……..v.?….
00000000`002efae0 00000000`00001b6d 00000000`00000000 00000000`000005f6 00000001`406f6340 m…………………..co….
00000000`002efb00 00000001`3f540000 00000001`3f9a7621 00000000`00000001 00000000`00000000 ..T?….!v.?………………..
00000000`002efb20 00000000`00000001 00000000`00000000 00000000`00000000 00000001`3f9a0327 ……………………’..?….
00000000`002efb40 00000000`00000000 00000000`00000000 00000000`00000001 00000000`00000001 …………………………..
00000000`002efb60 00000003`27875439 00000000`00000000 00000000`00000000 00000000`7787f56d 9T.’………………..m..w….
00000000`002efb80 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 …………………………..
00000000`002efba0 00000000`00000000 00000000`77ab3281 00000000`00000000 00000000`00000000 ………2.w………………..
00000000`002efbc0 00000000`00000000 00000000`00000000 00000000`778f9220 00000000`778f9220 ……………. ..w…. ..w….
00000000`002efbe0 00000000`002eed30 00000000`00000000 00000000`00000000 00000000`00000000 0………………………….
00000000`002efc00 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 …………………………..
00000000`002efc20 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 …………………………..
00000000`002efc40 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 …………………………..
00000000`002efc60 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 …………………………..
00000000`002efc80 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 …………………………..
00000000`002efca0 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 …………………………..
00000000`002efcc0 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 …………………………..
00000000`002efce0 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 …………………………..
00000000`002efd00 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 …………………………..
00000000`002efd20 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 …………………………..
00000000`002efd40 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 …………………………..
00000000`002efd60 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 …………………………..
00000000`002efd80 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 …………………………..
00000000`002efda0 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 …………………………..
00000000`002efdc0 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 …………………………..
00000000`002efde0 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 …………………………..
00000000`002efe00 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 …………………………..
00000000`002efe20 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 …………………………..[/spoiler]

NB: I have followed installation and launch process correctly.

Don’t know how to get the spoiler working, lol sorry

Just to post my experience so far…the 64-bit client is running well, and co-exists nicely with the 32 bit exe file. The only thing I’ve noticed seems to be very slightly longer map load times. This is barely noticeable and in all my running around HoT (VB and Auric so far) I’ve not had any issues.

I’m running Win 10×64 on a desktop machine, 1st gen core i7, 24 GB RAM 1 TB Samsung 850SSD, nVidia GTX970FTW, and a 144Hz AOC 24" monitor @ 1920×1080. All GW2 graphics settings maxed, and I’m getting around 65FPS in relatively empty areas, dropping to ~20-30FPS in crowded maps and WB battles. With the 32-bit client, I was getting a number of OOM crashes…with the 64-bit client, not a single OOM crash thus far.

Thanks for putting the 64-bit client out for us!

My issue with GW2-64 crashing right away might be an issue outside of the game. I just upgraded my Motherboard and CPU to an Asus z97-A and Intel i7 4790 and TeamSpeak 3 64bit crashes as well. I went back to my old Motherboard and CPU (Asus x58 Sabertooth + i7 950) and it works fine. I’m going to upgrade to Windows 10 as I spoke with a few friends who have the 4790K and they had to as well. Even though this might be an issue outside of GW2 I’ll post my results just incase someone else who has a similar problem can try what I tried.

Okay, so I downloaded the 64bit launcher, and copied it (and subsequent files) to the gw2 folder and switched out the 32bit launcher for the 32 bit, but it still keeps re-installing the entire game and keeps making copies of the other files. What am I doing wrong here? Was I supposed to rewrite some code or something?

^ that fixed my issue. So anyone who has any problems with running some 64bit programs on Windows 7 with the z97 chipset and i7 4790 it might be your only option to upgrade to Windows 10, as I spent over 2 days trying to resolve that issue. (using all of my IT knowledge 14 years experience and multiple certifications)

Cheers

Tonight a whole bunch of people crashed that were running 32-bit on WvW when a zerg jumped down on us,

memory use with 64-bit client was 3.9GB, close to 4GB. I didn’t crash.

One person using 64-bit crashed once, then I told him/her to turn off post process. They don’t crash anymore

Hmm interesting, i’m on z87 chipset so probably why it’s crashing instantly for me as well
Wonder if the 64 bit exe will be updated for compatibility.. because of the hassle, I don’t really fancy upgrading to W10 yet until dx12 is more of a thing in future games =(

My game feels smoother running around central Tyria, but my load times are upwards of 5-minutes now. Also the client slightly freezes anytime a window (inventory, trading) opens which I don’t get in the 32-bit. I don’t have any crash issues in HoT areas so far but do seem to lag more… possibly as my computer is a potato on Vista.

My experience, now that I’ve used the 64-bit client for awhile, is that it is taking an inordinate amount of time to load/render models. When I fight something, I have to do it blind, and just hope my attacks are hitting. I’ve not noticed much in the way of map loading time decreasing, but it might be slightly…just hard to say; it’s always been rather lengthy for some maps.

I wasn’t crashing before, so I may just go back to 32-bit, as I miss my FPS counter (which doesn’t work in 64-bit, no matter what settings/adjustments I try).

renaming gw2-64 back to the original gw2 exe file name after 2 starts seemed to got it running without crashing on startup

Rei Hino.5961:

renaming gw2-64 back to the original gw2 exe file name after 2 starts seemed to got it running without crashing on startup

hm i just tried that, unfortunately did not work for me

msblueness.6781:

My game feels smoother running around central Tyria, but my load times are upwards of 5-minutes now. Also the client slightly freezes anytime a window (inventory, trading) opens which I don’t get in the 32-bit. I don’t have any crash issues in HoT areas so far but do seem to lag more… possibly as my computer is a potato on Vista.

Sounds like your physical memory is simply so full that windows starts swapping
memory to your harddisk. So either upgrade memory, restart your client when
it starts to get bad, or do what always was the tip against OOM crashes : reduce
your settings.

Raikidd.5803:

Johan Skold.4708:

So for everyone with terrible FPS, are you on laptops?

I am.

EDIT: I just did this https://www.reddit.com/r/Guildwars2/comments/3ripme/64bit_client_feedback_bugs_and_more/cwof6y7 and is working good, maybe better that x32 ,I need to do more tests.

worked for me as well

Thado.7620:

hansQ.7985:

I’m having a problem with text and graphics overall becoming blurry when playing on 64bit client. Anyone got a clue what would fix this?

I am having the same issues, text and graphics are blurry and not as sharp as the 32 bit version. Has anyone found na a fix for this? I’ve added the exe in nvidia setting and all but it’s still blurry (I have everything in max settings)

Having the same problem as well. Everything seemed to run fine except there was this weird low quality blur to everything. I looked at my settings and when I auto detected graphic settings it set everything to a lower quality by default. I set everything to max as well but it still didn’t fix the issue either.

Auto detect is working differently for the 32 and 64 client (in my case): on 32 auto detect sets everything High/Med on 64 it sets Low/Low… I though it will utilize the hardware better not dumb it down.