My god could you see Microsoft and Apple in a bidding war for games........ poor everyone else.

I welcome it with open arms. It will push them to make our content better.

Keep chumming the waters... I'm right here CBOAT... I can almost taste it.

I'm going to reinstall and re-patch. Before I go off the deep end.... I need solid conclusions first. If it is Microsoft Heil68.... the customer service rep, which I know it is not the poor basterds fault might have to take the brunt. /jk I never get pissy or mean to them.. I know it's not their fault. They are just some poor basterd trying to do their job. Remember that when talking to a customer service rep. . Be nice! :D

@Desmonic

Right @tormentos

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 - although we didn't ship with it on Redux due to time constraints.

Sometimes it's best... to sit back and watch the show. Especially in this situation.

There is way to much conflicting information surrounding this. At this point.

I have had Tormentos actually tell me in this thread... Writing code for a specific API from the ground up in DX12... will not help games on the X1. The API is already in the X1 he says... Yet, there are no games on the market that are written in DX12 engines. "You don't need those engines for the X1. They have been doing this for years on consoles." derp

The Xbox One hardware is specifically built around future DX...."that's from Microsoft's own mouth" Everything about the api in X1 is DX. It's either legacy DX11.2- or an unfinished DX12 API... With all evidence so far pointing to DX12... as the finish line.

With developers bitching and confused why Microsoft choose to build the console around the DX11.... API in the first place. With him stating you don't have to do this on consoles. The Metro developer interview on Eurogamer. The guy specifically states it is NOT a custom API, that it is infact legacy DX11. That counters everything dumbass is saying here.

This is the kind of shit you have to read on here. How do you even start to argue with a person with those beliefs?

:p

EDIT: I may be for everyone else... Not for me. :p

That's expected considering it's an online only game.

Some one is getting contacted, trust me on that one.

I'm not fucking happy at all....