68GB/s (DDR3) + 102,4GB/s(eSRAM) + 30GB/s (CPU-GPU Interconnect)
= 200,4GB/s
They did the same thing back then with the 360 eDRAM setting.
They claimed 278GB/s bandwidth. :smile:
Xbox One (Durango) Technical hardware investigation
- Thread starter Love_In_Rio
- Start date
- Status
68GB/s (DDR3) + 102,4GB/s(eSRAM) + 30GB/s (CPU-GPU Interconnect)
= 200,4GB/s
They did the same thing back then with the 360 eDRAM setting.
They claimed 278GB/s bandwidth. :smile:
Most people are saying they just unethically added the 30GB/s of CPU bandwidth to the normal 170GB/s.
Of course my sentiments laid with an overclock, but a possible gaffer insider implied otherwise so i cooled off a bit on that.
GPU clock has to hit 1 GHz to get there. Some people have written that Jaguar does not scale well to clock bumps past 1.6 GHz.
That could well be it. Disappointing, but not unlike past PR efforts. The overclock idea did sound ambitious for extra ESRAM BW; just fiddling the numbers is a lot easier.
Last edited by a moderator:
Makes an overclock very unlikely.
Unless the GPU and its connection to ESRAM could be over clocked asynchronously to the CPU?
Resolution reduction makes sense. I mean, the fact that most people have absolutely no idea that many games run at sub-720p resolutions on their 60" 1080p TVs means they'll never notice. You can only tell with the UI layer that's rendering pixel sharp text (which shouldn't be affected).
It seems like SHAPE audio processor is getting some recognition at last! It's fucking ace.
Yay, love sound. And in a racing game....
http://www.xbox-360.co.za/2013/05/23/fmod-studio-to-enable-next-generation-audio-on-xbox-one/
It's fucking ace. Yay, love sound. And in a racing game....
http://www.xbox-360.co.za/2013/05/23/fmod-studio-to-enable-next-generation-audio-on-xbox-one/
Last edited by a moderator:
Not 100% sure. But yes, I think we have heard about that, but the guy got the numbers wrong iirc. I think GCN capabilities are exactly the same on both consoles and both GPUs share the ability to draw two primitives per cycle -or per triangle, I don't remember-.
Betanumerical
Veteran
Betanumerical
Veteran
The only difference i can see the queues really making is that they allow you to have more data streams to pick from for when you want you to do something, so you could run more programs on the GPU concurrently, but other then that not much.
ShadowRunner
Veteran
They specifically said they would be using the planes for fast switching in the after conference tech panel IIRC. One plane each for OS/APP/GAME. Don't know if they allow devs to override this. Or maybe i am extrapolating what they were saying from the example they gave. Someone should go back and watch again, see if they get the same impression.
Makes sense to me that they would use different planes for the snapping functionality for apps at the side of the screen, running at a different res/refresh and scaled appropriately, and still having full screen OS/System level notifications on top of the two side by side Game and App planes.
Makes sense to me that they would use different planes for the snapping functionality for apps at the side of the screen, running at a different res/refresh and scaled appropriately, and still having full screen OS/System level notifications on top of the two side by side Game and App planes.
Last edited by a moderator:
ShadowRunner
Veteran
Im pretty certain these customizations in the PS4 gpu are real, Cerny has said so directly i believe.
They are designed to increase efficiency of compute jobs, specifically trying to maximise the use of GPU downtime by having lots of ques that can be picked from to process whenever there is a moment free.
I think the planes picture is obvious:
1: Full Screen Game
2: Full Screen App
3: Snap App
- Status
Similar threads
