Oh man the amount effort you put in making two 15 minute(ish) videos a day on such topics is mind blowing, well done Phillip ! Keep it up 👍

Input latency has always really bugged me. I personally hate it worse than lower framerate.

Exactly ALL of my thoughts on this tech in one video, wild. Input latency is paramount for me even in singleplayer games

thank you for this video phillip

I find the input latency these options have is a big turnoff for me; as you said, it is very noticeable, and bogs down the gameplay. That said, I do like where this technology is heading.

I think this would be most useful for really old games like okami that have their physics tied to their frame rate and could use the frame rate boost even if artificially.

Thanks so much for pointing this out. I have the exact same problem with DLSS3 image interpolation. If you already have high frame rates you don't need even more to make it even smoother. What matters most (at least for me) is the input lag!

Love how many videos you create recenetly. Keep it up man it's really great!

Great video 3klicks, I always appreciate your in-depth analysis of everything. I miss your map analysis videos of CSGO, scrutinising all the changes was interesting

what I like to see is a way to set DLSS3 to a target FPS. If you dont get the targeted FPS there will be generated frames to smooth out the image.

I finished A Plague Tale Requiem on my 4090 today at 4K120. I used DLSS3 with DLAA OR DLSS2 at quality with no frame generation swapping back and forth through out the game. I played the game on a dualsense controller. Using a controller the increased input lag of DLAA + DLSS3 vs DLSS2 quality wasn't noticeable for me, the difference in input lag according to nvidia's overlay was around 20ms between them. The biggest issue I had using DLSS3 was going over 120 FPS and getting screen tearing. DLSS3 was extremely impressive at certain points in the game where I was CPU or engine limited (my CPU is a 12700k at 5.4ghz 2 cores, the rest of the p cores at 5.3ghz with 5200mhz DDR5). This mainly happened in cities or a couple of times when the game seemed to only want to run at 60ish fps leaving CPU and GPU very under utilized. I didn't notice any visual glitches at all with DLSS3, although this game has a lot of walk and talk sections where the HUD is hidden so is probably fairly ideal in that regard. Most of the game DLSS3 was over kill, although if they add ray tracing in and or on the mid range or low end 40 series cards it would be very useful - at least to me. Overall I was quite impressed with it and it doesn't look like your TVs fake interpolated frames (soap opera effect) at all - it looks like real higher FPS to me in this game, but really wish they have a reliable way for it to function with frame rate caps and or vsync without destroying input lag even more. I couldn't get a FPS cap or vsync to work at all in this game with DLSS3, even forced through control panel etc. I 100% agree with Philip's assessment that it'll be worse than useless in some situations like competitive FPS etc and awesome in others like slower paced single player. I think for games like A Plague Tale it was a good fit, at least to me.

Your reviews, opinions are the most important for me in the whole internet. Why? Because you do it from an ACTUAL gamer perspective, with focus on the feel instead of technicalities.

Great video :) I really wanted to hear about the input lag feeling, You can always tell when the mouse is not 1 to 1 with inputs

Do NOT hit the Vsync limit or use any FPS caps while using DLSS3 frame generation. It will raise the input lag and it also introduce stuttering with a FPS cap. You need to stay below your maximum refreshrate only by increasing the graphics settings. It can get tricky when your display is only 120Hz max. I think DLSS3 is a feature for graphic whores, who like to play single player games. For example Spiderman at 5760*3240 via DL-DSR + DLSS2 quality + DLSS3 frame generation and all other settings maxed out. Looks absolutely insane and plays wonderfully without any obvious artifacts or bad input lag on an 120Hz OLED. Average base framerate while swinging near above the streets is roughly 45-65FPS and 65-90FPS with frame generation enabled in this game.

Dude you are the best KZfaq er. When you beat dirt rally 2 and revealed only at the end that you ripped it on keyboard is still a highlight for me lol.

