Guild Wars 2

Greetings all.

First of, if im blind and have failed misserably at searching the forum please do tell me if there is a thread about the new culling feature.

Ok so .. on to it.

I just want peoples experiances with the new culling options in WvW zergs.

I personaly have the settings maxed out so bassicaly culling is off and textures r maxed.

Obviosly culling does help with FPS still if u turn it on, but i also found that turning the textures down helped with the FPS even when u have GPU headroom. Now obviosly this is becouse the CPU still has to do some of the work and any extra head room u give it in WvW will help with the FPS, but i found that at the most it only added maybe 10FPS going from Low to Highest on the texture setting.

10fps is ofc alot for some, but tbh for Gw2 alsong as i stay above 30fps at al ltimes i dont mind. And my average is usualy 45+.
That said i really couldnt tell the difference between highest and low texture settings when in the thick of battle, so i may end up droping it to medium or low just to gain an extra 5-10 FPS in those intensive situations.

At max settings i still kept my minimum FPS above 30, and gained, thanks to this patch, a much better view distance.

All in all it seems good. I honestly havnt been on GW2 much in the last month so i cant recall very well if the performance has improved along with this change, so more feedback would be helpfull.

I noticed an improvement being able to view everything but for me the performance got worse. I tired Low/Low and High/High and everything in between.
It seems that the ability to view all the other players(culling) is offset by the sheer numbers of people. I am talking about the giant zergs of course.
X61055t OC to 3.5ghz is not a high end cpu but it really isnt a low end one either. My gtx 680 did the usual dip during high zerg battles but that is expected with the bottleneck.
I think that people with high end systems(ie 3930k@4.6) will benefit more so than the person with an average to low end system.
They seemed to put the end user in control of the issue rather than fix the engine itself which seems to be the cause.