Guild Wars 2

OK, so I had SweetFX going fine until the August patch or whatever it was that made it so that the d3d9.dll, dxgi.dll and injector.ini files needed to be moved to the /bin folder but I still can’t get it to work properly.. I think I have the folder an files in the correct places but it doesn’t toggle on when I’m pressing the Screen Lock button.. I’ve made sure it isn’t the settings file because I use the same files/version it with Elder Scrolls Online and it works perfectly there. I have a GW2 specific preset setting but I also copied the settings I have for ESO and that doesn’t work either. The game launches fine and doesn’t have any errors, it’s just that I guess somethings wrong with where I have my SFX files because that won’t toggle on. And at the very least want to use SMAA. Using SFX version 1.5.1
So I have whole SweetFX folder in the Guild Wars 2 folder where the executable is and I have the d3d9.fx, dxgi.fx shader.fx, sweetFX readme.txt, and the sweetFX Settings.txt files all in there.
And then in the bin folder I have: d3d9.dll, dxgi.dll, and the injector.ini files.
Anyone know what’s wrong?

Here’s the bin folder.

Got the same issue, though I can usually play the game with SweetFX still on after clicking away the warning a couple of times…
It happens again when I open the Black Lion Tradingshop

From what I’ve read on the interenetz is that this is an issue between SweetFX and Windows 8.1 – what is confusing however is that this only happened since a couple of weeks back… Plus, you do not seem to have Windows 8.1

I also tried a “fix” that was suggested with using RadeonPro, but this sadly had no effect. Removing SweetFX removes the warning, but in turn you miss it…

if you have an nvidia graphics card with an older version of geforce experience installed, that could be the issue.

There was an issue with shadowplay/streaming overlays and sweet fx, but that was fixed in an update. So check to see if you have any driver updates.

dodgycookies.4562:

if you have an nvidia graphics card with an older version of geforce experience installed, that could be the issue.

There was an issue with shadowplay/streaming overlays and sweet fx, but that was fixed in an update. So check to see if you have any driver updates.

I had GeForce Experience removed because of this last time, so it could not be it on my part :P

Dunno about the OP though…