Guild Wars 2

I’d like to see flaming phoenix wings.

This is awesome, a much needed improvement to GW2. Been using it for a few hours now no problems at all. Now all we need is for Anet to implement directx 11/12… what…? A man can dream of a zerg without low fps.

On a side note, if you are using GemFX make sure you tick 64x bit application otherwise none of the effects will work on the new x64 client. Also if you are using Nvidia Inspector to force vsync or any other settings then you have to click the little “+” icon at the top of the tool bar that says “add application to current profile”. Navigate to the new Gw2-64.exe and hit apply. Now all of your Nvidia Inspector settings should work as well.

I cant say that I’ve really noticed an fps drop (running a GTX 670). Have you tried turning off Ambient Occlusion/Best Texture Filtering/light adaptation/lower collision sensitivity, those were the settings that cost me some fps.

I’ll put a screenshot of my settings below. I get anywhere from 25-45 fps in big zergs, 60 pretty much anywhere else. Certain world bosses take me as far down as 20, but not very often at all.

If your also desperate for more fps, you can always lower your FoV.

Hope that helps a bit, see you all in Tyria!

Awesome outfit, this gives me high hopes for the new legendary armor!

Paul.4081:

Thanks Hidori, that’s pretty much what I was running but at x4. Just needed that compatibility flag you posted and now I’m back to looking good and no flickering with post processing on.

Cheers!

JohnnyS I remember in Borderlands 2 the anti aliasing wouldn’t work unless I had both settings at x2 or x4, if one was at x2 and the other at x4 it wouldn’t work.

Yah, I made sure TRAA and MSAA were set the same (both 2x AA or both 4xAA), but still nothing. Again, I managed to get SGSSAA working (although I don’t want to use it because of the fps drop/it blurs the screen quite a bit), it’s the regular 4x MSAA that won’t work. Besides, GW2 is suppose to have better performance and compatibility using the 0×00401044 (L.A. Noire) flag and my settings of 4xMSAA + 2x SSAA worked incredibly well before. Regardless of this other AA flag working or not I want to know why the 0×00401044 (L.A. Noire) compatibility flag stopped working all of a sudden with the newest Nvidia drivers.

Oh well, I guess I will just have to accept that some things break and there is nothing to do about it. I appreciate the help though. See you all in GW2!

This thread on reddit has some relevance so I thought I would link it
https://www.reddit.com/r/Guildwars2/comments/3ex5q2/smaa_possible_via_xml_edit/ctjc4of

Paul.4081:

Exact same thing here on 780ti. Same compatibility flag.

The only way I found to remove the flickering and occasionally having no textures (everything is grey) was to turn off Post Processing. Even with Post Processing off however my character selection screen remains all messed up. When I turned it (PP) back on later in LA everything went black with coloured outlines.

Everything else works fine, I even tried PP on with the new light thing off, same result until PP is fully off.

Update – Weird, I went to Hoelbrak and the giant ice sculptures were rainbow coloured & Asura gates flickered. I alt tabbed to say turning off Post didn’t work but when I alt tabbed back everything was normal again.

Thanks for sharing. I did notice a bit of improvement when turning off PP, but the flicker is still definitely there. Alt tabbing didn’t seem to do anything for me either. Oh well, at least I know I’m not alone in this!

Hidori.3472:

try this:

Open NVIDIA Inspector and click on the crossed wrench and screw icon.
Under Profiles select Guild Wars 2.
Under Antialiasing compatibility insert the flag 0×084012C0.
Under Antialiasing fix select On.
Under Antialiasing – Behavior Flags select None.
Under Antialiasing – Mode select Override any application setting.
Under Antialiasing – Setting select 2x Multisampling.
Under Antialiasing – Transparency Supersampling select 2x Sparse Grid Supersampling.
Click Apply changes.
Information You may use higher anti-aliasing, if you can run it, but both antialiasing setting and antialiasing transparency supersampling must match the number of samples that are being used.

http://pcgamingwiki.com/wiki/Guild_Wars_2

tried it just now and it worked fine at a world boss.

Hello, thanks for the reply!

Unfortunately I just tested this, and while Sparse Grid Supersampling does indeed work, regular MSAA is still jagged as hell/doesn’t work with this flag. It also seems like transparency supersampling (2x, 4x) still isn’t working with these settings either (Sparse Grid Supersampling tanks my fps so I couldn’t use that even if I wanted to). Out of curiosity, which graphics card are you using?

Hey all,

I’ve been having this problem for over a month now and it involves forcing AA through Nvidia Inspector. I use to play at 4x MSAA + 2x SSAA and it looked and worked beautifully! That is until I noticed that updating my Nvidia driver past version 350.12 (I’m using a GTX 670 FTW) caused really bad texture flickering (parts of the screen/ my characters flash black/grey/blue). The weird thing is my friend just built a brand new computer (GTX 970) and he has the exact same flickering when updating past 350.12 as well.

I noticed that it is only triggered when selecting “Override Any Application Setting” under antialiasing – mode in Nvidia Inspector. I’ve tried doing a clean install of my drivers, made sure in game AA was off, I have the correct AA compatibility flag (0×00401044 L.A. Noire), I’ve tried everything to no avail.

I know people are going to say “just use in game AA”, but I’m really OCD when it comes to the visuals in my games, especially aliasing. I’m guessing the fault lies with Nvidia, but I’m curious to know if anyone else has this problem and/or if they’ve found a solution.

Thanks in advance guys!

The real question is where are the fiery wings at? There are plenty of fiery armor sets, why no wings?

Finally some official word from the devs…