FXAA whiting out on windows editor

[tenpn]

Hey,

We're using the fxaa plugin in 2017.4.5. On mobile, the plugin works great and seems better on a wider variety of older devices than unity's post-processing stack. However in editor on windows, it to introduce a lot of alpha to the image that wasn't there previously. This makes it seem whited out in the editor and dark when saved to disk.

Since this is a mobile game it's not a huge deal, but if there was an obvious reason why fxaa would be introducing a lot of alpha on windows in unity 2017.4.5, it would be nice to be able to fix it.

cheers!

[tenpn]

Oh our setup: a camera pointing to a ARGB32 rendertexture that's then rendered in-game on a raw image inside a canvas.

[Amplify_Borba]

Hello, thank you for getting in touch!

We're happy to know that you find our plugin useful and superior to other solutions, however, FXAA is primarly used for camera AA, not necessarily for RT rendering, so something might not be working as expected.

If you could provide us with a sample with this issue present so that we may investigate this situation, we could likely offer additional insight.

Thanks!

[tenpn]

Sure thing, here's a 2017.4.5 project that shows the issue: https://www.dropbox.com/s/aad2r0m3z3yob ... e.zip?dl=0

- A main camera containing a canvas, containing a raw image, pointing at the render texture
- A second camera pointing at the render texture, with FXAA attached
- The render texture camera contains a sprite renderer displaying the "customizerbg" sprite

Here's an image showing the scene view, with the render texture camera on the left and the main camera on the right. The right image is semi-transparent:

Let me know if I can give you any more info. Hopefully I've just done something dumb.

[Amplify_Borba]

Thank you for taking the time to send us a sample, it seems that the shader is not taking the alpha into account, which might be something that we'll have to adjust on our side.

I'll register the issue and pass it along to the developer, however, it could take some time to investigate it as we're currently a bit overloaded.

We'll be sure to get back in touch once we have any developments regarding this, apologies for the inconvenience.