FSR 3 Is Coming to Console, Potentially Unlocking Performance Levels, Though PS5 May Have a Problem

Immortals of Aveum dev Ascendant Studios confirmed it is working to port AMD FSR 3 to consoles. The PS5 may have a problem with it, though.

[Marcus Fenix]

Im sure Sony will develop it’s own solution for FSR3 to work well and devs can plug that in their game engines.

[Babadook7]

It’s a good bet. It’s tough to know if frame generation would work well enough on either console though. It’s not great on PC yet.

[Eonjay]

No. This article is irrelevant because it says nothing of the PS5 graphics API. They are not privy to it and neither are we.

[Eonjay]

In addition just yesterday Dogital Foundry did a technical review of No Man's Sky running on the Nintendo Switch using a custom version of FSR 2. There isn't just 1 version of FSR that all platforms use. I doubt WCCtech is privy to capabilities of the PS5 GRAPHIC API.

[Einhander1972]

FSR 1 xbox fanboys said it wouldn't be on PS5, then the first game to use it was on PS5
FSR 2 xbox fanboys said it wouldn't be on PS5, then the first game to use it was on PS5
FSR 3 xbox fanboys said it wouldn't be on PS5, I'm sure the first game will be on PS5

And either way PS5 has it's own upscaller with it's hardware based checkerboarding that as far as I am concerned looks and preforms way better than any implementation of FSR. No game with FSR has yet to perform or look better than Sony inhouse games using checkerboard.

[ThichQuangDuck]

"A technical caveat might be an extra obstacle to AMD FSR 3 implementation on PlayStation 5. FSR 3 uses a DX12-based replacement swapchain that handles the Optical Flow and Frame Generation workloads asynchronously. As explained in this GPU Open blog post, the Unreal Engine 5 plugin does offer an alternative option for non-Windows platforms, but it does not work asynchronously and will, therefore, offer inferior performance.

With the Unreal Engine 5 plugin, there are more options to provide a starting point for supporting non-Windows platforms and that control frame pacing. The AMD FSR 3 UE5 plugin contains two backend types: RHI and Native DirectX 12.

The RHI backend is platform agnostic and should work effectively in most circumstances. However, it does not support asynchronous execution of the AMD FSR 3 compute workloads, so these jobs are serialized, with an associated performance cost. Additionally, frame pacing is handled by Unreal’s underlying presentation framework. The ideal use for AMD FSR 3 using the RHI backend is when VSync is enabled on a high-refresh 120+ Hz monitor.

The Native DX12 backend fully supports asynchronous workloads and full frame pacing, so it can have higher performance in certain circumstances. "

in this case its not a xbox fanboy at all though its wccftech saying the possible technological limitations. What actually happens who knows but this isn't even going to apply to all games. This is immortals of avevum one UE5 engine game and games ares still barely UE5

[ThichQuangDuck]

@mrcatastropheAF

I have accepted its just like that here. Can literally quote the article posted and come at it completely clear . Yet they still will disagree. Its wild to see on a game many of them won't even play though

[blackblades]

@Mr
If you using the word pony/bot you definitely a mindless fanboy.

[fr0sty]

That isn't a hardware restriction, it's an API restriction, they did not code support in for asynchronous use on non-directX systems. The developer would have to do it themselves.

[yeahokwhatever]

what it is, is a whole lot of words for "hmmm I'm not sure. sony will know"

[VariantAEC]

Meanwhile from AMD: "A future new member of the AMD FidelityFX SDK
All our AMD FidelityFX technologies are included in the new AMD FidelityFX SDK we released in June, so we’re really excited that we will soon be adding FSR 3 to the FidelityFX SDK, alongside our existing FSR 1 and FSR 2 upscaling solutions.

In case you missed this news, the FidelityFX SDK makes it easier for you to integrate all our FidelityFX technologies (shaders and runtime code) into your DirectX®12 or Vulkan® applications without the hassle of complicated porting procedures."

So, you won't need DirectX to use FSR3 when FSR3 is added to the FidelityFX SDK, which could've already happened at this point. PS5's API is not Vulkan, but it's very similar. Basically this article is kind of right, but not really. So, as many have stated in the comments here already, FSR3 might come to PS5 before Xbox Series consoles like FSR and FSR2 did.

[darthv72]