so cool seeing this tech being a thing.. I think it's possible to separate controls and attach it to the generated image.. but can't wrap my head around it either. When everything is dependent on fps, I feel like the more complicated the game, the harder it would be to implement it.

Issues with 2D elements like HUD, menus, overlays, etc, have been an issue going back to the very first AA methods. It'll get sorted eventually.

Good video! I guess one of the points I was waiting to be brought up was the effectiveness of DLSS 3 when generating frames for low FPS games, like 30 for example. One of the things Digital Foundry found was that there's often not enough information in 30 fps to interpolate well in various scenarios, but it doesn't seem like that was your experience.

Everyone says it increases input latency so its bad for competitive games, but there are practically no competitive games that are taxing enough to need something like DLSS in the first place. They all run on toasters, which what makes them so accessible and popular. If you have a DLSS capable card, then its likely already far powerful enough to run esports at high framerates natively. DLSS was designed to be a solution to increase low frame rates, particularly with raytracing. (And games with raytracing tend to be slower paced games too) Not boost high framerates even higher. But I guess people decided it must work for every scenario well for it to be good rather than use it where it makes sense. Applying a solution to an suboptimal situation it wasn't designed to solve. Right now it only makes sense to use on lower end cards, but as new games come out, the lower end cards will be able to have a longer lifetime thanks to DLSS and even FSR technologies.

My mind kept going to Steam Deck during this vid. Glad to see you came to the same conclusion -- it would be the most ideal use case without a doubt!

Good video on graphical topics, as usual for you Philip. You always manage to explain stuff like this in a down to earth way, so I like coming to you for news and developments a lot. Say... Speaking of news and developments, you've mentioned Cyberpunk a lot in these videos lately. Do you think you'd ever do an update video on what you think of the game after it's been patched now? I'd love to know your thoughts on the world and story, whether you think after patching it can be viewed as a good game. Recently played through it myself and I really quite liked the game.

Ever since timewarp was added by oculus I have always wondered why it can't be applied to mouse movement glad someone else had the same idea. I think it's totally doable, extrapolation and interpolation should be combined just like vr does. extrapolation can actually give you lower lag then native rendering because you can just shift the image at the last possible moment when you wouldn't have time to re-render a whole frame the traditional way. at lower framerate the difference in lag between timewarp rotation and normal rendering will be dramatic, also mousefeel will be consistent at any framerate! and you won't get stutter. it's just win win win. It seems crazy to me that this hasn't been explored yet. you could have the mouse feel of 1000fps at any framerate!.

YES! THANK YOU. You are so god damn right on this one!

The cyberpunk example at around 8:30 really highlights the usefulness at lower framerates

Great video, this is good analysis

Really honest review. And it's not often happens on KZfaq lol. Thanks!

You are exactly right about taking input data and reducing the latency. Since they are using a machine learning step, additional data can be incorporated with the proper training. DLSS 2 was improved this way by adding more metadata like motion vectors. It may require some level of mapping for that particular game into a standard input dataset like defining what control moves the view and character or jumping etc. This way a future frame can be created based on the latest sampling of input, and potentially a huge increase in the amount of generated frames too if the tensor cores have performance headroom. The game logic/physics would also need to run at this higher rate to actually benefit from the finer control. This might be a while (DLSS 4/FSR 4), but in general deep learning solves problems like these pretty well, when there is diverse non-cohesive data, if built right.

you can really see the mouse input and game frames being separated when using (in my case) the quest 2 with a pc, when the games stutters, you can still look around the frozen frames

I love these videos and thank you so much for helping inform us!!! Would it work to upload a short 4k 144hz video file online so we can download it and play it offline to see the effects more clearly? Cus yt's framerate locking is annoying

I think this has a lot of potential on consoles where they're targeting 120fps at high resolutions. It would need to be an option obviously to disable if you wanted but it could also help with new releases a few years down the line and getting 60fps then.

Very helpful analysis

