• We've upgraded our forums. Please post any issues/requests in this thread.

AMD Demonstrates Full Support for DirectX 12 at Game Developer Conference

Joined
Jul 24, 2013
Messages
138 (0.09/day)
Likes
15
Processor Intel i7 4770K
Motherboard Asus Maximus VI Extreme
Cooling Custom water loop
Memory G.Skill Sniper Series 32GB (4 x 8GB) DDR3-2400 Memory
Video Card(s) 4x SAPPHIRE 100362BF4SR Radeon R9 290 unlocked to 290X
Storage 2x Samsung 840 EVO 250GB in raid0, 2x TOSHIBA PH3300U-1I72 3TB
Display(s) 3x Asus VS238H-P 23.0"
Case Corsair 900D
Power Supply ENERMAX Maxrevo EMR1500EWT 1500W
Software Microsoft Windows 8.1 Professional (64-bit)
#51
Joined
Nov 3, 2011
Messages
192 (0.09/day)
Likes
30
System Name InWin 503 |Fractal R5 | Samsung ATIV Book 8
Processor Intel Core i7-4790K 4.6 Ghz | Intel Core i7-7820X 4.5 Ghz | Intel Core i7-3635 QM
Motherboard ASUS Z87 Gryphon | MSI X299 Gaming Pro Carbon AC | Samsung ATIV Book 8
Memory 16GB 2400 Mhz | 32GB 3200Mhz | 16 GB 1600Mhz
Video Card(s) MSI Gaming X Geforce 980 Ti OC | MSI Geforce 1080 Ti FE | AMD Radeon HD R9-M270@850 Mhz
Display(s) 3X Samsung 23in LED | Samsung 27in 4K | built-in Samsung 15 inch LED touch screen.
Case InWin 503 | Fractal R5 | Samsung ATIV Book 8 (15 inch)
Audio Device(s) ASUS Xonar D2X | Creative Sound Blaster Z| built-in
Power Supply Cooler Master 750 watts | Seasonic 750 watts | 90 watts
Software All machines has MS Windows 10 Pro 1709 version.
#52
A repeat of Techreport''s article

From Techreport. http://techreport.com/news/26210/directx-12-will-also-add-new-features-for-next-gen-gpus

"However, Tamasi explained that DirectX 12 will introduce a set of new features in addition to the lower-level abstraction, and those features will require new hardware."

Mr Tamasi is from NVIDIA and doesn't have the authority for non-NVIDIA hardware.

Techreport's "new blend modes" and something called "conservative rasterization" refers to DirectX12's new rendering modes.

1. "Programmable blend and efficient OIT with pixel ordered UAV".

2. "Better collision and culling with Conservative Rasterization".


If you compare point 1 with http://software.intel.com/en-us/blo...ency-approximation-with-pixel-synchronization


The API is based on Intel's Pixel Sync. The main feature with this Intel API is the pixel shader wait function. This avoids the "link list" requirements since the pipelines are handling the pixel shader read/manage/write order.


Again, NVIDIA's Mr Tamasi DOES NOT have any authority for non-NVIDIA hardware.


For reference

DirectX11's Link List based OIT from http://www.docstoc.com/docs/106125562/Order-Independent-Transparency-Using-DirectX-11-Linked-Lists

OpenGL 4.0+'s Link List based OIT from http://blog.icare3d.org/2010/07/opengl-40-abuffer-v20-linked-lists-of.html



-----------------

From http://www.amd.com/us/press-releases/Pages/amd-demonstrates-2014mar20.aspx

"Full DirectX 12 compatibility promised for the award-winning Graphics Core Next architecture"


AMD claims "FULL DirectX 12 compatibility".
 

g101

New Member
Joined
Oct 27, 2013
Messages
2 (0.00/day)
Likes
0
#53
A repeat of Techreport''s article

From Techreport. http://techreport.com/news/26210/directx-12-will-also-add-new-features-for-next-gen-gpus

"However, Tamasi explained that DirectX 12 will introduce a set of new features in addition to the lower-level abstraction, and those features will require new hardware."

