I mean for 3rd party. Obviously first party will be golden.Based on the DF analysis of Demons Souls that was posted today, if that's gonna be considered unstable....lol.
I mean for 3rd party. Obviously first party will be golden.Based on the DF analysis of Demons Souls that was posted today, if that's gonna be considered unstable....lol.
this was already clarified that its just in old dev kits. Retail and newer dev kits don't have this ."Several developers speaking to Digital Foundry have stated that their current PS5 work sees them throttling back the CPU in order to ensure a sustained 2.23GHz clock on the graphics core."
this was already clarified that its just in old dev kits. Retail and newer dev kits don't have this .
You got a link?this was already clarified that its just in old dev kits. Retail and newer dev kits don't have this .
U r mixing up 2 things . Old dev kits,devs had to choose clock profile . Newer devs kits its not the case . Both the gpu and cpu can run at max (while at max) till an activity arrives that pushes the power draw above the allowable limit (like opening map in horizon zero dawn) in that case the gpu or cpu will down clock by 2% to reduce the power draw by 10%. So gpu and cpu will not always run at max. So the sentenceCan you please share the link for that? I saw the entine Cerny presentation and he clearly also said that the CPU and GPU can't sustain the max clock all the time.
"Mark Cerny freely admits that CPU and GPU won't always be running at 3.5GHz and 2.23GHz respectively."
U r mixing up 2 things . Old dev kits,devs had to choose clock profile . Newer devs kits its not the case . Both can run at max Until gpu and cpu while at max an activity arrives that pushes the power draw above the allowable limit (like opening map in horizon zero dawn) in that case the gpu or cpu will down clock by 2% to reduce the power draw by 10%. So gpu and cpu will not always run at max. So the sentence
"Mark Cerny freely admits that CPU and GPU won't always be running at 3.5GHz and 2.23GHz respectively."
is 100% correct . There are activities that causes one to he down clocked by 2%.
Your other point was clarified that it isnnit the case anymore
"Several developers speaking to Digital Foundry have stated that their current PS5 work sees them throttling back the CPU in order to ensure a sustained 2.23GHz clock on the graphics core."
Gpu or cpu at current state dev kit or retail units have no input from devs. Its done automatically.
Can you please share the link for that? I saw the entine Cerny presentation and he clearly also said that the CPU and GPU can't sustain the max clock all the time.
"Mark Cerny freely admits that CPU and GPU won't always be running at 3.5GHz and 2.23GHz respectively."
Yes that sentence is correct. Gpu and cpu can both run at max till Some instruction causes the activity in gpu or cpu to increase power draw suddenly (like opening map for example) .in this case a down clock in cpu or gpu by couple of % will happen to reduce the power draw by 10% .Let me see if I understand. You are correcting what I said by also saying that the CPU/GPU don't sustain the max clock at all times?
"Mark Cerny freely admits that CPU and GPU won't always be running at 3.5GHz and 2.23GHz respectively."
Same article y'all are discussing, the YouTube video. Start at the 5:25 mark.
I've come to learn its best to watch the video too for DF articles. Because sometimes things are left out the article.
The profiles are in the dev kits, for retail the variable clocks handle that.
That is the whole point of "variable".Let me see if I understand. You are correcting what I said by also saying that the CPU/GPU don't sustain the max clock at all times?
"Mark Cerny freely admits that CPU and GPU won't always be running at 3.5GHz and 2.23GHz respectively."
Yes that sentence is correct. Gpu and cpu can both run at max till Some instruction causes the activity in gpu or cpu to increase power draw suddenly (like opening map for example) .in this case a down clock in cpu or gpu by couple of % will happen to reduce the power draw by 10% .
So they won't always be running at max 100% of times.
The other sentence was not correct where devs had to choose .thats automatic now.
Tbf you seem to have changed the context of the argument. The question was about devs current PS5 workload and scaling back CPU to ensure max GPU workload. Don't think anyone is debating the fact that permanent maxed clocks isn't a thing but Cerny did state that fixed profiles is for devs to use during profiling and won't be part of any released title. Easy cross convo situation.Let me see if I understand. You are correcting what I said by also saying that the CPU/GPU don't sustain the max clock at all times?
"Mark Cerny freely admits that CPU and GPU won't always be running at 3.5GHz and 2.23GHz respectively."
?Yeah, nothing to see here. This video also makes clear that the PS5 cannot sustain CPU and GPU clock at max all the time.
U posted :
Thank you.Tbf you seem to have changed the context of the argument. The question was about devs current PS5 workload and scaling back CPU to ensure max GPU workload. Don't think anyone is debating the fact that permanent maxed clocks isn't a thing but Cerny did state that fixed profiles is for devs to use during profiling and won't be part of any released title. Easy cross convo situation.
Thanks . Exactly. He is confusing 2 things togetherTbf you seem to have changed the context of the argument. The question was about devs current PS5 workload and scaling back CPU to ensure max GPU workload. Don't think anyone is debating the fact that permanent maxed clocks isn't a thing but Cerny did state that fixed profiles is for devs to use during profiling and won't be part of any released title. Easy cross convo situation.
Tbf you seem to have changed the context of the argument. The question was about devs current PS5 workload and scaling back CPU to ensure max GPU workload. Don't think anyone is debating the fact that permanent maxed clocks isn't a thing but Cerny did state that fixed profiles is for devs to use during profiling and won't be part of any released title. Easy cross convo situation.
U posted :
"Several developers speaking to Digital Foundry have stated that their current PS5 work sees them throttling back the CPU in order to ensure a sustained 2.23GHz clock on the graphics core."
this sentence means devs had to choose to lower cpu to make sure gpu runs at max. This input doesn't exist anymore. It was the case in old dev kits .
Expectation on XSX is 4k/60fps, 1440p/120fps or 8k/30fps as minimum.
?
You asked where the profile, dev kit vs retail thing came from.
I provided the source....
Nothing to see about what you asked for?
My bets:
XSX = 4k native
PS5 = sub-4K resolutions/CB/dynamic resolution
Games will otherwise look 95% identical and probably perform very similarly.
Expectation on XSX is 4k/60fps, 1440p/120fps or 8k/30fps as minimum.
Yea the option doesn't exist anymore. Now it runs at max clock when needed till an activity arrives that raises power draw (at same clock) in this case automatically frequency drop happens and will go back up as soon as this activity is passed. Devs don't choose any profile for gpu or cpu anymore.This is not what I said. I didn't say anything about developers having to choose anything.
2- Developers have the option to lock down the PS5 CPU at a lower clock speed and this way they can guarantee that the GPU will stay at the max 2.23GHz clock speed.
Yea the option doesn't exist anymore. Now it runs at max clock when needed till an activity arrives that raises power draw (at same clock) in this case automatically frequency drop happens and will go back up as soon as this activity is passed. Devs don't choose any profile for gpu or cpu anymore.
Resolution is easy to tell the difference.Xbox will generally have higher resolution in games with dynamic res and nobody will notice without magnifying glass.
Xbox will generally have higher resolution in games with dynamic res and nobody will notice without magnifying glass.
The point is of needed PS5 can run at max frequency all the time but this rarely happens. So I'm overall scheme of things it won't effect CPU sides of things or fpaThank you for the correction on that. Although that was not my main point here.
Yes and I clearly said "We already know that the PS5 can't sustain the CPU and GPU at max clock all the time." both are clearly compatible. I included word by word the quotes from Cerny and the developers that spoke with digital foundry. With what you don't agree exactly?
"Mark Cerny freely admits that CPU and GPU won't always be running at 3.5GHz and 2.23GHz respectively."
"Several developers speaking to Digital Foundry have stated that their current PS5 work sees them throttling back the CPU in order to ensure a sustained 2.23GHz clock on the graphics core."
there is no reason for any game to always need max clocks. Thats the point of why they set this up. There are times where jobs are already done on the CPU or GPU and the clock can go down in those cases or when there is come kind of code that is causing issues like the map screens on Horizon that makes the PS4 Pro Scream. The System will operate at max clocks when its needed and the clocks can literally change Frame to frame based on the activity of the GPU or CPU thats all that means. its a more efficient way to use clock frequency that just trying to keep sustaining clocks no matter what.Yeah, nothing to see here. This video also makes clear that the PS5 cannot sustain CPU and GPU clock at max all the time.
lmao.Expectation on XSX is 4k/60fps, 1440p/120fps or 8k/30fps as minimum.
In certain cases, yes it is.
Look at post #253 I'm pretty sure that's where some discussions were conflated. It seems everyone agrees with each other but in separate quote threads. Chill.
it never ends. I just need launch so we can finally show people the performance differences 3rd party are slim to none lol.In certain cases, yes it is.
Will those cases be common? We shall see...
I'm just amazed that after everything we've seen for PS5 examples..old talking points are still being debated.
there is no reason for any game to always need max clocks. Thats the point of why they set this up. There are times where jobs are already done on the CPU or GPU and the clock can go down in those cases or when there is come kind of code that is causing issues like the map screens on Horizon that makes the PS4 Pro Scream. The System will operate at max clocks when its needed and the clocks can literally change Frame to frame based on the activity of the GPU or CPU thats all that means. its a more efficient way to use clock frequency that just trying to keep sustaining clocks no matter what.
Please give me an example of this happening where you have 100% GPU and 100% CPU Utilization in a game over a extended period of time. Other than a single frame or a few frames. If not you literally are arguing something that literally never happens and is a Worst case scenario for literally any system and also means the game is poorly optimized. Also the xbox will also have issues in this case as well. it literally will cause extra power draw on the system.The point here is what happens to the clock speeds when both the CPU and GPU are running tasks that consume a lot of power. The PS5 has a locked power budget and if either the CPU or the GPU go over budget, the clock speed will go down. The XSX on the contrary has a locked CPU and GPU speed, that is always available to the developers under all cases. Someone was comparing the PS5 and XSX CPU speeds and I made the observation that the CPU clock on the PS5 can go below the one on the XSX.
I was just thinking today on my hour-and-a-half drive home "I can't wait for DF's videos on Cyberpunk, even before the next-gen patches hit."