Very interesting video. I had been putting some armchair theory towards figuring out what to think about DLSS 3. But there's no replacement for hands-on experience :) I think I would tend to just avoid it. I 'always' disable motion blur (and depth of field, and v-sync).

The input latency and the tearing would probably mean I'd never use DLSS3 as I'm quite sensitive to the feel of the mouse, competitive title or not. Thankfully if you have a 4090 everything's going to run well anyway

Thanks for your analysis! I came to the same conclusion as you and I didn't even use it yet. I do have a bit of experience in FPS games, dealing with how poorly my 3950X microstutters in many games, plus plenty of interpolation and video techniques through editing and video encoding. I was presuming that the visual artifacts were going to be a non issue (since VFX + video editing is all about focusing the viewer's eye), and that the input latency was going to be game dependent. I wouldn't exactly call FS2020 a game where those extra 20-40 milliseconds matter, as I'd imagine that getting 50+ FPS in LAX or JFK would be much better than getting 25 FPS.

Just here to say that Requiem is my favorite game of the last couple of years. Needed to get it off my chest. Nice video btw.

dude when that music kicks in in your videos my dopamine rises UP

THANK YOU for this video. I do not care at all what it looks like when you slow the footage down. I want to know what it FEELS like as a gamer. This video is perfect, and hits the nail on the head of what gamers actually care about: the feel and general experience of the new tech.

Great and very informative video

I saw your comment about separating HUD elements from the game world, this is already a thing in most Engines like Unity/UE. More things than you might think are separated using a priority system. Afaik, the HUD is rendered first, then rougher objects like walls, roads, houses etc, then translucent objects, and lastly refractive objects, mostly based on the type of material the object uses. And so the cleanest solution to DLSS3 interpolating the HUD would be integrating the frame generation into the game engine itself rather than having a universal frame generator for every single game.

Alright, that was quite insightful

I found that when using higher sensitivity’s u could feel the latency more in fps games, and with a slower more csgo styled sensitivity that most pros use made the games feel way better with DLSS 3 and slow sensitivity. Thanks for this video ❤️❤️👍 I am having lots of fun doing almost the same stuff your doing right now, hopefully we will get this to gaming consoles in the future by xbox and sony.

I played through RDR2 with DLSS on and it was pretty good. The biggest issue I noticed was when there were a lot of smaller "high contrast" areas, for example grass on slightly snowy ground. When you moved the camera it blurred a bit and when it stopped immediately went back into high contrast so that was notable. Otherwise it really didn't show that much. From a few other games I did notice some of the smaller shortcomings. In "Resident Evil 8" smaller lighting details like lit candles vanished on a greater distance. In "Supraland: 6 inches under" some glass panes have a grid pattern on them, that became noticeably rougher when you stood just a bit away than on full resolution. I think DLSS is a pretty good tech and sure hope they manage to iron out the flaws with it some more in the future. I'm no programmer so I have no idea if that is possible but it may help with preserving some details better if certain items in the environment could be tagged in the engine to render as a higher rez overlay and then put that on top of the rendered frame.

I wonder if you can replicate the feel of 144fps video if you slow down the video to 60fps and let the viewers increase the playback speed

As you already said, it depends on a lot of things and especially the game itself. In my opinion dlss3 is almost a no brainer in games that are like Cyberpunk, RDR2 or other singleplayer adventure games because the input lag you get is simply not a big enough deal while in CS or Overwatch or any other comp game you obviously don't want it on since it's that precious input latency + you most likely already have your monitor's refresh rate fps or higher to begin with

It would makes sense for them to eventually introduce adaptive interpolation, which kicks in when you have low fps for long enough. Maybe it can already see the "real" framerate, the only thing left would be to calculate some rolling average based on it. Doubt they'll spend time on that though, as super-high-fps benchmarks is what sells their cards

