Associate
My understanding is that DLSS 3 will essentially interpolate between 2 ‘properly’ calculated frames and add in and display between them some interpolated frames … there by displaying more fps overall .. great idea.
But, in order to do that, it needs to calculate the later frame its going towards, then figure out the in between interpolated frames, display them, then finally display the calculated later frame. That will surely add latency into the display compared to simply displaying the later frame when it was originally calculated.
Admittedly, at high fps, its not much time between frames, but looking at the demo on the presentation, the original source was ~25fps (40ms/frame) boosted to 100+fps when you play at that wraps rate, there is a lot of inherit latency, and to wait for that latter frame to be reached via interpolated frames between is going to add more still surely, as in another 40ms ? So the display latency could be 80ms overall even though your seeing 100fps.
Or have I understood it all wrong?
But, in order to do that, it needs to calculate the later frame its going towards, then figure out the in between interpolated frames, display them, then finally display the calculated later frame. That will surely add latency into the display compared to simply displaying the later frame when it was originally calculated.
Admittedly, at high fps, its not much time between frames, but looking at the demo on the presentation, the original source was ~25fps (40ms/frame) boosted to 100+fps when you play at that wraps rate, there is a lot of inherit latency, and to wait for that latter frame to be reached via interpolated frames between is going to add more still surely, as in another 40ms ? So the display latency could be 80ms overall even though your seeing 100fps.
Or have I understood it all wrong?