Nope, hardware design doesn't particularly care what your language of choice is. Be it C++, Ruby, Lua etc. etc. the instructions that drive the circuitry, and the trade-offs made for efficiency (of note in the console space) are not the domain of programming. It's a single SIMD instruction to fully use all CU's on a gpu, be it 32, 48, or 64+. Your design determines how fast you execute those instructions. Point in case; There is a reason AMD dedicated so much die space for their RDNA2 silicon to an extra cache level.
You get speed up based on how much you can make your tools - in this case your programming tools - work within the limits of the design.
As a crude example: If i took a single pixel, and wanted to test it's colour i'd at minimum require three passes (i have an incredibly badly designed system). With each pass the RGB values are read into registers, then held in some buffer. It makes no difference to the programmer how this process is called, and/or achieved. Because (and this is how you actually do it) you can just pack each 8-bit RGB value into a single 32-bit register, and read them off in a single pass. Easy 3-4x perf increase for this badly designed system when reading pixel data. This is all abstracted away. How you expose the circuitry to the 'programmer' is another thing entirely.
You get speed up based on how much you can make your tools - in this case your programming tools - work within the limits of the design.
As a crude example: If i took a single pixel, and wanted to test it's colour i'd at minimum require three passes (i have an incredibly badly designed system). With each pass the RGB values are read into registers, then held in some buffer. It makes no difference to the programmer how this process is called, and/or achieved. Because (and this is how you actually do it) you can just pack each 8-bit RGB value into a single 32-bit register, and read them off in a single pass. Easy 3-4x perf increase for this badly designed system when reading pixel data. This is all abstracted away. How you expose the circuitry to the 'programmer' is another thing entirely.
Likes:
arfi-gorgona-O
The "unstable: Ps5 framerate can be resolved by re downloading the (patched) game again,because its a bug!!Why should i mention a bug...The reality is,series x resolution scales down more that ps5 in order to maintain 60 fps.
Last edited:
Likes:
Two4DaMoney
You still don't get it. Sony fans expect the SX to show a difference. The SX is stronger. Strong enough that they should be able to brute force beyond the ps5 according to you lol. Each time these various games are close or performing better on the PS5, that's a loss for the SX. The gap is supposed to be clear. The expectations were set high all because of MS's power talk and their stupid fanboys bragging pre-launch of these consoles. Even with these cross-gen games there should be a gap with how you carried on. Even in cases where the SX does outperform the PS5, you make the worlds biggest mountain out of a tiny ant hill(your COD:CW thread).
Remember that this isn't the fault of Sony fans so don't direct your anger this way. You guys stood in front of the fan. It just so happens that some
hit it too. Multiple times.
Last edited:
Likes:
arfi-gorgona-O
Lots of weird bugs lately lol.
Do you have a source for that? So if you download and patch the game again, the Ps5 version runs stable at 60? Never seen that before.
You're still tied to your tools, right? Which is what I'm talking about. So, for what I understand, almost no developers code directly to the steel anymore. Hence, as MS upgrades their tools and devs get familiar with it, they will be able to get the most out of the hardware.
Not sure why you felt in the need to go so deep in the explanation. Not that I complain though.
Do you have a source for that? So if you download and patch the game again, the Ps5 version runs stable at 60? Never seen that before.
You're still tied to your tools, right? Which is what I'm talking about. So, for what I understand, almost no developers code directly to the steel anymore. Hence, as MS upgrades their tools and devs get familiar with it, they will be able to get the most out of the hardware.
Not sure why you felt in the need to go so deep in the explanation. Not that I complain though.
Last edited:
I have seen it yesterday on tweeter,after the latest patch almost everyone complained that Ps5 drops frames in places that it wasn't before.I cant remember who was the guy that found that solution tho...I remember him saying there is something wrong with the patch installer.So in order for this to work you need to re download the already patched game.
I think the solution was in the discussion when John said this.This is sadly only a pic someone got, not the link of the discussion.I would ask him but for now the guy locked his account,and no one can answer or talk to him except the one he mentions lol
I think the solution was in the discussion when John said this.This is sadly only a pic someone got, not the link of the discussion.I would ask him but for now the guy locked his account,and no one can answer or talk to him except the one he mentions lol
Last edited:
When it comes to performance, of course it does whether it's on an API level or not. Said otherwise, if it was linear, differences would show up from day 1.
Uhmm... you probably got confused. Yes I'm aware some people recommend not to patch it. Anyway, it will probably take a while to have this game decently optimized.
Uhmm... you probably got confused. Yes I'm aware some people recommend not to patch it. Anyway, it will probably take a while to have this game decently optimized.