Just tested it in FS2020 with target frame rate 60 and it's working pretty well! The latency becomes really bad (comparable with my TV with its own frame interpolation enabled), but it's still playable and overall a much smoother experience than the 45 - 55 fps I normally get due the main thread being saturated. Note that I had to force v-sync in the NVidia control panel (as Digital Foundry found out) and also disable RivaTuner's frame limiter (which in my case caused 1 frame to drop each second, resulting in slight, but noticeable stutter).

Wouldn't dlss3 also be less effective in lower end cards as they'll be slower to actually generate the frames?

There are just too few games out with DLSS3 rn to test it properly. The issue I also have is, that most of these games have a fixed character camera, when I'm then moving my mouse it only needs to pull the info from the depth buffer and basically only needs to work out what gets priority in taking up more screen space since it not like updating 5 out of every 6 frames generated, I think the overhead is pretty minimal. We's need a game where if you have a fixed character camera, and object in the distance needs to raise from a very flat position while it's raising to like 45° angle then flip to the side and rotate continuously and also change the distance to the main character drasticly back and forth. Only thing I can imagine doing that in a game and with this dimensions would if you had an arcade-type yet fighter game...

I was hyped for the DLSS3 mainly because I game on a strobed display, and having a proper strobed experience on a 240/280Hz panel demands that you have an FPS equally as high as your refresh rate, which is asking a lot from my CPU in quite a lot of games where I'd be lucky to even get 144+.

You're correct. One simple prove is that people all watching game play on 60 fps at most at youtube or twitch, nobody would say it feels lagging or not smooth. Frame rate is all about the input responsiveness.

I think I know why DLSS 3 includes HUD elements for its frame generation. If I recall correctly from the DLSS 3.0 presentation, they specifically said that the frame generation is made possible in real time by using the final framebuffer instead of 3D data. They only use the motion vectors for masking, but the AI for the interpolation only uses the final image. This is why it can not make a difference whats on the screen at the time. At this point I don't think its possible to come around this issue, since adding new information to the process (like Z buffer or other 3D data) would make it more precise but also slower, defeating the purpose of the interpolation.

Game developers could maybe focus more on general engine latency in future titles to compensate for these features. Digital Foundry tested latency a few years ago and shared the data in DF Direct Weekly #82 (at 47:25). Latency varies greatly between titles, some do a way better job than others.

I've been wanting to ask someone else who I think also has sensitive eyes like me. Have you noticed some car LED headlights flicker instead of look solid?

