URP Camera Stack and Anti-Aliasing

A brief temporary summary:

The fact FXAA affects all cameras including ones on the camera stack and SMAA only affects the base one, makes it a poor choice to put them together for users to choose from.
I personally would consider this a bug.

----------------------------------------------------- Original Post --------------------------------------------

I've been using a separate Screen Space Camera for my UI canvas. Now that I'm trying to migrate to URP, I understand that I need to add the UI camera to the base camera's Stack for it to be rendered.
But the result is wrong due to anti-aliasing (FXAA) applied after everything.
So, is it possible to skip AA for the overlay cameras? Or am I doing it wrong adding a UI camera to the camera stack?

Plus I find it weird assigning a ForwardRenderer to the UI Camera.

 

Oh, another question. I found docs on version 9.0, but the source is no where to be found. https://github.com/Unity-Technologies/ScriptableRenderPipeline seems to be either removed or private now (I still have a local clone of 7.1.1).
So the source in development is no longer available right?
------
Never mind. I found it at https://github.com/Unity-Technologies/Graphics.

 

After digging into the source a little I feel like understanding why it's not obvious there should be a switch for skipping AA. But doesn't it look like a lot of people will be needing such a switch? I want to use multiple cameras but I only want the first of them AAed. I guess I'll have to render the overlays on separate textures and blit them AfterRendering + 2?

 

SMAA happens a lot earlier and therefore won't affect overlay cameras!
Seriously, even just for the sake of consistency, FXAA shouldn't affect overlays either, or they don't belong together on one drop-down list.

 

I'm experiencing the same thing. SMAA is applied after the base camera, and FXAA is applied after each of the overlays. I agree with the OP that this is considered a bug since it's not consistent. Would be curious to know if there's a way to control this as I'm in the camp that wants AA to be applied after all overlays (depth buffer seems to be cleared after SMAA applied on base but I need to access it for an overlay camera). Whereas the OP seems to want it to be applied to the base camera only.

 

Bump. I'm having this issue as the FXAA affects text mesh pro and I have my 3d camera and UI camera on the same stack. I want FXAA to affect the 3d camera only, but the AA settings only exist on the base camera

 

I had similar problems with different camera configurations (stacking UI from different space). After messing around with the initial camera stacking feature provided. I simply gave up and concluded that it is faster that I implemented my own custom ScriptableRenderers that do what I want for each different cameras and have them output to a temporary RenderTexture which gets collected by the "master" camera with the default ForwardRenderer via a custom RenderFeature.

It was such a pain to realise that having different viewports is not supported by the packaged camera stacking feature.

 

This is really annoying

 

Crazy that Unity does this but you are right, it is just an issue that they obviously never foresaw when implementing FXAA. Just did a quick check of my own assets AA (DLAA), and it works perfectly when stacking cameras, not affecting the world-space UI camera in this instance. Quick little comparison here: https://imgur.com/a/RWvPNFr

 

Yeah this really sucks. For mobile I'd prefer to run FXAA and SMAA on PC/consoles. But since FXAA messes up TMPro fonts that's no really an option. This setting should be per camera or at least off by default on stacking cameras for both FXAA and SMAA.

 

i just wanted to pile on here to say this AA situation is confusing and inconvenient. my main issue with it is also that FXAA destroys textmeshpro rendering.