IntentionalPun
Ask me about my wife's perfect butthole
This dude has no clue WTF he is talking about.
This dude has no clue WTF he is talking about.
That's not how this works. That's not how any of this works.
What he said is exactly what Matt said over at Era. I'd trust Matt more than these other 'insiders' since Matt got all the stuff about PS4 x XBO right (wayyy before launch)I simply don't get this way of thinking. The XsX can run at its max clocks all the time. On a leveled playing field Variable clocks can't match fixed max clocks.
Actually a good few things he said are correct. And as someone said above also what matt said over at the other place.That's not how this works. That's not how any of this works.
Link to Matt's post? I might have seen it already but I can't remember lolWhat he said is exactly what Matt said over at Era. I'd trust Matt more than these other 'insiders' since Matt got all the stuff about PS4 x XBO right (wayyy before launch)
But isn't this video just the June 11th trailer? What's the significance?
It's not that video that just what happens when you link the channel, the thing of importance is there is a private video on the channel that got listed today.But isn't this video just the June 11th trailer? What's the significance?
I simply don't get this way of thinking. The XsX can run at its max clocks all the time. On a leveled playing field Variable clocks can't match fixed max clocks.
But isn't this video just the June 11th trailer? What's the significance?
What he said is exactly what Matt said over at Era. I'd trust Matt more than these other 'insiders' since Matt got all the stuff about PS4 x XBO right (wayyy before launch)
Sorry, I don't have it, someone posted a print on this very thread.Link to Matt's post? I might have seen it already but I can't remember lol
Honestly looks ugly asf
That is not how it works either - it will down clock when the power draw exceeds the budget which it easily can - but then in an uncontrolled way.
Edit: This whole discussion is filled with quite some ignorance. With making both power and frequency variables the system can avoid bottle-necks more often. It is really that simple - and yes, it is a clear benefit to be able to control both as on the PS5. Only upside - no downside.
I ask you this question: Do you think that Cerny would still say that TF and CU counts don't tell the whole story if the XSX had less TFs and CUs than the PS5?
He wouldn't. There's no way in hell that Cerny would downplay the importance of CUs and TFs if they were one more bullet point that the PS5 could one-up the XSX with. So I think it's safe to say that on the CU/TF subject, he was damage controlling.
Don't get me wrong, I think the PS5 will blow the XSX out of the water, but him handwaving TFs and CUs as a true measure of power was damage control.
Link?What he said is exactly what Matt said over at Era. I'd trust Matt more than these other 'insiders' since Matt got all the stuff about PS4 x XBO right (wayyy before launch)
He tries, but he physically can't suck Microsoft's dick any harder without descending to timdog (or what's his name) levelsI don't need to zoom 800% to clearly see through his BS.
That is not how it works either - it will down clock when the power draw exceeds the budget which it easily can - but then in an uncontrolled way.
Edit: This whole discussion is filled with quite some ignorance. With making both power and frequency variables the system can avoid bottle-necks more often. It is really that simple - and yes, it is a clear benefit to be able to control both as on the PS5. Only upside - no downside.
The XSX has thermal boundaries whereas the PS5 power boundaries. Different workloads will cause different problems for both consoles. There will be tasks which cause XSX to generate unneeded noise and excessive heat because it's running a task at max power that wont need max power because of it's fixed clocks. Ps5 is designed to avoid that it gives power to what the tasks need.Let's say that the CPU is under heavy load due to AVX usage. As far as I know the XsX CPU will handle the load and the PS5 would have to underclock to stay under the power budget. No?
But... the XSS clocks are fixed, higher than the max clocks of the PS5
Honestly looks ugly asf
The XSXs CPU clocks are a little higher I believe. But in terms of GPU the PS5s is clocked quite a bit higher.
Not saying the PS5 has more TFs but the GPUs frequency is higher.
Yeah read the last sentence in my post.
Titus says some accurate things, but it's also clear he doesn't get a few things.
Are people really still confused by this stuff?
Thanks.. I was wondering the same and thinking I must be the only one missing something... LOL.
Good news is supposedly on PS5 you can load your saved game right from the system OS.GEDAFUCK ATTA HERE!
Seriously though, I'm talking about turning the power on the PS5, wait the system to boot, run Spider-Man/Witcher 3/AAA title, load a saved game, wait for the game world to load and play.
For most of those games, the procedure takes like, 3-5 minutes.
Heck, the X1X needs about a minute to boot.
He said so in the last tweet. CPU/GPU are stronger on XSX. It's more of a design limitation on workloads or something like it (hence why this is used in laptops). It won't make PS5 stronger, just more efficient, since it doesn't have a 500W PSU to power it.Link?
Maybe he's badly paraphrasing things that are correct.. but what he said is absolutely not correct.
You can't magically not lower performance when lowering clocks.. like who would ever make that claim?
You can get higher average performance than the same design at fixed clocks though. But... the XSS clocks are fixed, higher than the max clocks of the PS5... so when comparing them, the XSS has the clear advantage at least overall theoretical TF.
PS5 has advantage for maximum clock speed per CU on the GPU side though.
What part exactly do you think he was wrong about? I read his tweets and looks pretty much in line with my understanding. Maybe I missed something.Yeah read the last sentence in my post.
Titus says some accurate things, but it's also clear he doesn't get a few things.
Are people really still confused by this stuff?
Kingthrash
![]()
Halo Infinite vs. Killzone Shadow Fall [Graphics Comparison]
Warning: too much swearing. Great work from @Kingthrash . DF should take notes, assuming they are honest to begin with.www.neogaf.com
lol.. I meant X, sorry.. fuck that branding.I didn't see that last part sorry. And when you said XSS I thought you meant the Series S for a moment.
The entire point of making clocks variable is because that same chip/setup/power budget/etc. could NOT handle max clocks at all times. He makes the statement that it isn't why they exist, but that isn't true at all. It's literally the reason you make clocks variable, to push beyond what would be possible by picking a static number. That was flat out wrong, and his stuff about bottlenecks is just sort of overly confusing too.What part exactly do you think he was wrong about? I read his tweets and looks pretty much in line with my understanding. Maybe I missed something.
Swearing level at 10000 ....lol mabad![]()
Let's say that the CPU is under heavy load due to AVX usage. As far as I know the XsX CPU will handle the load and the PS5 would have tounderclock to stay under the power budget. No?
This has been discussed before... no it isn't.lol.. I meant X, sorry.. fuck that branding.
What Tidus gets wrong: The variable clocks are ABSOLUTELY because it couldn't maintain full clock speed for both at all times.
WTF are you talking about?When that happens on the XSX it means that you will have uncontrolled down clocks on the silicon that tapped out (CPU or the GPU).
How is possible after of months of this discussion you still confusing clock with utilization, you canlol.. I meant X, sorry.. fuck that branding.
What Tidus gets wrong: The variable clocks are ABSOLUTELY because it couldn't maintain full clock speed for both at all times. Like the rest of his post contradicts that entire claim.. ti's THE reason to have variable clocks in any setup, in the Sony setup it's about power budget.. others do it by measuring heat. (which really are related pretty closely)
The rest I guess is accurate.. but that statement really throws the whole thing off, and he's just over-confusing it with the bottlneck talk and acting like variable clocks are some magic fix for bottlnecks.
They just let a processor go beyond what it could do "at all times" otherwise.
If you mean tweet no 3 I think you misread him.lol.. I meant X, sorry.. fuck that branding.
What Tidus gets wrong: The variable clocks are ABSOLUTELY because it couldn't maintain full clock speed for both at all times. Like the rest of his post contradicts that entire claim.. ti's THE reason to have variable clocks in any setup, in the Sony setup it's about power budget.. others do it by measuring heat. (which really are related pretty closely)
The rest I guess is accurate.. but that statement really throws the whole thing off, and he's just over-confusing it with the bottlneck talk and acting like variable clocks are some magic fix for bottlnecks.
They just let a processor go beyond what it could do "at all times" otherwise.
Yes it is.This has been discussed before... no it isn't.
Actually, he is quite right on the PS5This dude has no clue WTF he is talking about.
Why you people always ignore what the lead architect explained about boost clocks? How YOU THINK it works, it's not HOW IT WORKS. What Tidux wrote e completely right.The entire point of making clocks variable is because that same chip/setup/power budget/etc. could NOT handle max clocks at all times. He makes the statement that it isn't why they exist, but that isn't true at all. It's literally the reason you make clocks variable, to push beyond what would be possible by picking a static number.
You can't magically not lower performance when lowering clocks.. like who would ever make that claim?
How is possible after of months of this discussion you still confusing clock with utilization, you can
have two CPUs with exactly the same specs running to the same clock but have a very different
consume of power because the operations which are running are different and the use is different
in each of those CPUs.
I know is hard to believe Tidux is good in something even I cannot believe and is making me
rethink what is actually is truth and what is not (in the life in general).![]()
Yes it is.
Why wouldn't Sony max the clocks at all times if it was possible within their power budget/not cause thermal issues?
Because CPU/GPU don't get 100% usage all the time. Simple as that. When CPU is at 80% and GPU at 100%, more performance goes to the GPU, less to the CPU and vice-versa, it's pretty simple.Yes it is.
Why wouldn't Sony max the clocks at all times if it was possible within their power budget/not cause thermal issues?
The entire point of making clocks variable is because that same chip/setup/power budget/etc. could NOT handle max clocks at all times. He makes the statement that it isn't why they exist, but that isn't true at all. It's literally the reason you make clocks variable, to push beyond what would be possible by picking a static number. That was flat out wrong, and his stuff about bottlenecks is just sort of overly confusing too.
Fixed clocks: Pick a static number that you believe all code can achieve without causing power/heat issues.
Variable clocks: Let the clocks go higher than they could "at all times" because there are specific times when that is feasible without causing issues.
Typical method: React to thermals, give more power to the processor if the thermals are good, lower it when it heats up.
Sony method: Do this based on workload, basically PREDICTING ahead of time that a piece of code would be likely to cause thermal issues and do it within a specific power budget (another way to avoid thermal issues.)
If the CPU is using the power that isn't needed in a specific frame and you redistribute that power to The GPU, exactly how you lose performance?, you basically taking all the performance you can get and putting it where is needed multiple times per frame.
You are not letting the CPU or the GPU waste resources that they don't need at a specific moment.