first clouds now hUMA's

ill believe it when i see it this was said before for ps3 vs 360

sure sony's first partys will have a noticeable difference but what about the top selling games which are 3rd partys COD GTA BF ect

I know?

AMD the person who actually makes the GPU is saying this tho, and yet you still believe some 3rd party devs? lol denial much. Don't bother responding to my post I simply don't have time to respond to someone who's so brainwashed by MS to face facts.

User was banned for this post.

yo_john117

Your answer/question suggests AMD is only saying this because they are trying to sell hUMA. Which implies they are lying about it being better just to sell the product. That logic makes absolutely no sense.

I don't see anywhere that you say hUMA is their new thing.

If they thought MS was better without it, yes they would say it. It's not like the One's apu isn't their tech. I can't seem to grasp your logic.

First I'm reporting you for the brainwashed comment... It is one thing to disagree with someone and explain why (like I did), it is another thing to insult them; a bit of taunting and even trashtalk may be fine; but I'm getting tired of this "brainwashed" comment against anyone who disagree with you and when you close the door the debate with this comment.

Second, as I said in my post, AMD did not say "PS4 blah blah blah"... NeoGAF/people on internet forums did that and this thread title is misleading...
So, yes I totaly believe AMD when they are talking about the hUMA technology... Now what the internet community is making out of this, is another story.

AMD burning bridges with MS?

I would think more so to promote their product than the PS4 in the hopes that PS4 graphics look noticably better on multi-plats or exclusives... Which they probably will to a small extent, but Sony devs do a great job of optimizing graphics anyways so AMD may just want to piggy back on that to promote their product.

It sounds like cool tech. My problem with AMD is they always talk about new tech and how great it is. When the rubber hits the road, performance is never what is promised. It's all hear say, if I chose to listen to anybody it would be the software developers. It's really just a choice between theory or reality.

Huh...interesting...

Kevin Bachus:  Started working at Microsoft in 1997 as the Project Manager of DirectX, he left that positon in 1999 to become the Director for Third-Party Development at Xbox and left that position in May of 2001.  Four months before the Xbox was released.  He's had 7 positions since.

Seamus Blackley:  Started working at Microsoft in 1998 and left in 2002.  A year after the Xbox was released.

Ted Hase:  A long-term employee, he started in 1991 as a systems engineer, then a program manager, before becoming a PR guy until 2003.  In 2003 he became the program manager for the first iteration of the XBLIG program, and a year later became a corporate stratigist.  A position he kept until 2006.  He now works at Aristocrat, the people behind The Walking Dead game series.

 Otto Berkes:  Like Ted Hase, Otto was a long-term employee and wore many hats at Microsoft.  The longest position he served was his first at Microsoft, as a developer of DirectX until June of 2000.  He would rejoin the Xbox team in 2009 to help develop the Xbox One.  In 2010 he left to moved onto a GM position, then a year later worked on developing Microsoft's cloud services, after which he left to work for HBO.

First, let's understand one thing.  Intelligent and creative people have a tendency to want to do lots of things, they move up and one quickly.  Only Otto actually held positions for more than 3 years.  The majority held positions for one or two years before moving on to new challenges.  Two of them only stayed with Microsoft for 5 years or less.

Second, none of them were forced out or forced to move on from their positions.  They all had opportunities to advance and take on more challenging roles and they took them, and they continued to take them.

J Allard:  Was a long-term and instrumental employee of Microsoft, as was Robbie Bach.  Considering both still worked for Microsoft in 2010, when much of what was planned for the Xbox One was already decided (as per the 56-page Durango document), my guess is that their issues were unrelated to the Xbox One but likely with other devices, namely the Kin and Courier.  I'm sure there was frustration with the fact that the Kin was wrestled away from the EED and handed over to the Windows Phone team, as well as when the Kin ultimately failed that the blame for the failure fell on J Allard and the EED not on the Windows Phone team.  Internally at Microsoft at the time there was a lot of politics, siloing, and tension.  It wasn't until recently that that atmosphere has begun to change.

Neither was forced out, both left on their own accord, though I'm sure not happily. 

Marc Whitten has been involved in the Xbox product development since he began working at Microsoft in 2004.  Prior to that he worked at IBM.  Phil Spenser has been involved in developing games at Microsoft since 2002.  A great deal of others have also been a part of the team, but few people at the level of talent most of these people are at stay in one role or company for too long.  Lifers are rare today, and even more rare in technology fields.  
 

Not to burst anyone's bubbles over this, but the Xbox One incorporates its own technology as was explained back at the architectural panel at the Xbox One reveal:

Archtectural Panel Video

"we have to invest a lot in coherency throughout the chip, so there's been io coherency for a while but we really wanted to get the software out of the mode of managing caches and put in hardware coherency for the first time on the mass scale in the living room on the gpu."

-->hUMA is AMD's definition of a unified memory implementation with certain features. It seems Xbox One has the same features implemented but they just don't call it hUMA due to the extent of customization of the chip.

The Verge: 
"The AMD chips inside the PlayStation 4 and Xbox One take advantage of something called Heterogeneous Unified Memory Access (HUMA) "


Source