AMD gives an update on FSR 3, the follow-up to FSR 2 that triples the fidelity of the frame rates in PC games like Forspoken and Immortals of Aveum.FSR 3 com...

TL;DW:

  • FSR 3 is frame generation, similar to DLSS 3. It can greatly increase FPS to 2-3x.

  • FSR 3 can run on any GPU, including consoles. They made a point about how it would be dumb to limit it to only the newest generation of cards.

  • Every DX11 & DX12 game can take advantage of this tech via HYPR-RX, which is AMD’s software for boosting frames and decreasing latency.

  • Games will start using it by early fall, public launch will be by Q1 2024

It’s left to be seen how good or noticeable FSR3 will be, but if it actually runs well I think we can expect tons of games (especially on console) to make use of it.

  • echo64@lemmy.worldEnglish
    24·
    1 year ago

    Yeah, it does, which is something tv tech has to try and derive themselves. Tv tech has to figure that stuff out. It’s actually less complicated in a fun kind of way. But please do continue to explain how it’s more compute heavy

    Also just to be very clear, tv tech also encompasses motion vectors into the interpolation, that’s the whole point. It just has to compute them with frame comparisons. Games have that information encoded into various gbuffers so it’s already available.

      • echo64@lemmy.worldEnglish
        11·
        1 year ago

        No. Tvs do not quite literally blend two frames. They use the same techniques as video codecs to extract rudimentary motion vectors by comparing frames, then do motion interpolation with them.

        Please, if you want to talk about this, we can talk about this, but you have to understand that you are wrong here. The Samsung TV I had a decade ago did this, it’s been a standard for a very long time.

        Again, tvs do not "literally blend two frames ** and if they did, they wouldn’t have the input lag problems they do with this feature as they need a few frames of derived motion vectors to make anything look good

        They do not need to know what is foreground or background, they don’t need to know what’s a ui element or not, they need to know what pixels moved between two frames and generate intermediate frames that moves those pixels along the estimated vector.

        Modern engines have this information available, it’s used for a few things, modern engines can provide this. A tv has to estimate it.

          • echo64@lemmy.worldEnglish
            11·
            1 year ago

            Rolling my eyes so hard at this entire thread.

            You: doing this on shader units is bad! Not possible! Uses too much compute!

            Me: this tech has existed for over a decade on tvs, and there is motion interpolation software that you can get today that will do the same thing tvs do on compute and it works fine on even bad cards

            You: tvs just blend frames. This is different it uses motion vectors!

            Me: tvs use motion vectors. They compute them, whereas if you hook it up via amds thing, you don’t need to compute them

            You: No, this is different because if you hook it up via amds thing, you don’t need to compute them, and it can look better

            <— We are here.

            You’ve absolutely lost your thread on what you are mad about, you’re now agreeing with me but you want to fixate on this this as a marker of how it’s not the same thing as tvs, even though it’s the same thing as tvs without the motion estimation exactly like I have been saying this entire time, but you’re desperate to find some way that no, I was right and win! Even though you’ve lost what thread you originally were talking about.

            Maybe we need to reframe this. How is this not possible or a bad idea to do on shader units? That’s what you were mad about. How is this totally different from tv tech but also the same and less compute heavy as tv tech bad to run on shader units?