AMD: No Such Thing As 'Full Support' For DX12 Today

[Majestic]

NOPE

 

R7 370 = R9 265

 

Which was pitcairn, which was the 7850.

 

 

just because you got a better product, doesnt mean a damn fucking shit, if you do not sell it.

 

But they do sell them, at a 80:20 ratio. And why are you so hostile anyway.

 

 

Nvidia is marketing their GPUs as superior. While in reality, they are not.

 

That's marketing in a nutshell.... clearly my first assumption about your knowledge in this matter was spot-on...

[Briggsy]

and you failed in marketing 101

 

just because you got a better product, doesnt mean a damn fucking shit, if you do not sell it.

 

Nvidia is marketing their GPUs as superior. While in reality, they are not.

 

Die size can have many explanations outside of pure GPU core. Auxiliary functions that are done on-die also needs Die size..

 

AMD has a few extra cores on their GCN 1.1 and 1.2 cores to run audio, using True Audio... So that alone would increase the size a tidbit.

 

Nvidia does some of their auxiliary functions outside on a extra chip on the PCB (physX), unless they changed that structure.... Havent looked into it for a while.

 

I'm not going to spend all day searching, but there was a PCPer podcast from a year or two ago where Josh Walrus (yes I know its Walreth  ) Explains the GCN Architecture in some depth. I won't try to draw too much from memory because my brain doesn't have ECC, but one thing that I remember was him saying that every 4 shaders is paired with a 5th weaker shader that is highly tuned for advanced mathematical equations. It can perform normal shader functions if a developer codes for it, but destroys in high math like trigonometry etc.. He also compared to Cuda Cores which are all uniformly identical in what they can do.

 

I don't take what any tech reviewer says as gospel, but Mr. Walrus is definitely well read on AMD hardware.

[HKZeroFive]

NOPE

 

R7 370 = R9 265

Yeah, I knew that...

Nah, had a brain fart, thanks for clarifying.

[Majestic]

Yeah, I knew that...

Nah, had a brain fart, thanks for clarifying.

 

You were correct.. the 265 = pitcairn. 

 

Pitcairn = HD 7850/7870 (2012) / R9-270(X) (2013) / R7-265 (2014).

[ivan134]

Wait, I thought it was :

R7 370 = R7 270 = 7850

Nah, 270 is a 270x with lower clockspeeds. Both have 1280 stream processors. It's pretty much 7870 and 7870 GHz Edition. There was no reason to buy a 270x after the 270 launched, because you could just take all the sliders to the right on the 270 (on the twin frozr one at least), save 20 bucks and have yourself a 270x.

[bogus]

GCN 1.2 is 100% DX12_0 compliant and was initially fully DX12 compliant. Once 12_1 was carved out GCN 1.2 was no longer fully DX12 compliant. 

 

Its likely that there could be 12_2 or even 12_3 iterations, which would mean a theoretical graphic card that is fully 12_0 and 12_1 compliant would still not be fully dx12 compliant. 

 

It boils down to word-play, because having full DX12 support is dependent on supporting every current feature, and there being no newer DX12 features getting released. In Nvidia's case, Maxwell supports the newest 2 features, but does not support all of 12_0 features. totally bass ackwards.

But the stupidest shit ever is that they - by they i mean NVIDIA - insist on this shaddy, not clear, missinformed state.

 

Why the fuck would they do that?! Are we waiting for another #VRAM-LIKE-GATE... a #DX12GATE maybe, where along the line someone will uncover some weird shit that will contradict what they advertise and expose them to liability?

 

Are they afraid to expose their IP lol...?

Why don't they inform their customers and the general public? Why wont they do something like AMD and game developers did, wich is bring light to a awkaward situation that's anything but clear? It's really weird for a company who claimed to be developing DX12 for 5 or 6 years....

 

One thing we know, they tried to blame it on the developers but fortunatly it was debunked...

 

Mark my words - be aware of NVIDIA, I sense a shit storm coming and they already triggered damage control.

[Majestic]

@bogus you should work for gawker, sensationalist.

[bogus]

@bogus you should work for gawker, sensationalist.

