• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

The RT Related Games, Benchmarks, Software, Etc Thread.

Status
Not open for further replies.
DF DLSS 3 vid shows DLSS artefacts in motion in Spiderman in more than one occasion.
They have a list of known artefacts in motion to test for now.:p

There are artefacts, that's obvious but it's nothing like dlss 1 or fsr where their issues such as say severe ghosting was "persistent" across "all" frames, the scenes with FG where there are artefacts/issues is with the "fake" frame, which is between the "real" frames, this is why DF and HUB have to slow the footage down entirely or even to a complete pause in order to capture that e.g. this image here where you are seeing all 3 frames, the first and last are real, the second is the fake one, which has the artefacts:

hxr1bfg.png

Having said that, there is an artefact in the last frame there :p But it shows the issue well and is why as both have said, when you're running at 100+ fps in normal gameplay, it is very hard to show the issue, the HUD breaking is more noticeable and more of an issue than "gameplay" imo.

That or if you do what HUB did where you change the camera angle completely in f 1, the fake frame will **** itself due to the drastic change of the scene/frame.
 
So in summary, it's only **** when it suits your pov? :cry:

I've already stated where the issues are and if you watch Tims video, you'll see him saying exactly the same as I have pretty said in that post above, word for word of him showing all the issues like that f1 22 frame:

obviously this is an unrealistic situation because in a game you're not stopping to view each frame but the goal of dlss 3 is to hide these frames between the real rendered frames and fake its way up to higher level of smoothness provided the frame rate is high enough and these dodgy generated frames is shown only for a short enough time, you'll probably not notice what is going on and that is true, it can genuinely be hard to spot all of these issues that can appear so glaring when you view the individual generated frames. The big problem with FG is when you are using FG at a low frame rate
 
So would that suggest FG is going to be less of a plus further down the 4xxx stack. Plus, if it is unlocked in some way on the 3xxx and 2xxx cards, it may not be worth doing. Isn't that what the chap who got it working on a 2xxx card fund?
 
So would that suggest FG is going to be less of a plus further down the 4xxx stack. Plus, if it is unlocked in some way on the 3xxx and 2xxx cards, it may not be worth doing. Isn't that what the chap who got it working on a 2xxx card fund?

Depends entirely on FPS, if less than 100 fps, you'll notice the issues more easily, if higher than 100 fps, as per Tims own words (since DF are "shills" and not to be trusted even though they said the same.... :cry:), "genuinely be hard to spot all of these issues". I haven't looked/read too much into if the issues are less present when using dlss quality over dlss performance so someone else can confirm that aspect but the message seems to be it's all about what fps you're getting when using fg.....

Jury is still out on turing and ampere, the one guy who tested it is using a workaround specifically for CP (i.e. it's not hacked at the driver level but game level) and stated with his 2070, it was stuttery and crashing, he said he was going to try a 3080 but nothing since that post....

You could see the 'flickering' around spidey in the DF video when he was running up the building - no slowing down needed there. I don't know why so defensive over it - something that will I need to test for myself before deciding if it's a win or not.

Yup, you can definitely see some flickering in certain scenes, hopefully those things will get sorted with further iterations but I'm not sure how much can be done for this especially if/when you're at less than 100/120 fps.
 
Depends entirely on FPS, if less than 100 fps, you'll notice the issues more easily
Which is why it (in it's current guise) may not be all it's cracked up to be - Adding latency into a game which a 4090 is able to run pretty damn well anyway.

Without trying it myself, I'm not going to condemn or praise it..

What might be interesting is if, as part of DLSS 3, you could potentially have a slider to control the frequency of FG, to take advantage of the best of both worlds.
 
For those who actually care about the tech and are curious why that F1 22 "fake" frame looks so bad other than just using it for narrative purposes..... here is why it looks so bad:

Real first frame:

nTGG70i.png

"fake" second frame:

Fn6bt6Y.png

real third frame:

gOfazBj.png

As Tim stated, it's 2 very different frames when compared to normal gameplay of something like this.

Which is why it (in it's current guise) may not be all it's cracked up to be - Adding latency into a game which a 4090 is able to run pretty damn well anyway.

Without trying it myself, I'm not going to condemn or praise it..

What might be interesting is if, as part of DLSS 3, you could potentially have a slider to control the frequency of FG, to take advantage of the best of both worlds.

Precisely, just because the option is there doesn't mean it should always be turned on.

Alex summed it up well in this image of when it will really shine and you will want it turned on:

hoCWI76.png

Although I would use a lower preset of dlss like balanced or even performance to bring the latency down a bit more.

That would definitely be a good option to have and I wouldn't be surprised if we see something in the future.
 
Last edited:
It's not enough to make me come close to considering a 4xxx card though. 73fps and lower latency will win out for me of 109fps and increased latency. 30fps to 109fps? I'll take it, if it works as intended/promised. But only when it comes down to a somewhat reasonable cost. I'm not particularly hopeful for the 4080s at this stage, don't see them beating a 3090ti without DLSS.

Lower latency = greater immersion purely down to responsiveness. I have to deal with audio latency quite often with guitar modelling, and it's an absolute pet hate of mine.
 
contains a sweary :D read the board in the middle

Removed :p

It's not enough to make me come close to considering a 4xxx card though. 73fps and lower latency will win out for me of 109fps and increased latency. 30fps to 109fps? I'll take it, if it works as intended/promised. But only when it comes down to a somewhat reasonable cost. I'm not particularly hopeful for the 4080s at this stage, don't see them beating a 3090ti without DLSS.

Lower latency = greater immersion purely down to responsiveness. I have to deal with audio latency quite often with guitar modelling, and it's an absolute pet hate of mine.

For the price? Me neither. Even 4080 16gb not a big enough leap (unless it really pulls ahead in future RT games, which it probably will....)

I'm excited for FG and what it can offer (I've always said, I love how smooth games are when I can hit a locked 170 fps on my qd-oled screen, which is very hard even with dlss 2), imo, it's in a good state for first release, nothing like for example dlss 1 or FSR 1/2.
 
Miles Morale on the 18th November :cool:


Ray traced shadows as well this time!

- plague tale
- gotham knights
- miles morale
- Portal RTX
- witcher 3 remaster due end of this year too I think?

All RT games between now and end of December (might have missed a couple but those are the ones I'm looking forward to!) and of course CP 2077 getting increased ray tracing, good times ahead :D
 
Last edited:
Status
Not open for further replies.
Back
Top Bottom