The Last of Us Part I

New patches for The Last of Us Part I & Robocop: Rogue City improve AMD FSR 3.0 Frame Generation

Naughty Dog and Teyon have released new patches for The Last of Us Part I and Robocop: Rogue City that improve their support for AMD FSR 3.0 Frame Generation. So, thanks to these updates, both of these two games can now be enjoyed with AMD FSR 3.0 FG.

Now I haven’t tested these patches but according to reports from other users, these updates do exactly what they claim. By using the latest version of AMD FSR 3.0 FG, these two games can now feel smooth.

For those unaware, The Last of Us Part I and Robocop: Rogue City originally used an old version of FSR 3.0. That version had framepacing/”frame delivery” issues, similar to those we reported in Forspoken and Immortals of Aveum.

Thanks to the latest version of AMD FSR 3.0, though, these games can feel smooth on VRR monitors. Not only that but you no longer have the exact framerate of your monitor’s refresh rate to get smooth framerates. That’s great news as PC gamers can now enable it to get better performance.

Now what I find ironic here is that Naughty Dog has not bothered adding support for NVIDIA DLSS 3. The team went into the trouble of fixing AMD FSR 3.0. So, I don’t really know why it has not added support for DLSS 3. It should be easy as the game already supports AMD FSR 3.0 FG. Yes, there is a DLSS 3 Frame Generation Mod you can use, but that’s a paid mod.

Before closing, I should note that these patches only fix the issues with AMD FSR 3.0’s Frame Generation. They do not improve the quality of its Super Resolution upscaler. AMD FSR 3.1 will be able to offer improvements to it, so it will be interesting to see whether the devs will, once again, update their games to add support for the latest version of FSR.

Stay tuned for more!

FSR3 Frame Generation JUST GOT FIXED!! The Last of Us, Avatar, Robocop & More!

13 thoughts on “New patches for The Last of Us Part I & Robocop: Rogue City improve AMD FSR 3.0 Frame Generation”

  1. John, please test The last of Us FSR 3, if that is working smooth now then the game should be much playable for many users now.

    1. I tested game is smooth but it have lots of artifacts even more than mod and it’s have higher latency than fsr3 mod , so doesn’t worth it at all but give it a try it won’t hurt

    1. Not FSR 3.0, but according to AMD using the frame-gen part of the upcoming FSR 3.1 should be possible with DLSS.

  2. The Last of Us Part 1 is one of the worst ports ever to land on PC. I have no idea how woke Iron Galaxy is but I sure hell do know that looking at the sky definitely won’t require utilizing CPUs at 30~35% across all the cores and threads!!!

    1. Its even worse after insomniac leak and shows how incompetent they are because Spider-Man 2 PC port fixed and run almost as good as its ps5 counterpart just few month after that leak by fans

      1. I’m not disagreeing about the port quality but you can’t use a game running on a completely different engine as your point of comparison just because both were PlayStation exclusive lol.

        The handle the entire rendering pipeline and their game logic completely different from each other.

        The first step in avoiding incompetence is a basic understanding how things works in the first place and without that knowledge you really shouldn’t be speaking out on how incompetent a dev team or in this case the differences in performance of a console games performance on pc compared to a different game… Not only that but insomniacs engine had dx12 support already and naughty dogs only supported Sony very different very bespoke PlayStation API. Spiderman was also developed knowing it would be ported to window and last of us was absolutely not made with that knowledge.

        The last part alone means there was a fundamentally different method of design and development used between both games.

        Sigh..

        1. True, but an amateur ragtag of fans able to fix probably alpha stage of leaked port (meant they have no resource and contact towards the original engine devs) just shows that Iron Galaxy, paid and fully resourceful devs , is blatantly ignorance towards their own quality of work

  3. Adding DLSS FG is not an easy to do quick task. Also when you mod to use “DLSS FG” you’re really using FSR FG whether it’s an nVidia GPU or not.

    DLSS FG requires the optical flow hardware which the 3xxx series has but it’s not as good as the 4xxx series. This hardware receives direct data from the game engine in the form of motion vectors. It uses that information to more accurately predict where something is moving in the scene then it compares the differences in pixel data with quick image analysis on previous vs current rendered frames to keep potential errors as low as possible.

    FSR FG doesn’t do the first part so when it’s enabled like when you mod “DLSS” into a game to use on a 3000 series or older cards the game isn’t sending motion vectors. FG is just receiving the frames, making the analysis and a best guess on pixel movement then interpolating a frame.

    You can’t just hit a button or write a couple lines of code for the motion vector data, it needs to be part of the way the rendering pipeline is setup which means adding it then testing the game so it really doesn’t make sense to a dev to add that to an old game especially if you can just use a mod to get a still good version of frame gen.

    Just to add some more information.. when you use a mod to add “DLSS FG” and use it on a what you are actually doing is using a hack that tricks the engine into thinking the GPU is part of the 4000 series so it enables DLSS FG. The engine is sending the motion vectors into a black hole and the frame gen is really FSR FG. Vice versa when you mod DLSS FG into a game that only supports FSR you are just using FSR. Everyone seems to really like FSR lol and at this point significantly more people use its FG than use nVidia’s and that probably won’t change until about 4 years from now and people upgrade over time.

Leave a Reply

Your email address will not be published. Required fields are marked *