EDGE: "Power struggle: the real differences between PS4 and Xbox One performance"

I've read the quotes, did you read the Digital Foundry interview portion I quoted? The software engineer specifically designates their current memory setup as an EVOLUTION to what was on the 360. Things that evolve usually don't get worse. Where are these articles or statements from devs of the gaming media suggesting that there was much difficulty dealing with 360 development from the memory perspective? Sure, early on I'm sure there were some hurdles to climb, and some new methods to learn, but after 8+ years of developing using this method, how is it all of a sudden an issue again?

Read the article in the OP. Developer says "eSRAM is a pain"
 
Dude I love you, you are quite possibly the biggest Sony fan in all of GAF :)

Microsoft is not calling it quits and they will sell a bunch of consoles.

The biggest Sony fan wouldn't have played on a 360 for most of this generation and blow about $60 in Gamertag changes.

I said IF, trying to support the other person's argument. I understand competition is good for the industry, but Xbox isn't taking Microsoft anywhere. They lost money on Xbox, lost some with 360, and will probably lose more with the Xbox One.
 
Dude I love you, you are quite possibly the biggest Sony fan in all of GAF :)

Microsoft is not calling it quits and they will sell a bunch of consoles.

"Sega is not gonna call it quits and they will sell a bunch of Dreamcasts."

No joke, the deja vu triggered by your post was startling.
 
Yes I've read the entire article and pointed out many fallacies multiple times.

Like people have said, it has "evolved" as you'd like to put it, to do more than it did in the x360 and it has to do this due to the disadvantageous position the xb1 is in hardware wise compared to the PS4 doing more with it is proving to be very difficult. Please remember that the statement you are quoting is from a PR interview, please consider the implications of that.

No need to bring the PS4 into this specific debate we're having. I know the PS4 memory architecture is better and more efficient. I'm strictly talking about the Xbone's memory here, and how it compares to the previous generation. I want to know how something that is considered an evolution, and more capable than its previous iteration, make it automatically more difficult, and where people are all of a sudden getting the idea that the 360's memory architecture was difficult to develop for? I feel like some people here are just grasping for straws, just to make the Xbone's memory architecture seem THATT much more inferior to the PS4's method.
 
'Upclock issues too'?

Is that an issue with performance or an issue with the return of RROD?


Maybe he's talking about another up clock across the board?



Edit: Before you say "no they're not stupid, they won't do that" think about all the reversals and everything that has transpired since E3. MS is dead set on short term gains no matter the cost
 
The biggest Sony fan wouldn't have played on a 360 for most of this generation and blow about $60 in Gamertag changes.

I said IF, trying to support the other person's argument. I understand competition is good for the industry, but Xbox isn't taking Microsoft anywhere. They lost money on Xbox, lost some with 360, and will probably lose more with the Xbox One.

I'm not being critical, I'm just saying...

"Sega is not gonna call it quits and they will sell a bunch of Dreamcasts."

No joke, the deja vu triggered by your post was startling.
Microsoft is not Sega though.
 
Maybe he's talking about another up clock across the board?

Yeah, he could be but my question still applies. This could be just a slight hiccup or it could be something drastic like causing the consoles to overheat. I'd like to know which is was because SURELY MS won't risk releasing another console with a problem they know exists?
 
I can't really trust Microsoft right now. Original Xbox had overheating issues and the power cord recall. 360 had RROD, E74, and disc scratching. My brother's Slim from 2010 is sometimes louder than my 60GB PS3 from 2006. The disc drive will occasionally make ungodly noises and then go back to normal.

Customers are going to see $500 and think that the extra $100 will ensure a good quality machine. Oh, how wrong they might end up being.

the average consumer might also see the $100 difference as a power advantage. "higher price? it must be more powerful"
 
Read the article in the OP. Developer says "eSRAM is a pain"

So right now we have a "developer" saying eSRAM is a pain, but in what context? We don't know the talent and experience level of the developer, we don't know if he's new to the Xbox platform. Heck, at this point the "developer" could be a member of a small minority of developers that are having these initial issues with the memory architecture, while the majority aren't having nearly the same issues. It will take the opinion of more than just "A developer" to convince me that this is a growing concern.
 
No need to bring the PS4 into this specific debate we're having. I know the PS4 memory architecture is better and more efficient. I'm strictly talking about the Xbone's memory here, and how it compares to the previous generation. I want to know how something that is considered an evolution, and more capable than its previous iteration, make it automatically more difficult, and where people are all of a sudden getting the idea that the 360's memory architecture was difficult to develop for? I feel like some people here are just grasping for straws, just to make the Xbone's memory architecture seem THATT much more inferior to the PS4's method.

It's all relative my friend. the past doesn't apply here
 
i ams cshokked athis urpsriise.truly >am