Why am I a sensationalist? I'm just asking questions and telling what we already know

 

I'm one of the few "sensationalists" that defended what is taken for granted know - wich is the relationship between Mantle and the new APIs. Waaaay but way before all of this. I was bashed, insulted, pointed for being a fanboy... don't call me that.

 

I think people even called me Richard Huddy lover

[Doobeedoo]

Heh heh, AMD clarifying shit before creating unnecessary hype for themselves again.

 

LMAO with that GIF

[Doobeedoo]

Most likely related to gaming, if gauging by Nvidia presentations.

 

The 2 features that Robert Hallock mentions "Rasterizer Ordered Views" and "Conservative Rasterization" are both DX12_1 related, which means GCN 1.2 is fully 12_0 feature compliant... something people are overlooking.

 

 

The slide below confirms this:

 

Why is it like this, being 12.x and make fragmentation, not just 12 since ver. 12 is barely born yet no games on it and then there's fragmentation crap with 12.x again.

[Majestic]

Why am I a sensationalist? I'm just asking questions and telling what we already know

 

No they're sensationalist memes and assumptions you're perpetuating. I don't think any well-read techie will really be interested in #VRAM_GATE or #DX12GATE narratives.

 

AMD acting like the gutmensch has nothing to do with actually being transparent. The whiny fury x pumps, overheating 295x's , the arbirtary frequency ranges of freesync. All stuff nvidia would've gotten another #something_Gate shitstorm over. But no, it's ok, because AMD is underdog so we'll just slide it under the rug.

 

Not saying Nvidia doesn't do some shady shit, but don't pretend AMD to be some saint either.

[Doobeedoo]

Hopefully next year GPUs will have full support of DirectX 12/12.x 

[silberdrachi]

Why is it like this being 12.x not just 12 and make fragmentation. Ver. 12 is barely born yet no games on it and then there's fragmentation crap with 12.x again.

 

Because standards take years to create and years longer to implement. HDMI1.4 barely came out before we started hearing about HDMI2.0 features and release dates. Thunderbolt2 has been out for how long and now we are expecting Thunderbolt3?

 

Not to mention most of the graphics companies never (EDIT: fully) implement the _X versions of the spec, it was the same for DX10 and DX11. They will just support them in the next major revision (assuming the cards can).

[bogus]

No they're sensationalist memes and assumptions you're perpetuating. I don't think any well-read techie will really be interested in #VRAM_GATE or #DX12GATE narratives.

 

AMD acting like the gutmensch has nothing to do with actually being transparent. The whiny fury x pumps, overheating 295x's , the arbirtary frequency ranges of freesync. All stuff nvidia would've gotten another #something_Gate shitstorm over. But no, it's ok, because AMD is underdog so we'll just slide it under the rug.

 

Not saying Nvidia doesn't do some shady shit, but don't pretend AMD to be some saint either.

 

I never said AMD are saints, fuck it's far from it lol... but in this matters AMD is way more transparent then NVIDIA. AMD never denied any of those issues, and specially haven't defined a issue as a feature! (not lately at least)

 

AMD, Intel, even Apple are little girls in comparison to NVIDIA in the shaddy business matters. I'm still waiting for a leak of a major Gameworks contract

[xAcid9]

I'm one of the few "sensationalists" that defended what is taken for granted know - wich is the relationship between Mantle and the new APIs. Waaaay but way before all of this. I was bashed, insulted, pointed for being a fanboy... don't call me that.

Still remember those days, where are they now?   :lol:

[Briggsy]

I never said AMD are saints, fuck it's far from it lol... but in this matters AMD is way more transparent then NVIDIA. AMD never denied any of those issues, and specially haven't defined a issue as a feature! (not lately at least)

 

AMD, Intel, even Apple are little girls in comparison to NVIDIA in the shaddy business matters. I'm still waiting for a leak of a major Gameworks contract

 

Nvidia will likely respond to this in a similar manner to previous issues, where Tom Petersen goes on a PCPer stream and together they try to smooth out the controversy, while highlighting all the great things about DX12_1 and the performance gains that ROV and CRT will bring to Maxwell through gameworks, and the superior DX11 performance of their drivers. I give it a couple weeks tops before we see this.

