Oxide Games Dev和AMD有合作關係，因此AMD特別挑了DX12中NV卡硬
體層面沒有實際支援的Async Compute來突顯GCN的長處，並歡迎NV與Oxide
接觸，以修正原本不利於MAXWELL的程式碼，個人是感覺笑裡藏刀，反正顯
卡廠和遊戲商合作，說不搞鬼是幾乎不可能的，但有時也能反應一些事實，畢竟
AMD用的也是DX12規範的功能，只是看準對手弱點進行猛攻...



http://www.techpowerup.com/215663/l...directx-12.html
http://www.guru3d.com/news-story/nv...n-settings.html

"Personally, I think one could just as easily make the claim that we were biased toward NVIDIA as the only "vendor" specific-code is for NVIDIA where we had to shutdown async compute. By vendor specific, I mean a case where we look at the Vendor ID and make changes to our rendering path. Curiously, their driver reported this feature was functional but attempting to use it was an unmitigated disaster in terms of performance and conformance so we shut it down on their hardware. As far as I know, Maxwell doesn't really have Async Compute so I don't know why their driver was trying to expose that. The only other thing that is different between them is that NVIDIA does fall into Tier 2 class binding hardware instead of Tier 3 like AMD which requires a little bit more CPU overhead in D3D12, but I don't think it ended up being very significant. This isn't a vendor specific path, as it's responding to capabilities the driver reports," writes Oxide, in a statement disputing NVIDIA's "misinformation" about the "Ashes of Singularity" benchmark in its press communications (presumably to VGA reviewers).

Oxide某開發人員的說法，NV的驅動回應報告說支援該功能(Async Compute)，
因此設計人員便將該功能打開，結果就一整個悲劇。最後NV也回應MAXWELL
沒有支援該功能之硬體層級(tier 1)，但是也質疑Oxide故意把焦點放在某處，對
於全觀性的DX12並不具備代表性。目前NV和Oxide吵很大，NV強烈要求Oxide
在benchmark將該功能關閉，當然，皮皮的Oxide認為既然是DX12的功能，又
為何要關閉，NV質疑Async Compute用量太多，影響公平性，Oxide則認為他
們只是適量使用而已，並沒有突顯之意~~






下個可能出現的DX12 BENCHMARK
http://www.geforce.com/whats-new/ar...e-game-features

這套遊戲的DX12 PATCH原本要出了，小弟從8/28就留意，不過到今天好像還
沒出，就是ARK：Survival Evolved，據聞DX12可增加20%效能。
這個遊戲使用了GAMEWORKS，和NV有合作關係，小弟認為NV應該會在此
GAME中吐露一下他們的怨氣，不過原本上週五要出的DX12 PATCH到現在還
沒出，也難免令人有些遐想。如果要看AMD和NV在DX12的表現，在目前遊
戲都被雙方挾持的情況下，恐怕還是井裡窺天，客觀的結果恐怕要等明年才能知
曉...