Most GPU work is usually queued the display of frame-to-frame is entirely dependent on whether the GPU itself is ready to display it (and as devs we don't really have full control over this); DLSS is just adding another unit of work to that queue and it can be beneficial to latency if you aren't already "fast" so to speak. Framerate and input latency aren't exactly glued to the hip, input is buffered into the games update-cycle and draw-calls usually operate on an entirely different loop. Can read up on this by searching "game update loop vs game draw loop" and more often than not for "good" engines they'll have these running on different threads (which can then spawn more threads, etc.). A popular design for our era of games usually involves batched multithreading, this design usually speeds things up from a processing perspective but we have to wait for vertical sync (or for the GPU to effectively "push" the frame and the monitor to display it). So we queue that work up and process as quickly as we can on the CPU side; there are likely many cases where players are looking at frames that are 1-3 frames behind too or pieces of said frame may be utilizing work cached from a previous frame. There is CPU work being done for a lot of reasons too, not all of it is strictly game logic but just synchronizing data & preparing it to be sent off to the GPU (which isn't always available to be sync'd too). I am not 100% familiar with the DLSS workflow, but if it's using previous frame data it'll almost always mean input delays but that "might" be okay because for a 60 FPS game the input can be sync'd as quickly as 16.33ms~ so if you can boost frames to 120 FPS and it adds +4ms to input you have a new input latency of 12.33~ms (which is an overall net improvement). It's less desirable if said boost isn't sufficient though, say it's 80 FPS instead... then you are looking at 16.5ms which means the game will generally "feel" off. This is already very speculative of how each engine does it's input reads. Inputs are usually evented from the OS, then the game logic will keep a buffer of the most-up-to-date inputs collected from OS events and then compare the previous frame buffer with the newest frame buffer and store that information for the update-loop to read & process. Meaning usually more often than not, 500 FPS is basically "peak" input latency; after that is hit your input hardware usually isn't quick enough to pick up any changes (let alone the OS + Engine), I would guess realistically minimum latency is achieved around 300 FPS with human beings being able to react effectively around ~240 FPS (our lowest reflexive reaction time is like 8ms; in a perfect world this would be about 125 FPS, but because of buffering and such our targets need to be higher). Hope this helps to answer some questions; just a hobby game-dev.

Do you think dlss 4 or beyond will allow vr for better graphic quality games? Like making it possible to run a game with graphics if a new mw2 on vr with physics and stuff for example?

What is that robotic portal shooter that philip is playing around min 1:20?

Timewarp for VR I believe actually comes at a bit of an extra cost. It's used for Wireless VR headsets to mitigate the massive latency wireless introduces for VR. I believe it actually renders at a higher resolution outside of what you set it to. At 1080p, it might render like 1200p, but NOT show you the extra edge space it's rendering. The extra edge space is reserved to pan across when moving your head. Calculated in headset, individually from what's going on in game. Hence the perceived latency reduction. The problem is that this won't reduce all other input. Gunshots and movement will respond slower, and so will jumping, or other interactions. It only compensates for head movement, and in Cyberpunk it'll only compensate for the player camera movement at like an extra 5-10% performance cost for the extra pixels rendered that are out of bounds 90% of the time. You can actually bug out Timewarp my moving your head really fast in an erratic fashion. It'll show black lines on the side of your VR screen where it's panning to but nothing is rendered if you move too fast. This would be difficult to mitigate on a monitor and much more noticeable, unless AI just filled in the gaps.

My first thought regarding DLSS 3 was that it's most likely only relevant in scenarios when native/DLSS 2 (at a reasonable quality level) only gets you around 40-60fps in games played with a controller or where you don't use precise mouse aiming. Mouse aim would get annoying due to the input lag and you don't really need it in general when you already have more than 60fps.

I am actually hyped on how Nvidia wants to top this in the next generations. Last year I upgraded from a 980ti which I used for 6 years to a 3080 to use it for another 5 to 6 years. I can only dream how sick my next upgrades jump will be if they already improved this damn much.

Perhaps this may be incredible useful for Animation or CGI in the future at least!

2:13 can hear crofty yelling THROUGH GOES HAMILTON

Great video

It would be nice to see objective data like a input latency tool attached to the monitor, or a high speed camera to give us some numbers here instead of it based off feel. I trust your judgement, but feel can be off sometimes and Id like to see its actual impact and how its changed with reflex off/on. I feel the same with very high framerates. I'm more concerned with mouse aim feeling snappy and instant as a result of high frames. The game looking smoother in motion is nice, but its really all about that input delay feeling better. Nvidia is on point though with their tech and this is version 1 of this new feature. They are very aware of response times with reflex, I have faith they will improve on this to the same degree DLSS1 was improved on with DLSS2.

perfect video.

Quick note on 2:15. Racing games are in the same spot as CSGO where you need a lot of fps for several reasons. One is obviously input lag and response time. Another is that the force feedback of the wheel needs to get data from the game so low fps will give you worse ffb. In other words, simracing needs way more than 60fps in a competitive field.

This is really something for the future, the feature is exclusive to 4xxx cards, which don't really struggle reaching 60 fps in any title with dlss 2. So it comes down to the choice would you rather have really smooth visuals or a more responsive feel? But only in really hard to run games which there are not many of right now. If AMD brings something similar to the table for all GPU's, then we are talking because we might be able to run games like cyberpunk on a potato pc with 60 fps.

great video.

Great music again

The AI frame generation V DLSS 3 makes me think of camera stabilisation in post. Some new cameras record gyroscopic & accelerometer metadata and use them to help stabilize the video in post, much cleaner than pure software stabilisation relying only on the image. I wonder if DLSS 3 has some kind of motion data as well the image displayed to help generate new frames?

Just got to the 3rd chapter in Plague Tale Requiem and haven't noticed anything weird with DLSS3. It's about 180FPS with some drops to about 140 maxed at 4k.

I have a 6600xt and a 4k tv. Sometimes I hook up my pc to the tv and the 6600xt cant get more than 30-40 fps in 90% of the games I play at 4k high settings and I limit the refresh to 30hz and use the Tv's truemotion feature or whatever it's name is to get the 60fps feeling. It works amazing, yes you can feel the latency, but it's very smooth and now that it's integated directly into the gpu, with actual good tech to take advantage of it I'm pretty hyped to try it out.

This is the best attempt at a fair, real world based review on DLSS 3

Regarding latency, this makes me wonder if games could have an option to enable DLSS3 only in non-latency-critical situations (driving, cutscenes, …) and disable it for shooting segments of a game. Of course, resolution or other graphics settings would have to be turned down automatically to allow for higher framerates during shooting segments, as well as having a fast enough CPU to avoid bottlenecks. I think it's still something worth trying :)

What do you think of Using DLAA and DLSS3 in Plague Tale Requiem . Does is produce a very high quality image ?

My guess with the artifact interpolation error on stuff like menus in flightsim could be due to the way the game is loading the gpu when switching and using menus vs running the game. Could be some kind of load spike or sharp decrease in usage that delays or inhibits the interpolations ability to draw that frame.

"Mouse movement being smoothed" is where I turn back. No amount of frames is worth giving up input latency in my opinion.

What game is the clip with the ponytail girl in armor, at the beginning? Thanks!

Me with a GT 1030: ah yes very helpful

one thing i could think of is uploading to google drive or another file hosting service, that way people with high refresh rate displays could correctly see it. big issue is that it defeats the purpose of youtube and not everyone has a high refresh rate display

I think generating whole frame and then interpolating in-between is not optimal solution. Maybe after first frame you can generate lower resolution frame(like 360p for 4k Image), then use previous frame to apply changes. Then use your 360p image to generate 1080p image and upscale it. In that case I think input penalty should be between 1 to 1 rendering and current dlss3. Also, doesn't dlss 2 already renders gui in full resolution instead of upscaling?

Do you think DLSS3 works for Cyberpunk in CPU limited Scenes where lots of NPCs are on Screen like near Viktor's Clinc?

Couldn't agree more, at first I thought i was missing on with rtx 4000 series but Im not really the person that would like the imput lag difference. I guess I'll buy amd form now on.

I'm playing the new A Plague Tale and with my 4090 already gets a nice high frame rate just using DLSS 2 on ultra settings using 4K. However there are a few times where the framerate will just tank into the 60s which are very noticeable and jolting for me. With DLSS 3 enabled pushing my framerate well into the triple digits, these same, rare, and recreatable instances where framerate tanks, go nowhere near double digits therefore gameplay is uninterrupted and not jolting. So for me the extra latency is acceptable and welcomed at least in this title.

I'm curious why there are artifacts on the HUD which shouldn't be part of the DLSS stream. Surprised the HUD is even part of the optical flow accelerator.

I love your "tech" focused content, and the steam deck example is great and sounds like hacks for better battery life

Whats that tech Demo at 01:20?

05:48 doesnt it work if you upload on 60fps and we speed it up 2x?

a VERY important thing to remember with the DLSS artifacts when you're actually playing is how the human brain processes visual information. your brain fills in the gaps subconsciously, so if something is a little off your brain's basically going to auto-correct it anyway. that is, until you slow down and look at the frame on its own.

Hey philip how are you doing mate? Have you considered making a video on DLSS 3 on Arma 3 (If it's supported? I'm not sure if it is), or just testing the new CPUs with the 4090 in general on Arma 3, since it's always been a game that ran very poorly on the beefiest PCs, it would be interesting to see how the new hardware runs the game!

DLSS 3 seems like something that will allow for 4k 120+ fps gaming in games like A Plague Tale Requiem. At least on a card as insane as the 4090. But it will also allow future games that look even better, and that are even more intensive than Requiem to get solid frame rates.

Is input latency more noticeable on the 4080 vs the 4090?

Fun fact: you can technically upload & play 120FPS video to KZfaq, you just have to convert it to half speed before uploading, then play it back in 2x speed on KZfaq.

Did you speed up your voice in this video by any chance? Maybe you're just really good at speaking fast XD

I ask, would enabling the “ultra” setting on latency on Nvidia help with the input lag?

What I would find interesting is if the Frames feel like the KZfaq videos where there is some noticeable interpolation happening or if its more akin to the higher quality increases of FPS where it looks more natural and not so noticeable to the eye. I can't stand the first method as It always looks so artifical to me.

Finally someone who explains the issues I feared would be pretty important, but everyone kept dismissing. DLSS 3 is great for 4K 120hz gaming but yeah, I think a 4080/4070 will be powerful enough to not need frame generation. Maybe SpiderMan and movie games look better but everything else...

Exactly my thoughts. Dlss3 would make sense for consoles or situations in general where we want the best possible graphics and can't get more than 30 fps. Nvidia should make it work with vsync and target a specific frame rate like vr games do with double buffered vsync.

I think the delay on mouse movements "can" sometimes be even good. Games that are slow paced and want to give the player some handicaps like condemned criminal origins was one game where I felt it was done well. There are many games where this can be somewhat fine (especially single player games), but this weird mouse smoothing is for some odd reason always added in places you would not expect it. Hardware mouse acceleration in windows, OSU!, Starcraft Broodwar, overwatch 2... I can definitely understand why a CS Go player would hate it.

It'd be nice if they made it support some older GPUs my 2080s has been letting me down a little bit lately in some titles.

Using DLSS 3 right now on my 4080 on Plague Tale, Witcher 3 and Portal RTX. With Nvidia Reflex on you really have to force yourself to feel the difference at most times when compared to DLSS 3 off and without Reflex. Yes, Reflex can improve non-DLSS 3 responsiveness even more than native and if compared to that the latency can be ever so slightly more pronounced but TBH it really isn't as big an issue as people are making it out to be and you will feel that if you just start playing a game for a few mins with DLSS 3 and Reflex on and experience it yourself. Also, the crazy boost to frames makes it even less noticeable and worth it. So I did a test with the Nvidia Frame View tool and here are actual numbers: Game: A Plague Tale Innocence @ Ultra + DLAA Res: 1440p Case 1 - No DLSS 3 / No Reflex FPS = 100 to 103 PC Latency = 30 to 33 ms Case 2 - No DLSS 3 / Reflex ON + Boost FPS = 99 to 101 PC Latency = 27 to 30 ms Case 3 - DLSS 3 / Reflex On (can't be changed to Boost for now) FPS = 160 to 163 PC Latency = 37 to 40 ms I tested this out in another area too, max latency difference is the same (at around 10 ms) but the FPS boost is insane (60+ fps). I even tested it without Reflex and without DLSS 3 and saw that sometimes the game has the same latency as it gets with DLSS 3 and Reflex ON so there's no difference if you compare those two cases. Now, I'll be completely honest and say that I personally CAN feel the difference of 10 ms if I concentrate on the mouse movement really hard and keep testing it out with DLSS 3 on and off a few times in succession, but I am so hard pressed to actually feel any real difference during gameplay that it's really irrelevant. I have a 144 Hz screen and I actually find the game so much nicer to play with a higher frame rate than worry about the 10 ms added latency which I can't really feel anyway due to the smoothness of the visuals.