btw i hope fyou arent fans of 1080p on xone, wehn hw is out in wild you wil se wat I meant about isues. puclocks too. Risk evwyerhwere. this palce is ntus. 2014 was beter pln.

Another RROD coming & issues within Native 1080p? Oh, snap.

I've said it before, & I'll say it again: PS4 is better designed to run Native 1080p perfectly than Xbox One.
 
I'm so happy. I want to watch Xbox burn after all the anti-consumer stuff they tried to pull.
tv sports tv sports tv tv tv sports!
 
I feel like some people here are just grasping for straws, just to make the Xbone's memory architecture seem THATT much more inferior to the PS4's method.

The overwhelming majority of GAF believes that xbone architecture is that much inferior, and rightfully so. So far everything we've seen and heard points to a large gap (40%+ and i'm being conservative).

Nothing wrong with you defending your taste in games but when you start to make arguments about how the gap may not be as large as it seems be, then you start raising red flags.
 
...I want to know how something that is considered an evolution, and more capable than its previous iteration, make it automatically more difficult...
You're really clinging to "evolution" as a saving grace for that embedded memory. Evolution generally just produces features/functions that are suitable to task, not necessarily superior. It could be suitable for what the XBO needs to function optimally but that doesn't guarantee it's easier to work with.
 
Microsoft is not calling it quits and they will sell a bunch of consoles.
They probably will sell a bunch of consoles, but that doesn't mean that investors won't axe it if it underperforms. They are already circling.
 
No need to bring the PS4 into this specific debate we're having. I know the PS4 memory architecture is better and more efficient. I'm strictly talking about the Xbone's memory here, and how it compares to the previous generation. I want to know how something that is considered an evolution, and more capable than its previous iteration, make it automatically more difficult, and where people are all of a sudden getting the idea that the 360's memory architecture was difficult to develop for? I feel like some people here are just grasping for straws, just to make the Xbone's memory architecture seem THATT much more inferior to the PS4's method.

No one is saying that the 360 was difficult they were saying it was "more difficult than not having edram" that doesn't add much complexity.

and of course the PS4 is relevant in this, the difficulty of development is entirely based on the difficulty of development for the opposition console or PC, That's what gives us a baseline of what is easy and what is hard. It's like playing a sport, it's only as hard as whoever your playing against.

Let's look again at that quote you posted:
now texture out of ESRAM if you want to

Ok so a new ability to texture out of esram, you know what this means? new API for it. But 32 mb is small? can you put full textures in there or are you forced to use PRT? I'd guess PRT, new API for it. So you would have to use 2 new APIs to do this, how good are these new APIs? we don't know, from the developer quote in the OP of this thread we could say "horrible"

"Gosh, it would sure be nice if an entire render target didn't have to live in eDRAM," and so we fixed that on Xbox One where we have the ability to overflow from ESRAM into DDR3 so the ESRAM is fully integrated into our page tables and so you can kind of mix and match the ESRAM and the DDR memory as you go.

Do you know what this means? It means the memory is now addressable. that means the developers can choose where to put things, This allows for more possibilites, HOWEVER, this means developers need to put things in the right place, now that we know they do this, let's look again at the esram and the "1024 bit bus"

It's not a 1024 bit bus, it's 4x 256 bit bus's linked on 4 pipelines each of 8mb esram, the developers need to manage these as they are now addressable to get access to the 109gb/s read speed, it seems you need to have your data in all four "8mb chunks"

Esram is not edram, the Article you quoted is MS PR and shows falsehoods even in the small snippet you quoted.
 
Three red lights all over again would be so entertaining. The meltdowns would be glorious. What little trust people have for launch day Xbox hardware would be completely crushed.
 
I always felt that the XB1 felt a little rushed out of the door, and the new CBOAT post pretty much nails it saying 2014 was a better plan.

Whether the hardware works as advertised I don't know, but I really doubt parts of the OS will be fully functional on release, I guess we'll see in a few weeks.
 
Maybe he's talking about another up clock across the board?

No reasonable upclock would make any real impact on the performance gap...and if they are experimenting with it and seeing any heat issue at all, on an always on 10yr machine, and they do it...god help them.

..and it wouldn't really save the launch titles or first impressions?

CBOAT you mischievous man/woman/computer algorithm
 
that would be ridiculously risky... At some point the higher ups will put a stop to this, they can't afford another RROD.

But the system is virtually empty inside with a huge and i mean HUGE ass fan. And the power brick is once again outside. Imo, they could afford another upclock. I think what cboat is trying to tell us is that there will be another upclock.
Lol you just wanna watch a desperate company play Russian Roulette

I think the cooling inside the system can take it. The more parity between multiplatforms the better it is for everybody.
 
The buttocks has graced us with it's presence once more. It does seem like MS should have just waited for a 2014 release after they had ironed out most of the kinds that are haunting them now so far.

I think it's pretty obvious that when Microsoft saw this:

jE8VFUr.png



