D
Deleted member 86764
Guest
"It doesn't need the next frame to interpolate, the interpolation algorithm data is entirely generative based largely on the last frame data."
If software doesn't need a full set of rendered frames and can generate the data from the last interpolated frame, then the frequency should always be 60fps. As the software would make up for whatever rendered frame deficit there is. It certainly wouldn't be some random odd number.
"It's probably just better to look at frame rate as a function of the time it takes to produce a new frame, ie, 16.6ms is 60fps and 16.9ms is 59fps. for instance. So it just missed it's update window by 0.03ms after the frame interpolation. To lose 2 frames you need to be at 17.2ms."
But then we'd have a torn frame and we don't have that here.
"So basically there was a standard 33.33ms update with a frame injected inbetween to make it appear like a 16.66ms update. If PS4Pro misses a bit say 33.6ms from the previous update to the next it will appear at 59fps. To lose 2 frames, the next update would have been at 33.9ms. 0.6ms slower than the standard 33.33ms update."
That would surely lead to screen tearing, which we're not getting.
Sorry for the crap quoting, I'm on my phone while the baby sleeps nearby.
If software doesn't need a full set of rendered frames and can generate the data from the last interpolated frame, then the frequency should always be 60fps. As the software would make up for whatever rendered frame deficit there is. It certainly wouldn't be some random odd number.
"It's probably just better to look at frame rate as a function of the time it takes to produce a new frame, ie, 16.6ms is 60fps and 16.9ms is 59fps. for instance. So it just missed it's update window by 0.03ms after the frame interpolation. To lose 2 frames you need to be at 17.2ms."
But then we'd have a torn frame and we don't have that here.
"So basically there was a standard 33.33ms update with a frame injected inbetween to make it appear like a 16.66ms update. If PS4Pro misses a bit say 33.6ms from the previous update to the next it will appear at 59fps. To lose 2 frames, the next update would have been at 33.9ms. 0.6ms slower than the standard 33.33ms update."
That would surely lead to screen tearing, which we're not getting.
Sorry for the crap quoting, I'm on my phone while the baby sleeps nearby.