Mr Tamasi is from NVIDIA and doesn't have the authority for non-NVIDIA hardware.

Techreport's "new blend modes" and something called "conservative rasterization" refers to DirectX12's new rendering modes.

1. "Programmable blend and efficient OIT with pixel ordered UAV".

2. "Better collision and culling with Conservative Rasterization".


If you compare point 1 with http://software.intel.com/en-us/blo...ency-approximation-with-pixel-synchronization


The API is based on Intel's Pixel Sync. The main feature with this Intel API is the pixel shader wait function. This avoids the "link list" requirements since the pipelines are handling the pixel shader read/manage/write order.


Again, NVIDIA's Mr Tamasi DOES NOT have any authority for non-NVIDIA hardware.


For reference

DirectX11's Link List based OIT from http://www.docstoc.com/docs/106125562/Order-Independent-Transparency-Using-DirectX-11-Linked-Lists

OpenGL 4.0+'s Link List based OIT from http://blog.icare3d.org/2010/07/opengl-40-abuffer-v20-linked-lists-of.html



-----------------

From http://www.amd.com/us/press-releases/Pages/amd-demonstrates-2014mar20.aspx

"Full DirectX 12 compatibility promised for the award-winning Graphics Core Next architecture"

AMD claims "FULL DirectX 12 compatibility".

Thank you, I really get tired of the completely uninformed 'enthusiast' children attempting to poke holes in concepts they cannot even begin to grasp.

Now I will be repeating and extending some of what rvalencia has already said below. Since it appears some of you have absolutely terrible reading comprehension, maybe a few different formats of the same information will finally make the facts about dx12 sink in. Funny how people that actually have some idea of the subjects they talk about tend to draw the same conclusions, isn't it?

So yeah, NVidia's fancy 'better than mantle' driver? Complete nonsense, they are using a worst case scenario for mantle (no cpu bottleneck), using FALSE metrics for both dx and mantle for the AMD hardware metrics (do your own research, kids) and also not achieving comparable minimums by their *own* admission. Of course, they haven't included the most relevant metric (minimum fps) in their chart, they only verbally mentioned their failure to compete and their plans to 'whittle away at it'. Yeah, right. They gained less than 5 fps, a smaller gain than most dx titles see with driver-specific optimization and they couldn't even solve the stalls so commonly found with dx, even with just this *one* title.

Let's see crossfire mantle vs. sli dx 'magic driver' on that same hexacore testbed, novidia. Pretending that minimum fps isn't the most important metric is laughably transparent.


Again, NVidia will NOT be providing full dx12 support with kepler or anything before it. The fact that any of you believe what NVidia says when it comes to dx specifications (or any other API for that matter) is hilarious.

How quickly you forget NVidia 'dx 11.1* support'.

Have fun buying new hardware and also waiting until 2016 for *virtualized* 'unified memory'. Hilarious.



Little kids with zero education in semiconductors really have no business calling Charlie Demerjian 'chuckles'.
 
Last edited:

savage.r

New Member
Joined
Apr 4, 2014
Messages
1 (0.00/day)
Likes
0
#54
The only reason why microsoft brought DX12 is AMD's Mantle.

And since mantle/DX12 is mainly about multi-core CPU optimization, nvidia couldn't care less, since they just do not make any.
For same reason they still use unoptimized physX 2.8.x in ALL of their supported games.

But though nvidia always talking funny bullshit, they have brilliant marketing dept. for that, the most ridiculous in that INTEL "happily" supported DX12 too.

Intel, since it is literally the monopoly on PC market, is the last one who needs anything removing CPU overhead.
Because then AMD CPUs equal intel's from gaming performance point.
There is actual reason why intel make 4core CPUs for 7 years now, although they know the only way to keep performance gain is bring more CPU cores on.

But it is always nice to hear how many years they have been hardly working on that, wonder how long microsoft worked on low level API for their console. It is fucked up all those companies care about profit and they take PC platform for granted :/