Are you able to sight examples of these situations? I dont recall any such dialog but surely you can back up these statements.

Not disagreeing... just asking for clarity. Thanks in advance.

[Einhander1972]

No, I will never do what you ask unless it's what I want to do.

But I will mockingly post this link to xbox fanboys circling around themselves trying to convince each other that PS5 couldn't do ML and wasn't even RDNA 2.

https://www.purexbox.com/fo...

[Einhander1972]

Let me clarify my previous comment, it was xbox fanboys claims that the reason PS5 wasn't going to have FSR was because it wasn't RDNA 2 and didn't have ML.

PS5 does have FSR proving them wrong on 3 counts at once.

[Tacoboto]

@darth there are no legitimate examples - AMD themselves made it extremely clear as many devices as possible would be compatible with FSR, both 1 and 2.

I mean, part of the announcement was it even being run on Nvidia GTX cards...

[Zeref]

I think you're confusing FSR2 with RDNA2.
PS5 is not full RDNA2. Many tech channels have talked about it and explained it. It's a sort of hybrid.

[IRetrouk]

Why are xbox fans still trying to claim this, its a customised rdna 2 card, micros is more off the shelf lol.. there is no rdna 1.5 there is no hybrid ffs🤦‍♂️

[Einhander1972]

Thanks for proving my point to Darth, you're a bro!

[Zeref]

@IRetrouk

Why are Playstation fans in denial?

It's a known fact.

[IRetrouk]

No, it's fanboy bs, no facts involved.
The known facts are simple, sony looked at what amd were working on, went "hmmm, that rdna 2 stuff looks good, let's work together to make the chip better for us and what we want it to do"
Ms did the same thing, but to a lesser extent, thats all there is to it, the fact you still tryna cling to a made up claim is kinda sad, whats wrong? Starfield not do it for ya?

[XiNatsuDragnel]

Sony is going to develop their FSR solution.

[XBManiac]

They don't need, it is already available.

[Father__Merrin]

Ah ps5 technology limitation compared to the 12TF series X lmao fsr3 will be on ps5 and it's likely to be first console to get it.

Those 25% of xbox series users that are X owners really are sticking to the ps5 sux mantra

[Aloymetal]

Exactly!

[Sonic1881]

Maybe that's the reason for a PS5 Pro 🤔

[fr0sty]

It isn't a hardware limitation preventing it, so no that is not true. It is a limitation to the API that controls it, it was coded with directX in mind, and an API has not been created that allows for equal performance. Has nothing to do with the GPU or the power of the system, just the code that runs it.

[XBManiac]

FSR3 works on PS5, but with a different solution to DirectX 12 like on Xbox Series. It is a lower performance solution, but it can be improved. It is in the Sony/AMD side. Anyway... Unreal Engine 5 has its own version of temporary up-scaling, so, where is the problem?

[Fishy Fingers]

I read the article and it told me exactly where the (potential) problem is, with the Optical Flow and frame generation, not the upscaling.

[Eonjay]

The article is comparing two different APIs while trying to infer something about a third API with zero information or insight into how FSR 3 will be implemented into it.

[yeahokwhatever]

the article is a meaningless waste of bits.

[TQQ]

All too convientient.

I guess after Microsoft tried to make it seem like FSR 1 and 2 wouldn't be on PlayStation by using their "partnership" with AMD to keep PlayStation off the listed platforms. Now they are trying to make it seem like PlayStation will have a lesser version since the first approach didn't work.

And who is their go to for misinformation wccfltech of course the leading site after DF for PlayStation misinformation.

[porkChop]

Did you even read the article? FSR 3 uses DX12. The PS5 doesn't support DX12. Unreal Engine has a built-in solution for non-DX12 platforms but it isn't asynchronous and has worse performance.

But sure, blame big bad Microsoft for something that has nothing to do with them.

[TQQ]

Obviously PlayStation does not use DX12, that doesn't mean they can't use a similar function within their own API to complete the task.

What I didn't read in this article is any analyses of the PlayStation API all I read is them saying it can't be done.

I remember when wccfltech took super low resolution images of the PS5 chip to declare that PS5 didn't have a 3'rd cache (gamecache) before any real analysis could be done. Later when higher resolution images were made public people noticed that PS5 likely did have the cache.

They have been at the front of the misinformation about PS5, always trying to make it seem like it doesn't have this or it will be less than xbox over and over since before the consoles even launched.

