Thursday, February 29th 2024

AMD FSR 3.0 Extends to "The Last of Us Part 1," "Remnant II," and "RoboCop: Rogue City"

AMD announced three new entries to the growing list of games that support FSR 3.0, "The Last of Us Part 1," "Remnant II," and "RoboCop: Rogue City." The three will soon get patches from their developers that add FSR 3 support. "The Last of Us Part 1" is a particularly important title in the list. FSR 3 entails updates to the upscaling algorithm that provide more image quality at a given preset compared to FSR 2, but more importantly, it introduces frame-generation, with an interpolation technology that nearly doubles framerates. FSR 3 support will be available to those with Radeon RX 6000 series and RX 7000 series GPUs.
Add your own comment

18 Comments on AMD FSR 3.0 Extends to "The Last of Us Part 1," "Remnant II," and "RoboCop: Rogue City"

#1
robb
Last of Us will get FSR but has never fixed the DLSS and DLAA issues? DLSS can look very strange in areas the flashlight makes it worse. DLAA causes TONS of obvious ghosting so why in the hell was this never fixed? The game also still has quite a few other graphics issues that were never fixed as my last playthrough was long after the last patch.
Posted on Reply
#2
Keivz
robbLast of Us will get FSR but has never fixed the DLSS and DLAA issues? DLSS can look very strange in areas the flashlight makes it worse. DLAA causes TONS of obvious ghosting so why in the hell was this never fixed? The game also still has quite a few other graphics issues that were never fixed as my last playthrough was long after the last patch.
AMD sponsored.
Posted on Reply
#3
Ware
Seems like it's broken in Robocop. Frame gen does increase FPS and slightly lower GPU usage, but it looks worse - like lower FPS.
100 FPS with no FG looks smoother than 165 FPS with FG. The old FSR2FSR3 mod looks way better.
FSR3 really helped Starship Troopers, but for me the implementation in this title is broken.
Posted on Reply
#4
Vya Domus
Ware100 FPS with no FG looks smoother than 165 FPS with FG.
I am not sure you understand how this works.

165 FPS with FG means a base frame rate of 84, of course 100 FPS with no FG feels better because it's objectively more responsive.
Posted on Reply
#5
Chane
Nice. I'll have to play through these games again since I picked up a 7900 XT.
Posted on Reply
#6
Ware
Vya DomusI am not sure you understand how this works.
I'm not talking about responsiveness - I'm talking about smoothness.
Have you tried the new Robocop patch #04?
I'm comparing the behavior of native FSR3 fame gen implementations in 2 games I own and can can test with my own eyes.
I'm also comparing the results with the FSR2FSR3 mod in the same game.
Vya Domus165 FPS with FG means a base frame rate of 84, of course 100 FPS with no FG feels better because it's objectively more responsive.
I am not sure you understand how this works.
"The latency induced from enabling both AMD FSR 3 upscaling and frame generation is typically less than the native rendering experience without AMD FSR 3 enabled."

FG on should at least look smoother - that's the whole point. In my case despite the higher FPS reported by the drivers as well as my monitor, it looks worse(like lower FPS).
Posted on Reply
#7
Not4ce
WareI'm not talking about responsiveness - I'm talking about smoothness.
Have you tried the new Robocop patch #04?
I'm comparing the behavior of native FSR3 fame gen implementations in 2 games I own and can can test with my own eyes.
I'm also comparing the results with the FSR2FSR3 mod in the same game.

I am not sure you understand how this works.
"The latency induced from enabling both AMD FSR 3 upscaling and frame generation is typically less than the native rendering experience without AMD FSR 3 enabled."

FG on should at least look smoother - that's the whole point. In my case despite the higher FPS reported by the drivers as well as my monitor, it looks worse(like lower FPS).
Well, I only have robocop and I tried FSR3 on my 6800xt, and it does indeed become choppier. Its adding judder on the generated frames from what I can see, leading to the choppier experience/feeling like its rendering at 40-50 frames

Starfield on my end had the same issue on the beta FSR3 update from 3 weeks back, I needed to wait for the latest steam update and disable afterburner for the judder to go away. So im guessing they need to fix the motion judder in robocop as well, but yea, you are correct and 5/7 FSR3 implementations have been a very bad experience for me. Some of Puredarks mods have provided a better experience than these official implementations which is somewhat baffling (Forspoken, Aveum, Avatar)
Posted on Reply
#8
Vya Domus
Ware"The latency induced from enabling both AMD FSR 3 upscaling and frame generation is typically less than the native rendering experience without AMD FSR 3 enabled."

FG on should at least look smoother - that's the whole point. In my case despite the higher FPS reported by the drivers as well as my monitor, it looks worse(like lower FPS).
A game running at 100FPS will have lower response time than a game running at 165FPS with FG. FG is going to look smoother if you compare it to the same base frame rate, if you compare it to a the game running at a higher base frame rate then it's not guaranteed at all that it will look smoother.

If a game can run natively at above half of the refresh rate of the monitor it does not make sense to use FG, it's not not going to look or feel smoother in a definitive manner.
Posted on Reply
#9
Keivz
Vya DomusA game running at 100FPS will have lower response time than a game running at 165FPS with FG. FG is going to look smoother if you compare it to the same base frame rate, if you compare it to a the game running at a higher base frame rate then it's not guaranteed at all that it will look smoother.

