Why is the version of DLSS used SO OLD?

[automata.]

First impressions in the menu, quality was fine. Once I get in-game, anything remotely at a distance looks far too soft. DLSS looks better in other games so I decided to see what version they were using in Hunt 1896.

Guess what? They're using 2.3.1. For context that version of DLSS is THREE YEARS OLD (Oct 11th, 2021). WE'RE CURRENTLY ON 3.7.20. The difference in quality between current and multi-year-old versions of DLSS is staggering and I never realized until a game "rerelease"/2.0-style update came out in August, 2024.

An entire year ago DLSS was on version 3.5.0 (Aug 28th, 2023). For how hyped up this addition to the game was this is absolutely pathetic. Updating it is incredibly easy Crytek. How did this go through? Please update to the at least one of the last few versions. Bonus points if you use DLSS's "preset C" which is tuned for shooters/games with constant motion.

[KC_MrGreen]

Originally posted by automata.:

Originally posted by Hermit:

https://store.steampowered.com/app/993090/Lossless_Scaling/

i suggest you guys to check out this software

Lossless scaling is a great program, but it's no alternative in this instance. I'm looking for a better image quality from DLSS's reconstruction that can be found in the newer versions. LS will give frame generation, but it adds a non-insignificant amount of input latency that doesn't have any mitigation like DLSS frame gen has with Nvidia Reflex. The difference in responsiveness between Hunt w/ DLSS quality mode vs Hunt at native res + LS frame gen will be very, VERY noticeable and make for a totally different experience.

If Crytek takes the time to add in DLSS frame gen support on top of an updated base version of the DLSS upscaler, then I won't complain. But if that happens I hope FSR3.1 + FSR Frame gen is added to have parity. At that point we're asking much more than a simple .DLL swap from the developer's side

Is it really as simple as that?!

[Killswi†ch]

I wonder why they went with this outdated version of dlss and fsr. As far as I know it's as easy to implement as copying updated dll files into games folder. The ghosting is pretty bad right now even with dlss on quality.

[Mac]

Did anyone notice those horizontal lines while using DLSS on quality?
You can see them easier while aiming.
No, it's not screen tearing, that's not like this.
Or is it just me?

[Killswi†ch]

Originally posted by Mac:

Did anyone notice those horizontal lines while using DLSS on quality?
You can see them easier while aiming.
No, it's not screen tearing, that's not like this.
Or is it just me?

Maybe it's there, but I haven't noticed. I played a lot during the weekend, so I doubt I didn't notice. I have dlss set to quality.

[Killswi†ch]

Originally posted by ЭКСГИБИЦИОНИСТ:

Lossless scaling is a great program, but it's no alternative in this instance. I'm looking for a better image quality from DLSS's reconstruction that can be found in the newer versions. LS will give frame generation, but it adds a non-insignificant amount of input latency that doesn't have any mitigation like DLSS frame gen has with Nvidia Reflex. The difference in responsiveness between Hunt w/ DLSS quality mode vs Hunt at native res + LS frame gen will be very, VERY noticeable and make for a totally different experience.

If Crytek takes the time to add in DLSS frame gen support on top of an updated base version of the DLSS upscaler, then I won't complain. But if that happens I hope FSR3.1 + FSR Frame gen is added to have parity. At that point we're asking much more than a simple .DLL swap from the developer's side

I wasn't talking about frame gen, only newer version of dlss. Still I could be wrong and it's not that simple.

[KC_MrGreen]

Simple or not, using totally outdated upcaling on the shiny new engine update is a little ridiculous..

[Mecharion]

Originally posted by KC_MrGreen:

Simple or not, using totally outdated upcaling on the shiny new engine update is a little ridiculous..

Indeed...

[automata.]

Originally posted by KC_MrGreen:

Is it really as simple as that?!

It *truly* is that simple. Nvidia made DLSS stupidly simple to update. Go ahead and try it, find a game you own that has an older version of DLSS. Inside the game files there's "nvngx_dlss.dll". Replace that file with the same file of the latest version of DLSS (can be found on TechPowerup, they archive all versions) and open the game. A simple drag and drop and you're using a 2024 version of DLSS. I've done this to great effect in single player games. Multiplayer blocks manually updating it more often than not, only exception I remember being MW2 2022 which also benefitted dramatically

[automata.]

Originally posted by KC_MrGreen:

Simple or not, using totally outdated upcaling on the shiny new engine update is a little ridiculous..

I agree, but the ungodly level of simplicity makes it all the more baffling. This is something they could do in all of 5 minutes, maybe less than that. If it's not included in the next patch I'm gonna be extremely disappointed.

[KC_MrGreen]

Originally posted by automata.:

Originally posted by KC_MrGreen:

Simple or not, using totally outdated upcaling on the shiny new engine update is a little ridiculous..

I agree, but the ungodly level of simplicity makes it all the more baffling. This is something they could do in all of 5 minutes, maybe less than that. If it's not included in the next patch I'm gonna be extremely disappointed.

Maybe they're just too busy messing up the rest of the game...

[Mecharion]

Doesnt the new version cost money?

[Collect - FDR's Wheelchair]

ok

[Lufi]

we need fsr3 !

[automata.]

Originally posted by Mecharion:

Doesnt the new version cost money?

DLSS has never costed money for developers to add ever since the SDK released. Many years ago

[Unknown]

Originally posted by automata.:

Originally posted by Unknown:

I'm going off of information I heard a long time ago, so this might not be the case. But if I remember right, for some of the newer versions of DLSS, they require you to pay NVidia to cycle through the game so many times, to train their system. Whereas this version is probably just plug and play.

Can confirm this info is from a *long* time ago. That's how DLSS1.0 functioned, it needed to be trained on a per game basis. Ever since DLSS 2.0 (many years ago) the machine learning component changed from generating all new pixel information to just intelligently picking what to keep from previous frames to give the impression of a higher res. Modern DLSS is universal, it's why you can mod it into games and have it work flawlessly. I myself have manually upgraded the DLSS versions in many of my games to get the benefits of the more upgraded reconstruction, but multiplayer games don't like it. That's why it's up to the developers to implement it. DLSS is 100% free across the board, all they have to do is drag and drop on top of what they already have and it will work.

Yeah, it was actually frame generation that I was remembering.