Framerate Isn't Good Enough: Latency Pipeline, "Input Lag," Reflex, & Engineering Interview
ฝัง
- เผยแพร่เมื่อ 9 มิ.ย. 2024
- Sponsor: ID Cooling Frozn A620 Tower Cooler on Amazon geni.us/A0OZYtF
This engineering interview & discussion follows-up our previous industry interviews with people like Tom Petersen of Intel and Bill Alverson of AMD, but now featuring Guillermo Siman of NVIDIA, who joins to discuss the engineering aspects of latency. We've recently been talking about an increase in our focus in testing on latency, adding to our existing FPS benchmarks, and this discussion is to help provide an educational backdrop on what truly comprises end-to-end system latency. We'll focus on the latency pipeline, educational topics such as how the game engine handles and processes input, peripheral latency, and system-level latency (such as from the render queue). These topics also cover various types of bottlenecks.
GamersNexus pays for all of its own travel for on-location coverage. Learn more in our ethics statements and policies here: gamers.nexus/ethics-statement...
Help fund our travel coverage and unique behind-the-scenes discussions! The best way to support our work is through our store: store.gamersnexus.net/ -- grab a Modmat for PC building, a toolkit, a coaster pack, and more!
Find n0thing's channel here (and check back to see our testing with him): www.youtube.com/@n0thing/videos
Find another engineering interview here, featuring Tom Petersen of Intel: • Intel's Major Overhaul...
Find our engineering interview playlist here: • AMD's CPU Analysis Lab...
The best way to support our work is through our store: store.gamersnexus.net/
Like our content? Please consider becoming our Patron to support us: / gamersnexus
TIMESTAMPS
00:00 - Latency Testing & Engineering Interview
02:40 - Latency Pipeline Canonical View
08:55 - Common Misconceptions
11:32 - Types of "Lag" & Bottlenecks Explained
14:50 - Game Engine Input Sampling
20:39 - Impact of GPU Bottlenecks & Reflex
26:07 - Summarizing
** Please like, comment, and subscribe for more! **
Links to Amazon and Newegg are typically monetized on our channel (affiliate links) and may return a commission of sales to us from the retailer. This is unrelated to the product manufacturer. Any advertisements or sponsorships are disclosed within the video ("this video is brought to you by") and above the fold in the description. We do not ever produce paid content or "sponsored content" (meaning that the content is our idea and is not funded externally aside from whatever ad placement is in the beginning) and we do not ever charge manufacturers for coverage.
Follow us in these locations for more gaming and hardware updates:
t: / gamersnexus
f: / gamersnexus
w: www.gamersnexus.net/
Host: Steve Burke
Guest: Guillermo Siman
Camera, Editing: Vitalii Makhnovets, Mike Gaglione - เกม
Awesome engineering discussion with Guillermo. He definitely joins the list of some of the most educational interviews we've hosted. Looking forward to exploring this topic more!
Find another engineering interview here, featuring Tom Petersen of Intel: th-cam.com/video/5hAy5V91Hr4/w-d-xo.html
Or our interview with two engineers from AMD (Bill & Amit) over here: th-cam.com/video/RTA3Ls-WAcw/w-d-xo.html
Find our engineering interview playlist here: th-cam.com/video/hVSSOs9Z-uY/w-d-xo.html
Notice me senpai
Very interesting!
With hard wired don't forget the 'on time' latency of the diode/L.E.D. lol Screen sensor Latency + 'bullet' flight time LOL
If I may make suggestions... Would you guys mind, since you are going to add latency to your tests, demystifying some long held beliefs that we (in the know) know to be incorrect or correct but still see the mainstream opinion not catching up entirely?
A good example, as Guillermo was saying, how DPI is also important for input latency. Of course even if it doubles input latency from 0.8ms to 1.6 it is not like it matters, but it is too often people say I'm "wrong" in playing at a high DPI (from the sensor, with VERY low sensitivity in game or in my OS [pointer speed on windows would be the equivalent]), but we all know it is 'measurably' better, even if undetectable.
Then also the good old polling hz.
Like I said in some other comment, comparing amd anti-lag, nvidia reflex and just a good old dumb frame limiter to right below where you'd be GPU bound, like Battle(non)sense suggests..
IDK, if I were to give some thought instead of commenting on youtube I could think of more, but these are just examples off the top
great insite ty. (i know i cant spwll)
Thanks so much for having me on! Great to meet you and the team-that was loads of fun. Looking forward to Pt. 2 with n0thing!
Thank you for the clear explanation, it was really easy to follow!
Love your passion and dedication towards the topic
thanks for doing this, its always nice to put a face and personality to the tech we use. reflex in particular has been really good for me so far and it was cool to visualize how both the process it sought to improve and it itself works
@@minecraftmike5193I’ve not ever had an issue in any of my games. Might be an implementation issue in the game? Not sure just guessing.
Very informative and well made presentation!
@@minecraftmike5193 because developers who implement it needs to optimized it for their game. I just gonna go out on a limb that the Rachet and Clank devs didn't care enough to optimized Reflex for the game when Reflex is mainly used on Competitive games not single-player games..
One clarification to the answer to Steve's question at around 22:30. The input sampling is a "uniform random" variable with an average time of 5 ms in that example. This is because as Guillermo explained earlier, the input could have arrived anywhere from 0 to 10 ms before the frame, so the sampling causes an average of 5 ms of latency, though any particular frame has a roughly equal probability of being any value from 0 to 10 ms.
Correct-thanks for clarifying Josef!
Super helpful! Thanks for the extra info!
@GamersNexus The best analogy is video camera. As the shutter opens, information starts to accumulate, but at some point shutter closes, and everything that has been collected up to this point in time gets saved as a frame. Then shutter opens again and the cycle repeats. And since a click can occur at any point of that cycle with equal probability, statistical mean value is going to be half of the cycle time.
Shannon theorem
I would like to point out that in case of the cpu load is low enough, you could get away with something like generate the new frame asap, poll continuously for inputs and if you get new inputs generate the new frame and throw away your old frame sitting in the render buffer. This removes the risk of losing frames you'd get by waiting, but will hit your cpu harder.
Battlenonsense being cited in this video warmed my heart.
Great video with great insights!
I miss him! Hopefully he comes back around in the future.
Battle(non)sense is one of the most MASSIVELY UNDERRATED channls to ever exist on TH-cam.
@@SKO713 He's a Battlefield player so hopefully when the next game drops, in 2025 or 2026... We have been in limbo since 2013.. Some might say 2016.
Yeah, that excellent channel not getting the success he deserved and not making any more is part of why I hate yt so darn much
@@griffin1366 Battlefield 1 was a diamond in the rough. It runs so good these days. It's optimised to high heaven. Bigger maps, more players, same FPS as CS2 LOL.
I really enjoy the shoutout to battlenonsense and that they learned from that. Really humble, likeable guy who explains it well.
They hahaha!!!!!!!!!!!!! NVIDIA Learning (NASDAQ) US$ 726,58 -12,42 (-1,68%) just give us good stuff for good price then you sell more !
Thank you for looking at this. Latency is definitely the most underrated metric when measuring system performance right now. I purposefully optimize my graphics settings to get the lowest amount of input lag possible, rather than going for more FPS.
You nailed it - very underrated, and we've been a part of the FPS focus (even with frametimes) and want to expand the scope! A lot of times, the two align and are correlated. But there is definitely a lot more to the story!
Yeah, exactly. It can be a very tricky balancing act with some games, but it's worth it.
Same. Limiting FPS for low latency and consistent frame times almost always leads to a significantly better experience than running the GPU at 100% for peak FPS.
Yeah, take Frame Generation for instance - it's being marketed as a performance boost (which I absolutely hate), because the FPS values are higher (bigger number bigger better), but the latency is in some cases tripled. It should be advertised as motion smoothing technology or something
@TK-11 yeah at least in val at 900 fps uncapped it's saying my game to render latency is about 3ms while capping it to 500fps reports roughly 2ms. Interesting seeing im using reflex which is meant to eliminate the latency overhead u just mentioned.
I’m a consultant in the advanced technology space and have to give technical “talks” for a living - this was great. It’s really hard to explain technical complexity in a way that is accessible; it’s all abstraction of language we are dealing with so things get confusing quickly. This audience is likely much more technical than most, however thats still very cool something this in depth and a bit esoteric has 200k views. Solid work. Looking forward to Pt 2!
i often end up explaining how pcs work to some of my friends and this video has given me a new perspective on how to explain the cpu and gpu in a very simple fassion, the cpu draws everything and the gpu colours it xDDD
@@corylyon6231 cpu writes the recipe. gpu mixes the ingredients as per instructions. display cooks until ready.
The animations showing the render queue in GPU bound and CPU bound situations was really great. It clarified some things that I had always wondered.
Am I getting this right.. Being GPU bottleknecked is really bad? And that u always want to be cpu bottleneck?
Anyone please help😭
So basically I never want to be gpu bound or what? Even if it's like a 4090 + 14900k in that case i'm still gonna be gpu bound right. Or maybe it doesnt matter at high fps say240+ fps?
Damn i had no idea David does tech stuff youtube channel was also a CS Pro
hahaha. Didn't see the resemblance until you said it!
I was going to write the exact same thing
Same I thought it was him too
the second I saw him on screen I went to check the comments if anybody else noticed him, they look so incredibly similar lol
Thats pretty cool. I was still playing consoles when people were playing that game. I the whole csgo generation is a really important chunk out of the overall history of gaming. I always imagine what video games either traditional or VR will be like in a few hundred years if we don't kill the planet with nuclear war and find a way to coexist regardless of borders.
I really like that you do these deep background pieces, they give the required context to understand your also excellent hardware reviews.
I love listening to people who love and care about what they do talk about their work, especially highly technical things being explained in a more accessible way. Great stuff from the both of you, this video was really cool.
Fantastic coverage on this underrated metric. It felt very enjoyable to watch and not at all 'lecture-esque' as you thought it would be! Thanks for the great video and awesome content :D
Latency is not just a gaming thing! It's of utmost importance for professional audio and video recording too, so not only a graphics thing. Imagine recording like 15 microphones to separate tracks simultaneously, with EQ and many other effects on each, and the whole, and slamming it on a drive, as close to real time to be able to monitor it all! Same goes for recording scenes with many cameras, all at once, or even editing live between them.
Please do more on the subject Steve, and also give it more love from a processor/RAM... perspective.
and to circle back, audio latency can also be a huge gaming thing. Certain audio cues are used in place of visual cues in cases which they are faster. For example, it has been studied that the top LG (lightning gun) players in Quake have reaction times that exceed what is possible from visual input. One theory is these players use the audio cue of the hit indicator to calculate when the enemy player changes direction before they actually see it. Human reaction to audio stimuli is also slightly faster than visual stimuli
@@chasmurphy1227 Audio latency should not exist in 2024, that was mostly eradicated when quad cores became mainstream. Even 32 bit 192khz should still run perfectly fine. If your CPU is running at 100% then maybe there's a difference, but firstly you shouldn't be letting your CPU hit 100% as that caused extreme instability on your PC, and secondly most games won't utilize every thread on 16 thread and even some 12 thread CPUs. Audio is extremely important, but I don't see audio latency/lag being an issue still.
@@mttrashcan-bg1ro Sure it is. Wireless/BT peripherals introduce lag.
Latency is definitely a gaming thing.
@@necro4468I clearly wrote: Not JUST a gaming thing, not "Not a gaming thing" at all.
I'm really glad that latency is getting so much focus these days honestly. For a long time i feel like it's not really been talked about much, despite being so critical for the user experience
Fantastic video, the guy from Nvidia was an absolute pleasure to listen to and very professional. I now understand why when I run with reflex on my game runs so much smoother. Look forward to part 2. Thanks Steve and team
very educational video, i've been playing fps games for years but never really put lots of thought into how it all worked. really good to know
The game engine section was great!
@@GamersNexus Awesome video, primarily playing FPS games lately and adding this information to reviews will allow me to purchase the products that will be more attuned to my gaming goals rather then just 'more fps = better'.
@@Reznap7 I game between 60Hz and 85Hz on a CRT monitor (i could push it beyond 85Hz but a CRT is so fast that higher refresh rates than those are kinda pointless, it already creates natural motion blur at 85Hz).
We are on this absurd bubble of Hz and fps for gaming, it's like the loudness wars for music.
Finally, since VGA CRTs are analog, not digital, they don't add lag (you don't need anti-aliasing, AI upscaling and frame gen since CRTs don't have pixels or a fixed native spatial and temporal resolution).
Especially with higher polling rates being more and more common, latency deep dives are super necessary
Doesn't matter how fast you can get data from your hand to the computer; it's still going to sit in a cache until the CPU until it's ready to be processed. This is why polling will always be inferior to interrupt, which tells the computer to "drop everything you're doing and process this data". PS/2 purists aren't just being luddites.
with 1ms or less delay from the polling rate with a decent mouse, the savings seem kinda negligable @@MyNameIsBucket
@@MyNameIsBucket This was correct but modern chipsets put the PS/2 interface through the same caches as polled devices. Not only that, the PS/2 protocol is so slow it takes around a millisecond to transmit a single scancode, so one or multiple milliseconds per pressed key. A 1000Hz USB keyboard refreshes its entire rollover in the time it takes a PS/2 keyboard to signal a single key.
@@mitsync Unless your CPU is very busy completing other tasks like, oh I don't know, trying to render a CPU-bound game at 120Hz. Then the input from that USB keyboard takes quite a bit longer to register in the game. The PS/2 keyboard will still take exactly the same time.
@@MyNameIsBucket You are prioritising input over simulation speed. The game isn't going to do anything with your input until the next tick anyway, and very very few CPU bound games run over 60 tick. 1000hz polling is already well past the point of diminishing returns, you aren't gaining anything by trying to squeeze your inputs in quicker than that.
That was genuinely a very good one! glad to see you shedding light at this latency topic, looking forward to future content like this!
Latency testing would be such a great addition to the testing of hardware. Especially with the introduction of frame generation, but also for CPU overhead, driver overhead, OS overhead and human input devices. We generally mainly know latency from monitor testing. It won't be easy though.
Because your monitor and your internet connection is the main bottleneck.
I replaced my LCD with an old high end VGA CRT Monitor (it can do 1856x1344, pseudo 4:3 1440p) that is basically new (no one used it in a very, very long time) and it looks lightyears better on everything.
Glad that you're starting to look into this. Though this is MUCH larger than just for graphics. I.e. a very good example is storage (nvme/ssd/hdd); memory access; as well as general interrupt handling delays. The biggest item I run into pretty much daily is data subsystem performance (drive I/O basically). This is made worse as basically OEM's and all reviewers seem to be fascinated by 'streaming throughput' to a subsystem when this workload basically is completely non-existent for any real world workload. (anyone who doubts this, load up diskmon and check for yourself, it doesn't exist). Wish you can add similar level of detail to any reviews you do with these other subsystems.
Definitely agreed on storage mattering too! Talked with Wendell about this recently in a video!
100% agree but if u care about storage io latency so much those optane drives have been on flash sale recently and in case it wasn't obvious, they demolish any normal ssd in io latency both in averages and especially consistency.
Right, though for *average* latency you can't measure things by the weakest link in the chain (e.g. the SSD), because there are a bunch of layers of cache in between that prevent you from being bottlenecked by it. SSD -> RAM -> L3 -> L2 -> L1 -> CPU would be the rough chain for CPU work on a modern PC (SSDs can also have RAM, but it doesn't quite fit in with the other components in the chain which go from big to small, slow to fast).
Things get slow if you miss every cache and have to ask the SSD directly, but in a lot of workloads everything can be loaded in advance or consistently streamed in before it's needed, and you never hit that slowest path at a critical moment. In practice there *are* going to be misses, which is one source of frame time spikes, but if things are working correctly these are low probability events (but of course it depends on how much data the workload churns through).
@EmanuelHoogeveen Yeah true but remember to a cpu each miss is super detrimental when it's running at like 0.2 nano seconds per clock while a good ssd has an access latency of 50 microseconds, ie 250,000 times that, so a lot of wasted cpu cycles whenever it is waiting on data from the ssd. That's why hard drives had been such an enormous bottleneck for so long. To a cpu each miss as technically super rare as it is (proportionally i mean, it happens pretty frequently in absolute terms, check resource monitor and look for "page hard faults") is detrimental when they're that fast. Oh yeah and literally almost any time u load something ur almost definitely gonna get tons of misses. That's basically what loading something is, moving data from storage into ram.
Oh and fyi ssds have inherently really bad writes which is why dedicated dram cache on them is literally only used for writes and never reads so for latency it isn't really much help as generally, ur always read bound not write bound.
TLDR: No one's assuming ur cpu is pulling data from the ssd 100% of the time, the point is it it affects ur system latency regardless.
@@FrozokenI didn't realize that SSD RAM is mostly for writes but that makes sense, thanks :) I was trying to figure out where it fits in since it's so small relative to the SSD and even your regular RAM, but if it's used as a buffer more than cache that makes more sense.
This is great content. I love understanding the graphics pipeline. Very clear presentation. Shoot more videos like this, Steve! I enjoyed the TAP VR pipeline presentation years ago. I still go back to it from time to time.
This was a fantastic and very educational video! Thank you for always putting in the work to not just give us information but to teach us how understand it also. This was an awesome video!
this kind of testing is really important, recently i have been trying out frame generation in a bunch of games thanks to Lossless Scaling's implementation, and every single time i have decided against frame gen due to input latency. Frame gen from 85 FPS to 170 FPS feels so much worse than 90-130 real FPS with equivalent settings.
EDIT: Lossless Scaling just updated to not require a frame cap when generating frames, meaning I can now play at an unlocked 90-130 FPS with frame gen. After 5 minutes of getting a feel for this, I think it is AMAZING! Maybe I'll be noticing the input latency after trying this for longer but for now this is definitely how I'm playing my games.
FSR 3 in beta on Starfield has done this adding a load of input lag compared to DLSS in the previous patch, so you are 100% correct.
My Samsung CRT: "What is that?".
It really depends on the game though, and its implementation. I've had frame generation probably add 10-15ms input latency (you can do a test that shows how sensitive or accurate you are when it comes to telling how much input latency you're getting and FG felt like 10-20 in some games I've tested it with). But with other games, it easily adds 30-50ms. For context, I have a 4080 super
My goodness, this was an amazing compilation and summary around everything to do with input latency and render latency. Glad you are expounding on this topic more since FPS numbers tell so little about how the game feels to play. Thanks for doing this!
great explanation. thanks for putting the time in to do this
This is hands down my favorite video you've ever posted! Thank you!
Tech Yes City did a fantastic piece on this as well, his finding was latency peaked with intel 10th gen
Latency used to be something often tested. And then it suddenly went away. I remember a common one was the test with a mouse click and led to when the gun muzzle flash. Or whatever was supposed to be triggered. And there was more and more focused on frame. To the point we are now counting fake frames. How is that different to a time when we had games making 30 frames but displaying 60 by duplicating them. And the test was usually done for displays reviews only.
Man I loved Guillermo. Not just the all the info but how well he presented and explained it.
Also how he kept moving in place. XD I'm always amazed how host like Steve can manage to stay still for so long. It was nice see someone like me that can stay still for 3 seconds.
LCD display added absurd amounts of lag compared to crt. Maybe it was display companies being shady.
Frame generation tech has to be the low point of modern GPUs and gaming. They can't get real performance, so they're literally faking it. Lame.
8 people dont know how silicone works lol yeah its magic yall@@paradoxicalcat7173
@@Touma134 of corse... and is all about money
This is great content. Thanks Steve and Guillermo :D
Really enjoyed this detailed lecture/breakdown of Latency! Would love to see more vids like this keep coming. Thanks Steve!
SUPER useful piece, GN! I've admittedly downplayed response times in my choices of display thinking it wasn't really going to matter to me. This gives me a much clearer picture of what's actually going on and will allow me to make better decisions in the future. Thanks!
Thank you steve.
Just by you doing this, the industry and gaming is going to get a whole lot better.
Really excited to see you guys are going to add latency to your testing. This is awesome news and something that hasn't gotten much attention elsewhere.
This was a great video, and an excellent talk/conversation! Thank you for this
Great video! This is the level of knowledge dump I usually have to go to a conference to get.
This was such an amazing piece of information. Thanks for this video team
Thank you for this interview and the breakdown of this topic.
Wow, this is extremely informative, and still digestible. Kudos, and I can’t wait for part 2!
Fascinating. You guys are doing great work, and this is super informative! Keep it up.
I love this. Thanks for making a technical subject more accessable.
This is really good, thank you for the quality and in depth analyses
Loved this! This kind of in-depth explanation of complete system latency is Amazing! I thoroughly enjoyed this video... and have enjoyed all of your in depth & complex dives into how the tech is actually functioning! I'm Yearning for more like it! :)
Awesome video and so excited for what's to come!
Amazing stuff! I love that you picked Counter-Strike as an example and I'm looking forward to part 2. After playing CS2 the whole evening with Reflex off, it might be the time to finally give it another shot!
I love how battlenonsense get quoted here. Guys a goat
Great video! really nice with this level of discussion/depth into a topic
Finally had time to watch this. Great stuff! Looking forward to Pt2
This feels like I'm in a lecture and I should be taking notes!
Really interesting video; he's clearly very dedicated to what he does. I think more gamers should watch stuff like this, get a better understanding of what's going on closer to the hardware level and gain some appreciation to everyone making this stuff possible.
Wanna copy my notes? I expect quiz at the end of pt2.
amazing video, answered so many of my questions that I've had for years. thanks team GN & NVidia!
Amazing video guys, thank you!!
This is really helpful and interesting stuff. This vid helps tremendously in understanding what really happens when we're running into performance limitations. Thanks for this!
Great video - as always. Keep up the incredible nerd work. This stuff is far more interesting than it should be.
feel like your video will remind me to always keep reflex on in my video games. thanks
im so glad vids like this are starting to made. Maybe one day you guys can try to tackle the old "floaty mouse" / input lag/possible/sluggishness/visually framing issue/ emi/ situation that a lot of gamers are experienceing (even with high end pc's) and stopping us from playing at a high level and develop muscle memory , making it a very difficult problem to pinpoint to this day plaguing a lot of gamers , the others think were crazy because it is such a small minority compaired to the world but you cant overlook all the thousands of threads about it
The professionalism and quality of this channel are rocketing high sky, congrats guys, and thanks for all the info.
It would be great to have a similar piece with AMD to understand how Reflex and Antilag differ. Great job GN! 👏
As long as that one brother and sister work there, you will keep laughing hahahaha
This was really informative. Can't wait for this to become a standard addition in tests.
Incredibly informative video! Thank you for taking the time and putting effort of creating this video, breaking down the PC latency in video games.
This educational deeper dive into the he why and how is invaluable to consumers.
Most of us care about the entire experience of gaming not just fps.
Looking forward to part 2!
Wow, this is some video. Really high on the educational value. Kudos!
Not up to frametimes, I think it is much more important!
Thank you!
you're doing us a favour with this video. i hope this blows up
Amazing work on this video. Thank you!!!!!!!!!
Guillermo is quite clearly very knowledgeable and also an excellent teacher. Props for an excellent discussion from Steve too!
Wow this was eyeopening. Thanks! Awesome.
I felt like there was going to be a quiz at the end. That's how detailed this was. Great job everyone.
I’d have flunked it.
I respect your engineering and testing methodology. No one else takes the time to look at it with this attention to detail and consistency. In addition, you take the time to explain it so I know why the numbers matter and how you derived them. Spewing out a ton of data can quickly get boring and become meaningless, but you manage to keep the detail while making it relevant and understandable. That's not easy.
Really interesting video that explains it very well. Can't wait for part two!
This is literally gonna be the next step in hardware reviews. Hardware has become so good only unoptimized AAA titles and I guess casual games with good graphics need more FPS, but a ton of people who play competitively already get more than enough FPS. What really matters is whether the frame you see is even the one you're supposed to see and if the input you made gets processed fast enough that it's accurate. There's a lot of aspects to it and FPS can only do so much in that regard. I hope other tech reviewers start looking into it as well, it looks hella interesting.
Nothing beats CRT PC gaming, absolutely nothing.
For this to work it'd require measuring latency in complex states/environments. Just firing a gun without anything else is informational but it could be rather misleading. It's difficult to be the "next step" as it'd require to be somewhat standardized/repeatable as well.
This is awesome. As a sim racer I am was always wondering how to get the lowest latency and how it all works.
Great educational video! Love these!
These are the type of videos that are the best. Thank you.
Great video explaining reflex. As I watched I was thinking why not hold back the CPU and then yes - that’s exactly the solution.
This was VERY interesting and quite enlightening. It was also explained in a way that i think even people without much theoretical knowledge can understand .
This is fascinating! Great coverage, thank you
Really good topic guys Thank you!
Omg I have been doing and learning all I can to improve latency in windows and beyond. This topic is so interesting and important
Cool to see some of the visuals from Battle(non)sense in the presentation!
This was a dang good video! Also helped me understand what reflex is actually doing! Hope more game studios incorporate it into their games.
thanks for the depth you went through with this
I’m so glad you guys did this. The fighting game community appreciates this
Love this kind of content.
Super intresting topic. Cant wait to watch more on this on the next parts. Conclusions from this will be interesting too, especially on cs2!
Great job explaining all of this! I hope the tools to do this are low cost enough for most gear reviewers to pick up and use.
Mentioning Battle(non)sense was so nice to see! Love the channel and I actually hope he can monetize his content better. It's a real shame he can't do more of his stuff!
As long as he is healthy and happy, that is much more important than money and power!
This is the content I love and trust from GN. Very well delivered!
Absolutely amazing content. There aren't many channels like this one. ❤
This is what I've been saying for 10 years now. I never understood why no one ever cared about input lag. It is SO important.
thank you very very much!
Edit! PLEASE CHECK motherboard DPC Latency with LatencyMon!
I absolutely love this. Seeing numbers on charts can help get to the idea of what's doing what in your system, but having an engineer break down exactly how the pieces work together, and what their tech is doing to optimize it, that I love. One of the best videos I've seen in awhile.
Great idea for a video. Thank you!
Awesome job, learned so much, thank you! Like I said in the comments of a previous video, "input lag is more important than FPS, frame time, frame spacing, etc." is the hill I'm ready to die on.
I love this educational video how it's work/how it's made :D
Been waiting on a video like this! If anyone is interested in knowing more about polling (specifically on old consoles), there is a video called "You will never see a Bomb Torizo skip in a World Record Super Metroid speedrun (NTSC)" which talks about issues emerging at polling rates around 60Hz. It's very focused on Super Metroid, but I found it very interesting.
Finally!!!
I'm really looking forward to this journey. I'd love to also consider adding some Linux tests now and then, since Nvidia Reflex with latency markers will be added soon to Proton.
This is freaking amazing, thanks Steve.
I really love this video :)
Further proof that frames are king. I don't want RT to half my framerate only to "double" it with framegen - clogging up the pipeline even more.
Cap my frames so I can have smooth delivery of frames without having a gpu busy render queue.
Very cool info about how Reflex works (or is supposed to work). Thanks GN 👍
Great piece, GN. KEEP IT COMING!