DLSS VS FidelityFX-FSR2

Solved: https://github.com/NVIDIA/DLSS/blob/main/utils/ngx_driver_onscreenindicator_off.reg

Also DLSS has pretty strict requirements in advertising, requiring nvidia logo & adverts on splash screens and give nvidia any rights to use your app in their own advertising. [0] It's certainly not "free". A completely night and day difference to FSR, which just uses MIT [1]

Lots of people online seem to believe both are "free", so the only reason why you wouldn't implement one is some back room deal. But in my experience, just getting everyone into the same room to sign off on things like that is hard.

[0] https://github.com/NVIDIA/DLSS/blob/main/LICENSE.txt

[1] https://github.com/GPUOpen-Effects/FidelityFX-FSR/blob/maste...

"IT doesn't work that way. DLSS may be a click in some Unreal Games, but custom engines? Yeah, no. You need to modify the code to implement it, which is PROHIBITED by the license Nvidia has you accept when you accept their SDK terms: https://github.com/NVIDIA/DLSS/blob/main/LICENSE.txt DLSS is not FOSS (Free and Open Source) like FSR. For comparison, FSR's license that lets you do whatever the hell you need to get it functioning in the game or improve performance: https://github.com/GPUOpen-Effects/FidelityFX-FSR/blob/master/license.txt Blame Nvidia for devs not wanting to touch non-free code and enter a legal agreement where they may be litigated down the line...for implementing a technology that SELLS Nvidia GPUs. It's literally like me threatening to sue you for bringing customers to my business. Again, blame Nvidia. By the way, they are also the one that sold you the feature, so let them be the one to implement it. I keep hearing Nvidia is a "god tier software company" but can't implement DLSS on the driver side? Somehow I don't buy it, especially when they release game-ready drivers anyway. And before someone brings up the BS argument it needs game data, anyone can find those memory addresses to get to the engine or they can ask. Considering they are Nvidia, don't think any game dev will keep silent about it or how to interface with their game if there are driver issues. EDIT: Also just so you know, XeSS is also under a similarly stupid license as DLSS XeSS License: https://github.com/intel/xess/blob/main/licenses/LICENSE.pdf Keep in mind this nugget from Intel's license: "No reverse engineering, decompilation, or disassembly..." Only issue is that games need to be DECOMPILED when DEBUGGED! "

Literally. https://github.com/NVIDIA/DLSS

GameWorks on Github

- https://github.com/GPUOpen-Effects/FidelityFX-FSR2/releases/download/v2.2.1/FidelityFX-FSR2-v2.2.1-prebuilt-sample.zip

AMD's scaler is open-source. Here's the github for FSR2.

Sure, go ahead: here is the link. Go contribute and make it better, as it's an OPEN SOURCE project.

DLSS is a proprietary black box that developers have no control over (bad). FSR is open source, you can check the code, fix the code, modify the code, and port it to new devices (good). It also means there is a community of developers who are trying new things and submitting code for inclusion (there are currently 148 forks on the github).

literally not true. FSR has been constantly updated in the background and 2.2.1 was released 3 weeks ago.

If I get the FSR API files (ffx_fsr2_api_dx12_x64.lib, ffx_fsr2_api_vk_x64.lib and ffx_fsr2_api_x64.lib) from github what directory structure do they need to go into? Looking at working DLSS and XeSS as a template...

From the official docs: