this post was submitted on 14 Aug 2024
19 points (91.3% liked)
PC Gaming
8515 readers
652 users here now
For PC gaming news and discussion. PCGamingWiki
Rules:
- Be Respectful.
- No Spam or Porn.
- No Advertising.
- No Memes.
- No Tech Support.
- No questions about buying/building computers.
- No game suggestions, friend requests, surveys, or begging.
- No Let's Plays, streams, highlight reels/montages, random videos or shorts.
- No off-topic posts/comments.
- Use the original source, no clickbait titles, no duplicates. (Submissions should be from the original source if possible, unless from paywalled or non-english sources. If the title is clickbait or lacks context you may lightly edit the title.)
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Frame generation can only guess the next frame based on previous ones and motion vectors so when you do something it can’t predict (press a button) it still has to draw that normally. As I understand it because of this the input latency is going to be the same as if frame generation is off it will just look smoother.
That's the thing, though; it doesn't look smoother either. There's this hard to explain jitter in the motion that I'm only used to seeing in games running 30fps or lower.
This is a pretty early look at the tech but what they saw was that input latency actually increases with frame gen turned on so maybe that’s wheat you’re seeing? They also noted that at a 60fps target the generated frames were much more noticeable, so maybe that’s what you’re seeing?