DLSS
xess
DLSS | xess | |
---|---|---|
51 | 14 | |
645 | 525 | |
3.6% | 20.0% | |
2.6 | 3.1 | |
about 1 month ago | 10 days ago | |
C | C | |
GNU General Public License v3.0 or later | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
DLSS
-
Weird text on the bottom left of my screen while playing some games
Solved: https://github.com/NVIDIA/DLSS/blob/main/utils/ngx_driver_onscreenindicator_off.reg
- DLSS Super Resolution SDK 3.5.10 Released (nvngx_dlss.dll v3.5.10.0)
-
Starfield’s missing Nvidia DLSS support has been added by a free mod
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...
- Replying to comments: AMD Likely Blocks DLSS (Angry Fanboy Edition)
-
Nixxes graphics programmer: "We have a relatively trivial wrapper around DLSS, FSR2, and XeSS. All three APIs are so similar nowadays, there's really no excuse."
"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! "
-
Pro Modder PureDark says he will add DLSS3 in Starfield during the 5 day early access period
Literally. https://github.com/NVIDIA/DLSS
- Starfield Is AMD Exclusive PC Partner, as a NVIDIA User I'm worried this game will not run well without DLSS 2.0+ performance wise
- AMD is Starfield’s Exclusive PC Partner
-
Adding DLSS 3 to Unreal Engine 5.2 Games Just Got Easier with New NVIDIA DLSS 3 Plug-in (More DLSS News)
GameWorks on Github
- [TweakTown] AMD sponsored games with FSR don't feature NVIDIA DLSS support, and that's a little strange
xess
-
Replying to comments: AMD Likely Blocks DLSS (Angry Fanboy Edition)
The repository on Github does not contain XeSS either. It needs to be manually added as form of a plugin. But Intel does not seem to be interested in developing one currently at all (see here and here). So I wouldn't call that a proper solution and I wouldn't even say Intel is any closer to working together than AMD...
- AMD to bundle Starfield with Ryzen 7000 CPU series - VideoCardz.com
-
Nixxes graphics programmer: "We have a relatively trivial wrapper around DLSS, FSR2, and XeSS. All three APIs are so similar nowadays, there's really no excuse."
"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! "
- Boundary will no longer feature Ray Tracing, ditches DLSS over FSR & XeSS
-
A brief test on XeSS 1.1
XeSS 1.1 is open for download now. → GitHub - intel/xess
- Intel XeSS 1.1 released
-
"XeSS | High Quality Super Sampling from iGPU to dGPU | Intel Software"
Not at all, so far they've only provided (Windows) binaries without source and no concrete timeline for the actual open-sourcing of the underlying code. Definitely not like FSR which you can build from scratch by yourself and put anywhere.
-
AMD intentionally held back from developing a 600 W, US$1,600 RDNA 3 equivalent for the RTX 4090, feels mainstream gamers can instead spend savings on other PC parts
Nobody was saying "open source", just "open" as in the SDK is available here and runs on AMD, Nvidia and Intel GPUs, not just Intel ones. If they released XeSS and it only ran on Intel GPUs nobody would integrate it.
- Intel XeSS SDK 1.0.1
- Shadow of the Tomb Raider XeSS 1080p Prueba de rendimiento - Performance test (RX 590 R5 5600x)
What are some alternatives?
DLSSTweaks - Tweak DLL for NVIDIA DLSS, allows forcing DLAA on DLSS-supported titles, tweaking scaling ratios & DLSS 3.1 presets, and overriding DLSS versions without overwriting game files.
Streamline - Streamline Integration Framework
REFramework - Scripting platform, modding framework and VR support for all RE Engine games
FidelityFX-FSR2 - FidelityFX Super Resolution 2
Q2RTX - NVIDIA’s implementation of RTX ray-tracing in Quake II
FidelityFX-FSR - FidelityFX Super Resolution
LatencyFleX - Vendor agnostic latency reduction middleware. An alternative to NVIDIA Reflex.
Ro