AMD FSR antialiasing discussion

Unless something has changed recently Pascal never exposed FP16 support in DX/VK. The 1/64 rate was provided in CUDA only for s/w compatibility reasons. (And I'm not talking about GP100 of course.)

 

this sounds correct with my experience. Thanks

 

FSR seems to be a combination of Lanczos based upscaling and CAS sharpening so nothing really new and kinda explain why Lanczos upscaled screenshots look very close to what you get with FSR.
Both passes are done in compute and can run in FP16 without quality loss.
There are some hints that future FSR versions may use temporal approach too.

That's another weird recommendation in AMD docs - to use FP32 on Polaris.

 

We've now corrected the slide deck and recommend the FP32 fallback for both Geforce 900 series and Geforce 10 series. Thanks for reporting this discrepancy!

 

Necromundi Hired Gun has adopted FSR and it had DLSS support already.

Comparison video showing the game running at FSR Ultra Quality and DLSS 2.2 Quality.

Judge by yourself. The video doesnt show any zoomed image but the difference doesnt seem big and it performs better with FSR.

 

Additionally, Marvel Avengers has added FSR support and also supported DLSS when it came out. Same comparison method: FSR Ultra Quality vs DLSS Quality.

https://imgsli.com/NjE0ODU
https://imgsli.com/NjE0ODc
https://imgsli.com/NjE0ODg
https://imgsli.com/NjE0ODk
https://imgsli.com/NjE0OTI
https://imgsli.com/NjE0OTM
https://imgsli.com/NjE0OTQ

Performance is about the same for both techniques in this game. Quality..., well, judge by yourself.

 

Obviously DLSS is providing a better image with reconstruction, more detail. Likely better in motion as well. This is a given since it's a superior technique that we've gone over many times but will be argued back and forth for the next week. There's zero surprise here.

Maybe some discussion can actually be had on specifically FSR without it degrading into the usual stupid wars... doubtful.

 

At the same input resolution yes but isn't FSR ultra actually running at a higher res than DLSS quality?

 

One good thing is it looks like FSR will not require any driver changes from the Nvidia team to get an acceptable result.

 

DLSS also has some annoying aliasing, you can see interior lines with jaggies. Wish they wouldn't oversharpen or whatever is going on there, as otherwise it does look better, but those jaggy edges are going to look worse in motion as well. But then that's my preference, for a bit smoother rather than oversharpened, I always turn down sharpen filters where available.

 

Yes, DLSS Quality is 1.5x scaling, FSR Ultra 1.3x

 

This should not matter much.

Spatial upscaling will always be worse on pixel sized geometry without MSAA or SSAA - wires, fences, tree branches, geometry specular highlights, alpha transparent textures, such as tree branches, leaves, grass, i.e. all foliage, all other high frequency geometry details will lose definition and these details not even have to be real geometry, per pixel material blending in shaders, POM like effects, thin texture specular highlights, etc, etc, all these details will lose definition.

All this stuff is visible in these screenshots - https://forum.beyond3d.com/threads/amd-fsr-antialiasing-discussion.62394/page-40#post-2215893

Temporal accumulation can reconstruct these high frequency details in pure accumulation mode, but then TAA cuts off most of the mentioned high frequency details with neighborhood clipping and adds blur instead by clipping color space of history to a color space of 3x3 pixels in the last frame, that's why DLSS often looks better than native with TAA.

Using TAA with FSR doubles losses - that's a combination of lossy neighborhood clipping with lower resolution.

AMD suggests using FSR with lower texture mip bias and I would love to see how it affects temporal stability (would be a very bad idea to do something like this in a game with MSAA for example), neighborhood clipping in TAA is good at cutting off high frequency signal, but any texture noise that survive should be quite apparent and can be futher exaggerated by RCAS.

TAA has it too since accumulation fails in the same cases for both, luckily aliasing can be fixed with image prefiltering with morphological AA, sad that no dev is doing this.

 

All these games which I don't have are getting patches.

The code itself can probably be optimized for Nv h/w though. FP16 version may run differently on Turing and Ampere for example. 16 series may need some special care as well.

 

First game to combine TAAU and FSR?

https://forum.arcadegeddon.com/index.php?/topic/101-patch-notes-013/

 

TAAU is an UE4 feature and can be used in a number of titles which support FSR.
Acradegeddon seem to provide TAAU as a menu option though.

 

Woah, that's interesting. Does anyone here have the game and can make comparisons?

Speaking of FP16, doesn't route Nvidia FP16 calculations through the tensor cores automatically? If so, I wonder if the upscaling cost is any different on RTX GPUs compared to RDNA2.

 

Can you enable both at the same time though? Since that was how I understood "Hybrid Upscaling" in those patch notes.

 

I'm assuming it's either or situation. You can use either FSR or TAAU to upscale from some lower res to your screen. Running them both don't make much sense to me. Chances are that TAAU with some CAS on top would produce better results than TAAU+FSR.

 

FSR shimmers a lot.