Your reading comprehension sux. Ole simply told us that the problems XB1 face is due to how bloated and inefficient DX11 is in comparison to PS4 API. But yet still, the game in question was near parity.

He said, ” In general – I don’t really get why they choose DX11 as a starting point for the console.”

And the most amazing thing he shared was that On Xbox One it easily could be one million times slower because of all the bookkeeping the API does.

One million times slower because of DX11, but you still need a pixel counter to tell you the difference between Metro 2033 on the PS4 and XB1. 40 per cent resolution boost in favour of the Sony platform manifests as a slightly clearer image, and that only when you’re eyeballing, pausing, and showing still shots of the game.

He also said, “We may push 40 per cent more pixels per frame on PS4, but it’s not 40 per cent better as a result… your own eyes can tell you that.” And he’s right.

At this point we should all be asking, “how powerful is the PS4 when we have a console like XB1 running a bloated API producing 3rd party games at near parity?” In that current environment Oles insisted that the PS4 is just a BIT more powerful when comparing 3rd party multiplats. How? I mean it should be a whole LOT MORE powerful if thats the case right? Why is it only a little bit, when its common knowledge that the XB1 is handicapped because of its current API. Is Oles trying to tell us something?

This is what happens when you develop games specifically for XB1, which is powered by the “legacy” heavy DX11.

And how is Quantum Break even possible? Thats two games that are leagues ahead of the competition in their respected genre fx wise and in scale. Your ending statement is bogus because you couldn’t even understand where Ole was coming from, and ultimately suggestion.

http://vimeo.com/109943521

They think they are getting something which they will get within 20 years time (2more xboxes) and we will get it with one GPU upgrade 😀

You really didn’t understand what you just read did you? He’s saying that DX (any DX) is a stupid idea for the consoles. And he even uses an example that paints the picture perfectly by saying how you couldn’t even see the same draw calls on the PS4 on their profilers will on the X1 it took up an entire core because of DX (and that includes DX12, cuz 7.5 times better is nothing when DX11 draw calls capabilities are so bad when compared to PS4 true cxonsole API. You’re obviously a fanboy who wants to believe some other nonsense. But he’s telling you.

Here is what 4A Games’ chief technical officer Oles Shishkovstov (Metro Redux)
has said about the two systems draw calls capabilities.

“Oles Shishkovstov: Let’s put it that way – we have seen scenarios where a single CPU core was fully loaded just by issuing draw-calls on Xbox One (and that’s surely on the ‘mono’ driver with several fast-path calls utilised). Then, the same scenario on PS4, it was actually difficult to find those draw-calls in the profile graphs, because they are using almost no time and are barely visible as a result.

In general – I don’t really get why they choose DX11 as a starting point for the console. It’s a console! Why care about some legacy stuff at all? On PS4, most GPU commands are just a few DWORDs written into the command buffer, let’s say just a few CPU clock cycles. On Xbox One it easily could be one million times slower because of all the bookkeeping the API does.

But Microsoft is not sleeping, really. Each XDK that has been released both before and after the Xbox One launch has brought faster and faster draw-calls to the table. They added tons of features just to work around limitations of the DX11 API model. They even made a DX12/GNM style do-it-yourself API available”
In other words the PS4s API is much much better at handling draw calls, so it should still be a lot better than DX12 on the X1.

“Oles Shishkovstov: Let’s put it that way – we have seen scenarios where a single CPU core was fully loaded just by issuing draw-calls on Xbox One (and that’s surely on the ‘mono’ driver with several fast-path calls utilised). Then, the same scenario on PS4, it was actually difficult to find those draw-calls in the profile graphs, because they are using almost no time and are barely visible as a result.

In general – I don’t really get why they choose DX11 as a starting point for the console. It’s a console! Why care about some legacy stuff at all? On PS4, most GPU commands are just a few DWORDs written into the command buffer, let’s say just a few CPU clock cycles. On Xbox One it easily could be one million times slower because of all the bookkeeping the API does.

But Microsoft is not sleeping, really. Each XDK that has been released both before and after the Xbox One launch has brought faster and faster draw-calls to the table. They added tons of features just to work around limitations of the DX11 API model. They even made a DX12/GNM style do-it-yourself API available”

So in other words, way better draw call performance on the PS4 right now. So even with DX12, it wont be as good as PS4’s API now.

I call BS. Because nothing, ABSOLUTELY NOTHING, looks as good on x1 as it does on PC on Ultra settings. I realize now you don’t have a gsming rig, at least not one from this decade. That statement alone makes the rest of your argument redundant.

No, cuz what they aint telling you is how the PS4’s API could do way more draw calls than the X1 and its not some monster powerhouse is it? And MS has already bettered their draw call performance since their updated SDK. PS4’s API is like Mantle but better for the PS4. Also the main way you get better performance on DX12 over DX11, is by having the devs do certain routines themselves. Thereby, optimizing it to their liking. Smaller studios wont like that. DX12 is mainlu marketing propaganda but fanboys eat the s h*t up.

Wow, fanboys are to much.