Guild Wars 2

Cbuzz.5083:

Going from DDR1333 to DDR1600 will net you basically ZERO fps increase. The speed increase is so negligible you will not notice any difference. Your issues are elsewhere & not in the memory speed.

In fact, going from DDR1333 to DDR2600Mhz will net you around 1-5FPS MAX in gaming.

I don’t know whether you read the post thoroughly or I didn’t write it well enough.

It wasn’t a post on how to increase FPS, it was on how to fix the terrible performance issues I and many others have had with our Nvidia cards that should run this game without breaking a sweat.

I am aware that memory speed doesn’t make a noticible difference (with discrete gpus, iGPUs are a different story) but after making this change my performance was back to normal. So if it is the RAM something weird is going on to cause such bottlenecking.

If it wasn’t specifically the RAM, it may have been the XMP profile settings. I’ll have to look further into it. It may have also changed CPU settings in additions to RAM frequencies.

EDIT: Looking into XMP a bit more, it only overclocks the RAM and doesn’t deal with the CPU at all.

My other system with has a Phenom II X6 1090T and 800MHz DDR2 played GW2 at almost the same FPS as I’m getting on my current system now, same video card.

Perhaps specific to Intel, perhaps even more specifically to ASUS motherboards with intel chipsets. I really couldn’t tell you why it worked, but the only setting I have changed in BIOS are to overclock the RAM and RAM only.

Might be some compatibility issues with that ram speed on the mobo or something. You don’t get any more crashes or fps issues, so whatever works.

Only thing is that it would imply that somehow a compatibility issue from a P55 motherboard managed to remain on a Z77 motherboard. A defect that went undetected by intel for several generations is highly unlikely, but still a possibility.

In tweaking your RAM in BIOS, it probably affected another part of the system that gave you your boost, although I can’t fathom what. The reason why a 670 lags is because of the drivers, cos there is currently an issue that SSAO is being implemented even when forced off.

That’s what I’m thinking, the RAM isn’t the main cause I think, but it might have been affecting another component, perhaps due to GW2 being very CPU bound the CPU was being bottlenecked by the RAM, though it doesn’t explain why it is specific to this game only, every other game i play ran fine at DDR 1333.

The reason why a 670 lags is because of the drivers, cos there is currently an issue that SSAO is being implemented even when forced off.

Perhaps this is causing some weird gumming of the works in the hardware, it would explain why it is GW2 specific and doesn’t affect other games. Its an assumption from far off in left field though.

EDITED to address various posters.

Addy.3751:

What chipsets are the two motherboards you tested using and what cpu? Sandy and Ivy bridge have integrated memory controllers, would seem odd that that 1333 would be a bottleneck on these two cpus. I have a 670 and 2×4gb 1333 haven’t noticed any real problems but if I could get a performance boost, be a good excuse to get 16mb of 1600mhz ram since it’s pretty cheap these days.

I have a Ivy Bridge i5-3570K, Z77 chipset

My friend has a Lynnfield (Nehalem based) i7-820, with a P55 chipset.

I would not have guessed that 1333 Mhz would be a bottleneck since it ran fine with every other game, but with GW2 specifically it simply fixed all our issues related to framerates by increasing RAM frequency to 1600 Mhz.

What is really odd about all this is that it ran just fine in the beta, and suddenly did all this mess after release.

I looked everywhere for a solution as to why my Nvidia GTX 670 was running the game so poorly, and I may have found it in the most unlikely place.

A couple of days ago I noticed that my RAM was running at DDR3 1333 (1333 Mhz), so I went into BIOS and used the XMP profile to increase it to the advertised 1600 Mhz frequency.

Afterwards GW2 ran perfectly, as in no lagfest in combat, as a bonus, no random crashing anymore. I even did this on my friend’s computer which was also having framerate issues and it also made everything run smooth as butter again. (He has a GTX 570)

It seems that the newer Nvidia cards (Fermi and Kepler architectures) can power through the data it receives from main memory (your RAM) faster than main memory can deliver the data, so the GPU sits there waiting for more data to crunch, leading to framerate drops and possibly system crashes.

The fix is to obviously increase the speed of main memory, incidentally many motherboards will downclock RAM to 1333 Mhz despite the RAM sticks being advertised as capable of 1600 Mhz, 2100 Mhz, etc. It not uncommon for crazy overpowered gaming rigs to have their RAM running at DDR3 1333.

For those of you with overpowered systems having framerate issues, check your memory frequencies, GW2 won’t run very well if you have a GTX 5xx or 6xx and your memory is running at 1333 Mhz.

Why a native client?

First because Cider/Wine is so hit or miss in terms of performance/stability that I am genuinely surprised they are even considering using it at all. Emulation layers just add more code that could go wrong, and if there is a problem in GW2 and the root cause is the fault of the cider layer and not the client itself we’re left out to dry because Anet has to wait for Transgaming to issue a fix, something it is well known for NOT doing in a timely manner whatsoever.

Secondly, just making a band-aid emulation port gives out the perception that Anet doesn’t want to invest the time and work necessary to make a quality Mac version of the game and is satisfied with the game functioning 80% of the way. “Good enough” shouldn’t cut it, especially when there are many many posts and articles where they talk up how they care about a quality experience, a Cider port isn’t a quality experience, its a slapdash quick-n-dirty solution.

This game is just too amazing for it to be marred by a poor abstraction layer. I really hope this is a stopgap measure until they get an actual native client out the door.