...they went into straight up panic mode. There are so many aspects about the system that seem rushed. Why do you think they apparently delayed their reveal event?

Of course they'll never admit it.
 
But the system is virtually empty inside with a huge and i mean HUGE ass fan. And the power brick is once again outside. Imo, they could afford another upclock. I think what cboat is trying to tell us is that there will be another upclock.

Sounds more like another issue to me:

'you wil se wat I meant about isues. puclocks too'
 
Ok so a new ability to texture out of esram, you know what this means? new API for it. But 32 mb is small? can you put full textures in there or are you forced to use PRT? I'd guess PRT, new API for it. So you would have to use 2 new APIs to do this, how good are these new APIs? we don't know, from the developer quote in the OP of this thread we could say "horrible"

Do you know what this means? It means the memory is now addressable. that means the developers can choose where to put things, This allows for more possibilites, HOWEVER, this means developers need to put things in the right place, now that we know they do this, let's look again at the esram and the "1024 bit bus"

It's not a 1024 bit bus, it's 4x 256 bit bus's linked on 4 pipelines each of 8mb esram, the developers need to manage these as they are now addressable to get access to the 109gb/s read speed, it seems you need to have your data in all four "8mb chunks"

Esram is not edram, the Article you quoted is MS PR and shows falsehoods even in the small snippet you quoted.

What's PRT?
I assume using 2 APIs instead of only one has an impact on performance because it add more processing time?
 
So, regarding CBOAT's comment (thanks for the new info!)

Was it about possible issues with the X1 happening NOW or maybe they are considering another upclock which might be overkill and cause trouble down the line?

Could Sony have upclocked ps4's cpu or gpu and this is a reactionary action, or are they having problems without even considering an upclock? That's a damn big case to be overheating, so it must be yield related but that was already suggested before..Another upclock wouldn't close the gap by any means and would only increase the possibility of hw failure. They really must be scrambling over there..

Anyway, CBOAT has spoken, so things must be complicated for MS. I would be very worried if I was getting one at launch, but that's just me.
 
I think it's pretty obvious that when Microsoft saw this:

jE8VFUr.png



...they went into straight up panic mode. There are so many aspects about the system that seem rushed. Why do you think they apparently delayed their reveal event?

Of course they'll never admit it.

Yea for sure. I wonder why they didn't start preparing earlier. I mean this was the longest gen ever. Maybe they just got lazy.
 
I've said it before, & I'll say it again: PS4 is better designed to run Native 1080p perfectly than Xbox One.

Definitely agree with this. Every time new info has come out ever since the specs reveals it's just become more and more obvious that it's better designed for them with by far less compromises needed.

Wow, did not expect to see a new strong CBOAT post when I came in to read the latest info/posts. Appreciated as always.
 
Welp, now I'm a bit worried about my launch console, and how stress-tested the upclocks were.

Should have been worried when the specs came out for it. When they are charging 100$ more then the superior competitions hardware, and when they focused on nothing but TV and sports at their initial reveal.
 
Yea for sure. I wonder why they didn't start preparing earlier. I mean this was the longest gen ever. Maybe they just got lazy.

I'm certain in 2012 some Sony execs were quoted saying they wouldn't announce until they'd seen what MS had to offer, so maybe MS thought they had one more holiday season of selling the 360.

Only link I can find is this old one from Develop.

http://www.develop-online.net/news/sony-ps4-to-be-announced-after-next-xbox/0110985

Edit, here's a better link of Kaz Hirai stating "why go first when your competitors can look at your specifications and come up with something better?"

http://www.computerandvideogames.co...ps4-release-date-after-xbox-720-release-date/
 
Yea for sure. I wonder why they didn't start preparing earlier. I mean this was the longest gen ever. Maybe they just got lazy.


They did start preparing earlier, at least on the software side -- Published games on the 360 all but dried up on the last two years, games like Dead Rising 3 and Ryse were moved to next gen, etc.


It just seems like on the hardware side, it simply wasn't enough.
 
What's PRT?
I assume using 2 APIs instead of only one has an impact on performance because it add more processing time?

PRT is Partially resident Textures, it means only copying the section of the texture you wish to use. The benefit is of course you can fit a lot more useful texture data in 32mb of esram. As to using more processing time, I don't know but I don't believe the processing time is of particular concern as it is more of a size/bandwidth issue. The Reason I was talking about it is because using PRT will be beneficial due to esram, but it is a new API which seperates it from the xbox 360 edram, that the poster seemed convinced was the same as edram.
 
Yea for sure. I wonder why they didn't start preparing earlier. I mean this was the longest gen ever. Maybe they just got lazy.
I think maybe development just went slower than expected and they fell behind. Everything seems to have gone well for Sony, so it just made things worse. Microsoft was just unwilling to let Sony launch first and so it all seems rushed to market. Plus they apparently did not expect the bad response to their first reveal.
 
Top Bottom