[porkChop]

"that doesn't mean they can't use a similar function within their own API to complete the task."

It doesn't really work that way. Not natively the way you're probably thinking. You basically have to create a plugin or translator to make code work with a different API. That increases processing time per task and can bring limitations which is exactly what's happening here. Epic has already included a separate backend to use with other APIs, but because it isn't DX12 you lose the asynchronous aspect of FSR 3 and you'll end up with worse performance. The performance can be improved but it won't ever be entirely 1:1 with its DX12 counterpart.

"I remember when wccfltech took super low resolution images of the PS5 chip to declare that PS5 didn't have a 3'rd cache (gamecache) before any real analysis could be done. Later when higher resolution images were made public people noticed that PS5 likely did have the cache."

That's not quite accurate. The debate was about whether it had Infinity Cache. It does not. It has a unified L3 cache. It doesn't really matter though because it hasn't stopped the PS5 from powering incredible games anyway.

[TQQ]

You're describing trying to shoehorn the DX implementation onto the PS5 which is not what I am saying, I am saying the PS5 API will use it's own functionality to replace what DX is doing.

You are correct I mistook game cache which is for AMD CPU's with Infinity Cache for their GPU, but that is semantics over the name.

The cache isn't called "infinity cache" because that's an AMD trademark but the cache is fundamentally and functionally the same thing. And wccfltech was incorrect in saying it wasn't there.

Yes the PS5 has fantastic looking games and part of the reason for this maybe in part due to having the "infinity cache" that xbox does not have.

[mkis007]

It's all just 1's and 0's, I'm sure there are people who can implement it knowing it's all software. Correct me if I'm wrong, is the asynchronous aspect hardware based? If it is not then by definition it is platform agnostic. Assuming of course it isn't patented to DirectX. So it is literally just a matter of implementation, which if this is important enough, sony xdev will do.

And tbh it looks like you need to be running at 60fps before this is implemented...not very likely

[yeahokwhatever]

APIs arent hardware. just shhhhhhhhhhhhhhhhhh

[Petebloodyonion]

When there's a will there's a way :)
I'm sure they will find a clever way to make it work :)

[yeahokwhatever]

the only problem sony is going to have is keeping up with demand. fake ass news.

[DarXyde]

The absence of DirectX 12 can certainly be seen as a limitation, but I guess I don't really see the big deal here. In either case, if you're using FSR3, it's not native resolution. Good. We need to move away from that and free up hardware resources to commit to better frame rates.

Superior, inferior, equivalent. I really don't care. I didn't care when Xbox was putting out 720p to PS2's 480i. I didn't care about PS3 supporting HDMI in all models and X360 being able to upscale component cables to 1080p. I didn't care about PS4 outputting 1080p when Xbox One was doing 720p. I didn't care when that dynamic flipped either with Xbox One X and PS4 Pro.

I certainly don't care now and these are talking points for the terminally online community. Make it run well and "nice enough" to look at and you're fine.

[DeadlyFire]

Nah it will work fine.

[derek]

There are no advantages to be found on the xbox platform, this fact should be clear to everyone by now. You would think FSR3 blah blah blah was developed by AMD exclusively to work with dx12 which we don't even need a technical background to know that isn't the case. Stop this desperate search for upcoming advantages for the xbox platform that we all know will never materialize.

[boing1]

May means they are assuming. Worthless.

[z2g]

Also gonna be a prob when last gen gets completely dropped and full rdna2 is the minimum.

Ps5 already had a hint of this on the dead space remake. It had to run VRS in software (x and pc ran it hardware) cuz ps5 doesn’t have the full api suite of rdna 2 and VRS is one of those. It caused the textures to be all janky and they had to remove it altogether.

I’m not saying the ps5 can’t hang, but these are very real things that will show up on games actually built for next gen from the ground up - which we are finally starting to see more of.

[Binarycode]

I'll give my 2 cents.

Bullsht.

Nobody knows Until AMD or Sony come out and say this is what we are doing with PS5 in this regard.

As for games being 30fps. That's a choice.

[Babadook7]

“FSR 3 Is Coming to Console, Potentially Unlocking Performance Levels, Though XSX May Have a Problem”

This is another title they could have made. We just don’t know.

[jznrpg]

XSX has a serious problem. Hardly anyone is buying them.