It was closer to about 30%, which is by all means unacceptable. But 100% is an exaggeration.
Curious, but are there any sources on whether any launch 360s are still going?
I'd hazard a bet that close to all of them are dead.
It was closer to about 30%, which is by all means unacceptable. But 100% is an exaggeration.
So the OS of an unreleased console is not functioning 100%? Shocker. Does anyone expect MS to release a console that crashes all the time? It would be suicide.
No I think he's technically right - the actual bottleneck is the usage of DDR3 RAM instead of GDDR5 - ESRAM is just there to lessen the impact of DDR3's low bandwith....
Then the DDR3 is the bottleneck, not the ESRAM.
You could have just said you have no clue about anything CS related. Would have saved so much unnecessary keystrokes.
Indeed I believe it's just semantics. Like cboat said, they could fix it before launch, I'm sure they're on it as we speak. A slow, sluggish snap feature could be considered broken by some people's standard, slow and in need of fixing by another's. Hell I've seen people call 30fps a "slideshow" when it's perfect for others. Lots of ways to look at it.Seems like semantics to me.
So the OS of an unreleased console is not functioning 100%? Shocker. Does anyone expect MS to release a console that crashes all the time? It would be suicide.
I posted mostly Sony stuff,some people just have their preferences.Do you ever post anywhere that is not Microsoft related? Your post history is frightening. Do you enjoy games or just Microsoft?
Do you ever post anywhere that is not Microsoft related? Your post history is frightening. Do you enjoy games or just Microsoft?
Eh, not too much CYA. Basically sounds like snap may be ironed out or lessened for launch, xbl features not as much, compounded by users expecting a gold standard from xbl.Nice seeing the CBOAT post.
My only issue is he sort of sets himself up to cover in case he's wrong like "Snapback is broken: Fact (but maybe "probably") fixed before launch".
Just wish he could be definite if assertions are being made. Otherwise, I'm with the guy and the storms.
Then the DDR3 is the bottleneck, not the ESRAM.
/damage controlActually very much a hardcore gamer. My recent post history is entirely because of the ongoing carnival of stupid.
That and I'm currently taking a complete break before next gen because I was burnt out.
Nice seeing the CBOAT post.
My only issue is he sort of sets himself up to cover in case he's wrong like "Snapback is broken: Fact (but maybe "probably") fixed before launch".
Just wish he could be definite if assertions are being made. Otherwise, I'm with the guy and the storms.
They survived Windows ME. They'd survive the XB1 crashing all the time too.
As a wage worker my entire life, I'm always so surprised by how much initiative and motivation is missing. No one ever works as hard for his master as he does for himself or his true and equal peers and no one has ever washed a rental car. The best a wage worker can hope for is a benign monarchy - and they do exist - and when they do, they beat the snot out of a malignant monarchy AND a democratic company. They beat a malignant monarchy because malignant monarchies demotivate. They beat democratically run companies because they're quicker and more efficient. They're also exceedingly rare and get rarer the larger the companies get.Interestingly enough, you make one of the bigger criteria for analysis on 'how you help or enable coworkers to complete their tasks', and it directly eliminates this competition. The staunch teams that took this stackranking to heart abandon it to instead help the previously amicable teams to better the working environment for the entire org. Now, of course you might still get some jockeying--but what I've seen of the process has been very nice for my org.
He's not technically right about anything. A bottleneck is just the part of the process that impacts performance the most. In the case of the Xbone, that's currently managing the eSRAM.
If devs didn't utilised eSRAM and just used DDR3 (I don't even know if this is possible for them to do), then the main RAM would then be the (even bigger) bottleneck.
Oh shit. Between the vampire and the fish, this is going over the falls real quick.
They survived Windows ME. They'd survive the XB1 crashing all the time too.
Nice seeing the CBOAT post.
My only issue is he sort of sets himself up to cover in case he's wrong like "Snapback is broken: Fact (but maybe "probably") fixed before launch".
Just wish he could be definite if assertions are being made. Otherwise, I'm with the guy and the storms.
the b/w of ddr3 is one bottleneck and size of the esram is another bottleneck.
Rolling down the river.Actually very much a hardcore gamer. My recent post history is entirely because of the ongoing carnival of stupid.
Big difference there.
ME: launched in 2000.
XP: launched in 2001, replaced ME.
The XBone will not be replaced after a year.
Actually, he's a group manager which has nothing to do with PR.
What he's doing here is entirely on his own.
A proven leader with 18 years experience in entertainment and technology marketing. Extensive global experience in product management, marketing, and strategic planning. Deep background in Hardware and Software planning, development and marketing.
Has planned, executed and managed some of the largest launches in entertainment including Kinect for Xbox 360 and the new Xbox 360 S console.
Most recently, led the Hardware and all-up Product Planning efforts for Microsoft's next-generation console, Xbox One.
Extremely passionate around technology, marketing and team development.
Specialties: Marketing, strategic planning, product management, product planning, partner relations, quantitative marketing, media & entertainment, technology, video game industry, sku management, project management, PR Spokesperson
They survived Windows ME. They'd survive the XB1 crashing all the time too.
CBOAT pretty much said the same thing in a roundabout way:
Perhaps they just perceive the word 'broken' differently? Maybe a fairly sluggish snap feature is considered broken to cboat? Maybe to the dev I talked to it's not necessarily broken, just needs fixing.
A year is plenty of time to fix the XB1 OS, IMO.
Actually very much a hardcore gamer. My recent post history is entirely because of the ongoing carnival of stupid.
That and I'm currently taking a complete break before next gen because I was burnt out.
Actually very much a hardcore gamer. My recent post history is entirely because of the ongoing carnival of stupid.
That and I'm currently taking a complete break before next gen because I was burnt out.
The real shock here, is that some of you can confuse journalists with videogame reviewers.
They play games, give us a score and an opinion ( that's the order of importance ). Bob Woodward and Carl Bernstein they most certainly are not.
Exactly the point raised in the FamousMortimer thread earlier today. Always a fallback.
Any company leader who openly engages his customers is engaged in PR, regardless of what his title is or his official duties are.From Albert's LinkedIn page (impressive resume, btw):
Product managers need to know Marketing, and their job often requires PR.
And the reputation from a year of shitty hardware and gimped ports? ME never shook it off, and neither would the XBone.
I posted mostly Sony stuff,some people just have their preferences.
thanks!QUICK ROUGH TRANSLATION
From Albert's LinkedIn page (impressive resume, btw):
Product managers need to know Marketing, and their job often requires PR.
I do get a bit defensive which is embarrassing but most of the time I try to keep a cool head hehe.That is very true, but Loudninja I don't constantly running defense when anything anti sony comes out. I see you as a Sony centric gamer that loves to keep people updated on sony related games but not to any extreme.
I guess for the time being we can only sit tight and wait till we get more corroborative evidence in favor of any of those 3 cases.
People still don't believe that Albert was sent to here and reddit to do damage control...
aside from the fact that it isnt nearly big enough to cause that type of a bottleneck? Depending on how its addressable by the GPU then the GPU can theoretically move a full up amount of information in and out of it at a minimum of 2 clock cycles which will not starve the rest of the ALU for resources.
You can't be definite about something a month away. Theoretically they could fix it. Afford him some room for speculation. He's sticking his neck out this much for us.
Actually very much a hardcore gamer. My recent post history is entirely because of the ongoing carnival of stupid.
Exactly the point raised in the FamousMortimer thread earlier today. Always a fallback.
Actually, he's a group manager which has nothing to do with PR.
What he's doing here is entirely on his own.