Numerous developers have said the opposite...but you believe this one how convenient..

The power gap is there period,. it's technology not fairy dust, a SDK is not going to make a GPU 40% more powerfull. The proof is already there we know the specs of each box.

2. The guy admits there is going to be a power gap. You have apparently conditioned yourself to just ignore any text that doesn't say there is a huge generational leap or something. It's funny, but not really healthy for discussion. You spread the same FUD in other threads, making it seem as if anyone here who likes the Xbone has this strange delusional idea that there isn't a power gap.

Hope those helped.

Hummmmmm...

GTX 580: 48 ROPs @ 772MHz
GTX 680: 32 ROPs @ 1006MHz *1058MHz boost*

We are talking here about 32 vs 48 with a big increase in clock for the 32... in any case the 48 is less than 5% faster than the 32... overkill for 1080p in both cases.

Now 16 vs 32 with the first running with 53Mhz more clock... seems like the 16 is really a bottleneck if you ask me for 1080p games.

No thats not what I am saying. People saying "Better SDK, Drivers will close the gap" are wrong, and there are still plenty of them. Hardware is hardware there is no making up a 40% GPU Compute advantage by tricks. It will always be there, the more demanding games get the more pronounced it will be. PS4 also improves over time, it's pretty standard.

He quoted one spec which is meaningless, since a gpu's performance is based on its overall design. Some of those specs will be higher some will be lower. I'm not saying XB1 GPU is as powerful, definitely not.

Firstly: It is cool to use words like ROP and TMU and other buzz words, unfortunately you don't seem to know what they mean. As in real life, it is the weakest link that butes you in the ass in the end.

A 680gtx has 32 ROPs (at over 1GHz). This is more than enough to rasterize everything at 1080p/60Hz. Now the question is how many ROPs at what frequency you need to comfortably live at 1080p/60Hz (AMD recommends 32ROPs, by the way). Here is the sad truth for you: 16ROPs just don't cut it. This is the very reason why MS upped the clock frequency in the gpu instead of putting more CU's into their APU (as they discussed this decision without really telling why they went that way when the clock uptick was announced with great fanfare). The XBox One apu has enough compute power, but not enough raster power for a convenient 1080P/60Hz. (yeah, yeah, I hear people screaming "Forza 5! Forza 5!", neglecting to mention just how many clearly visible compromises that game had to implement to get to that goal. And just for the future: Every future game that goes 1080p/60Hz will show the same effect).

Secondly: The new developer kit is much faster. Cool, but it doesn't  run your game faster (unless the former compiler was shit). A faster SDK means that the compiler/assembler is now compiling the code much faster, like a minute instead of three, the linker is now taking only five minutes instead of fifteen to link the whole code bits into an executable. This is very nice for all developers but has no consequence on the fact: There are not enough ROPs for a convenient 1080p/60Hz.

Maybe not but there is for 900p/60fps. If Halo, for example, is 900p (which I expect) @60fps and can have IQ and fidelity that matches Ryse then the game will look amazing and nobody will complain. It's the 720p/60fps with bad aliasing that is in BF4 that has people buzzing about bad graphics. A better SDK will help solve this problem. I expect all if not most 30fps games to be 1080p on Xbox One and 60fps games to be 900p. I'm sure some will still be 720 but they should have a good AA solution so it won't look nearly as jaggy as BF4.

Not going to make up a 40% GPU compute diff no amount of magic will,.. Technology is technology it is not magic.

Firstly: It is cool to use words like ROP and TMU and other buzz words, unfortunately you don't seem to know what they mean. As in real life, it is the weakest link that butes you in the ass in the end.

A 680gtx has 32 ROPs (at over 1GHz). This is more than enough to rasterize everything at 1080p/60Hz. Now the question is how many ROPs at what frequency you need to comfortably live at 1080p/60Hz (AMD recommends 32ROPs, by the way). Here is the sad truth for you: 16ROPs just don't cut it. This is the very reason why MS upped the clock frequency in the gpu instead of putting more CU's into their APU (as they discussed this decision without really telling why they went that way when the clock uptick was announced with great fanfare). The XBox One apu has enough compute power, but not enough raster power for a convenient 1080P/60Hz. (yeah, yeah, I hear people screaming "Forza 5! Forza 5!", neglecting to mention just how many clearly visible compromises that game had to implement to get to that goal. And just for the future: Every future game that goes 1080p/60Hz will show the same effect).

Secondly: The new developer kit is much faster. Cool, but it doesn't  run your game faster (unless the former compiler was shit). A faster SDK means that the compiler/assembler is now compiling the code much faster, like a minute instead of three, the linker is now taking only five minutes instead of fifteen to link the whole code bits into an executable. This is very nice for all developers but has no consequence on the fact: There are not enough ROPs for a convenient 1080p/60Hz.