If a game can run natively at above half of the refresh rate of the monitor it does not make sense to use FG, it's not not going to look or feel smoother in a definitive manner.
You are mostly wrong. It sounds almost like you haven’t used frame gen.

How is 165 fps (frame gen, max monitor frame rate) not going to look smoother than 100 fps (native)? Sure it will be slightly less responsive because of the lower base frame rate (82-83 fps), but it will indeed look smoother.

Smoothness is determined by the frames per second (and the display’s pixel response time… and the frame pacing… but all else being equal, just the frame rate). Besides that, the motion clarity will be quite a bit higher as well with the frame gen boosted framerate. So while it may feel slightly worse with frame gen on (due to slightly higher input lag), it will still look smoother and clearer in motion, even with a lower base frame rate than a non frame gen boosted display output.
Posted on Reply
#10
Vya Domus
KeivzHow is 165 fps (frame gen, max monitor frame rate) not going to look smoother than 100 fps (native)
Because the game is running at 84 FPS instead of 100, I explained it as clear as I could. FG is not a replacement for additional performance, stuttering feels worse with FG as well because there is a mismatch between the moment a game stutters and what you see on screen.
KeivzIt sounds almost like you haven’t used frame gen.
I did, that's how I know a lower base frame rate with interpolated frames wont necessarily feel smoother than a higher native base frame rate, everyone who tried these scenarios can confirm this.
Posted on Reply
#11
Keivz
Vya DomusA lower base frame rate with interpolated frames wont necessarily feel smoother than a higher native base frame rate, everyone who tried these scenarios can confirm this.
You are sadly conflating terms. You don’t feel smoothness. You feel responsiveness. They are not the same. Smoothness is something you see. And like I said, a game will look smoother the higher the framerate. Fake frames or not.

As a more extreme example, imagine a game running at a 40 native fps. Now compare that to a game running frame gen to 75 fps. The frame gen output will look far more smooth, but will feel slightly less responsive.
Posted on Reply
#12
Vya Domus
KeivzYou don’t feel smoothness. You feel responsiveness.
A game running at 120FPS with FG will feel smoother than a game running at 60FPS natively, however it will not feel more responsive.

Of course smoothness is something you can feel not just see, a game can run at 120FPS vs 60FPS but if it has stutters it will not feel as smooth despite the higher frame rate. Or if the input lag is too big it wont feel smoother as well.
Posted on Reply
#13
remekra
Robocop doesnt feel smooth with FG simply because VRR does not work. It's the same implemenation as in Immortals and that other game.
Only Avatar for me works with VRR. If we are talking about official implementations. Because LukeFZ mod works flawlessly with VRR. On W3, Cyberpunk, even on Robocop.
I don't know where do they get these devs from.
Posted on Reply
#14
Vya Domus
remekraI don't know where do they get these devs from.
It's not the devs it's the way games are developed, features get implemented then immediately sent to testing without really checking anything, QA is unlikely to pick up on things like these as they are very specific.
Posted on Reply
#15
remekra
Vya DomusIt's not the devs it's the way games are developed, features get implemented then immediately sent to testing without really checking anything, QA is unlikely to pick up on things like these as they are very specific.
Checking if VRR works it's like the easiest thing to check. More likely it was found out but who cares. It's UE5 game so they just used plugin and probably didn't even test it. Just slap that on and that's it. Can't say for last of us as I don't have it.

But also the same is in Starfield. Maybe on steam release it works, but game pass version VRR does not work for me.
Posted on Reply
#16
Vya Domus
remekraChecking if VRR works it's like the easiest thing to check. More likely it was found out but who cares.
I worked in the industry, trust me no one is checking this unless specifically instructed to do so. QA mostly focuses on game functionality anyway, most of these things simply do not get tested.
Posted on Reply
#17
Aerpoweron
Not4ceWell, I only have robocop and I tried FSR3 on my 6800xt, and it does indeed become choppier. Its adding judder on the generated frames from what I can see, leading to the choppier experience/feeling like its rendering at 40-50 frames

Starfield on my end had the same issue on the beta FSR3 update from 3 weeks back, I needed to wait for the latest steam update and disable afterburner for the judder to go away. So im guessing they need to fix the motion judder in robocop as well, but yea, you are correct and 5/7 FSR3 implementations have been a very bad experience for me. Some of Puredarks mods have provided a better experience than these official implementations which is somewhat baffling (Forspoken, Aveum, Avatar)
I currently play Robocop, Remnant 2 and The Talos Principle 2 on my Vega 64. FSR 3 really helps to make the games playable. Even Frame Generation works. But with FG on, it still feels like without, but it looks smoother. I didn't really notice any motion judder, my frame rate may be too low for that.
Always check to set up your sharpening correctly. For cyberpunk i use 75%, but for Remnant 2 i use 50%
Posted on Reply
#18
remekra
Well after last update Avatar joins the club of games that FSR3 FG does not work properly. It's a juddery mess now. Thought that it's something on my side, but found post on reddit and yeah it's not me only.
Posted on Reply
Add your own comment
May 9th, 2024 03:34 EDT change timezone

New Forum Posts

Popular Reviews

Controversial News Posts