[bogus]

Still remember those days, where are they now?   :lol:

Preaching and trolling somewhere else I belive.

[Icecube26]

Nvidia will likely respond to this in a similar manner to previous issues, where Tom Petersen goes on a PCPer stream and together they try to smooth out the controversy, while highlighting all the great things about DX12_1 and the performance gains that ROV and CRT will bring to Maxwell through gameworks, and the superior DX11 performance of their drivers. I give it a couple weeks tops before we see this.

DX 11 will be history soon .... and so will be their driver advantage.... and the performance gains through DX 12.1.. ive seen the demo they showed at some convention ... different lightning and smoke effects... pure cosmetic stuff...even NV admits on their own website that assync compute, lower cpu overhead and better thread utilization are key features of DX 12 ... and by not supporting assync compute which i think is the best thing about DX 12 at least at the moment ..they might be screwed until pascal comes out

[Tomsen]

DX 11 will be history soon ....

As much as I would like this to be true, I doubt it..

DX11 will still be relevant for some time to come..

[Humbug]

DX11 will still be relevant for some time to come..

Probably. It will die quickly for majority of AAA games. Because the big game engines are all moving to support DX12 and Vulkan. Frostbite, Unreal 4, Source 2, Unity, CryEngine etc. Cryengine seems to be the most lethargic probably because of financial issues but Chris Robers is getting it done.

 

But for some devs who are using their own in-house engines (rather than licensing the above) they may consider it a lot of work and added responsibility to move to the new gen of APIs. Especially for smaller devs who do not have as much expertise or numbers. They may be more comfortable with the old way of doing things where the driver does the heavy lifting.

 

ps- it will be also interesting to see how the technically incompetent devs like ubisoft adapt to direct X 12 and Vulkan and try to make a stutter free game? No more relying on driver teams from Nvidia and AMD to fix your shit. Application control; the way it should be.

[Icecube26]

As much as I would like this to be true, I doubt it..

DX11 will still be relevant for some time to come..

games that are about to release later this year will still prob use DX 11... i agree with that ....but starting early 2016 u will see more and more  DX12 and Vulkan games

[bogus]

ps- it will be also interesting to see how the technically incompetent devs like ubisoft adapt to direct X 12 and Vulkan and try to make a stutter free game? No more relying on driver teams from Nvidia and AMD to fix your shit. Application control; the way it should be.

 

Ah, big AAA studios actually being responsible for the quality their products performance and not be dependent on resources of IHVs... the dream is closer... I hope so at least.

[Tomsen]

games that are about to release later this year will still prob use DX 11... i agree with that ....but starting early 2016 u will see more and more  DX12 and Vulkan games

Problem is DX12 is windows 10 exclusive, and DX11 will support more windows OS's.

There are more traction this time, compared to previous iterations of DX.

[Majestic]

DX 11 will be history soon .... 

 

There are still games today being released on DX9c

[Notional]

Probably. It will die quickly for majority of AAA games. Because the big game engines are all moving to support DX12 and Vulkan. Frostbite, Unreal 4, Source 2, Unity, CryEngine etc. Cryengine seems to be the most lethargic probably because of financial issues but Chris Robers is getting it done.

 

But for some devs who are using their own in-house engines (rather than licensing the above) they may consider it a lot of work and added responsibility to move to the new gen of APIs. Especially for smaller devs who do not have as much expertise or numbers. They may be more comfortable with the old way of doing things where the driver does the heavy lifting.

 

ps- it will be also interesting to see how the technically incompetent devs like ubisoft adapt to direct X 12 and Vulkan and try to make a stutter free game? No more relying on driver teams from Nvidia and AMD to fix your shit. Application control; the way it should be.

 

Actually most devs with their own engine, tends to use DX9. Just look at Rocket League. Or they simply go with OpenGL for their pixel art games.

 

DX11 will not die anytime soon, but I think most of them will either ship with or get an update for DX12. I assume the vast majority of AAA games in 2016 will support DX12.