Guild Wars 2

Hey guys, sorry in advance if a troubleshoot has been done recently on this.

I’ve been getting consistent crashes with the 32-Bit Client in full-map PvE Zerg meta events, so I picked up the 64-Bit Client to remedy that.

That worked out great, no more out-of-memory crashes, but my 64-Bit Client consumes ridiculous amounts of extra memory, causing ping spikes and frame drops, where the 32-Bit client is smooth as anything.

I’m in a lose-lose situation here guys, how can I fix the 64-Bit Client so it actually runs smoothly? I use Windows 10 and suspect some sort of connection.

64-bit client uses way more memory than 32-bit, nothing you can do about it. It’s still in beta so not as optimized, and add to this that 64-bit applications use more memory in general.

What can you do:
- lower/turn off some of the most memory-consuming game settings: Character Model Limit/Quality, Textures Quality, High-Res Character Textures
- turn off any extra programs while playing (including ones running in the background), maybe uninstall some not needed stuff
- last thing is adding more memory to your system… 8 GB is pretty much the minimum for 64-bit client if you want smooth gameplay and reasonable graphics detail level

Well, the ENTIRE POINT of using the 64-bit client was so that it WOULD have access to more memory to use. Of course it’s going to consume more in that situation.

Chaith.8256:

…I picked up the 64-Bit Client …no more out-of-memory crashes, but my 64-Bit Client consumes ridiculous amounts of extra memory, causing ping spikes and frame drops, where the 32-Bit client is smooth as anything.

…I use Windows 10 and suspect some sort of connection.

daft inquisitor.1605:

Well, the ENTIRE POINT of using the 64-bit client was so that it WOULD have access to more memory to use. Of course it’s going to consume more in that situation.

Since the 64-bit client should use more memory than the 32-bit, perhaps that is red herring for troubleshooting the other issues: stuttering and ping spikes. Those might be coincidental to your use of the 64-bit or might be due to using different graphic settings, e.g. if you set up you GPU to use specific settings for gw2.exe, you’d also have to teach it to use gw2-64.exe.

I’d recommend creating a support ticket so you can work with support (and being patient, since it’s a US holiday going into a weekend)

If you want to work on it yourself, use the world boss train to spawn your own zerg for testing. Then trim down all your graphics settings to the minimum you can tolerate. And compare results for 32-bit and 64-bit. Then, slowly start adding in additional shininess until you either get 32-bit crashes or 64-bit stuttering.

Tho tedious, it’s a pretty good way to rule out specific issues/settings. If you can narrow the symptoms or proximate causes down, it will be easier for others on the forum or on the support team to help with solutions you might think of on your own.

Good luck — please let us know what you find out, the better to help others.

PS Happy New Year.

What Agnes said. I have 8 GB RAM and run into some serious frame drops during very huge meta events. In those cases, I have to lower the graphics a little bit.

Those serious frame drops in zergs are nothing to do with memory; rather your cpu performance choking as everything gets thrown onto one core on gw2. Unless you have a massive overclock on an Intel i5/i7 from 2500k upwards, it will struggle in zergs. Best setting to turn down is character model limit and quality for this situation.
Use MSI afterburner and you can monitor ram usage in the background. When it gets close to using all resources the pc as a whole will slow down while gw2 is running. If you use the web while playing gw2 try and alternative browser to chrome on Windows 10 and see if it performs a bit better while alt tabbed.
8gb is more than fine for this game as long as you have closed down unnecessary crap in the back ground from running. GW2 on my rig on Windows 10 on pretty much max settings apart from the two i mentioned (and no supersampling) uses about 5.6gb of memory at the very most on the 64 bit client.