The name makes me ask: Is that adding to the directory, as in side-by-side, or is it injecting into the game code? We’re not going to vet, research, approve, or support a third-party program, but I’m curious about how this works.
Hey Gaile, didn’t see this before but better late than never
The injector is a directx proxy, so it does not alter the game files at all.
It works like this, all native calls to Windows libraries are made to local dll’s before global dll’s, so by either placing a d3d9.dll into the GW2 folder or by adding a hardlink (virtual link) for the dll, GW2 will call that file first, the same way how FRAPS on other application add their injection proxy.
The d3d9.dll used for the AA shader injectors are going in just before the real d3d9.dll renders the image to the screen, this is needed to add post processing on top of the original image, like SMAA/FXAA, Bloom, HDR, Tonemapping and other graphical enhancements to make the game look prettier.
GW2 uses the FXAA implementation by itself btw. but it doesn’t offer the quality preset selection neither does it let the user control the sharpening that removes some of the FXAA created blur.
You can check out the image gallery I got on my revision control to see exactly what this is about: https://www.assembla.com/spaces/fxaa-pp-inject/wiki
I also got all code as open source, with exception of the dll, since I didn’t create it, neither could I get my hands on the source for it (would love to, since I then could add user selectable hotkeys).
I hope that brings some light upon what SMAA Injector, FXAA Tool and SweetFx are about.