QUOTE(Demonic Wrath @ Sep 1 2015, 08:41 PM)
Funny how NVIDIA actually losses performance when going for DX12 API at Ashes of Singularity benchmark.. maybe they optimized their DX11 drivers too well?
Support async or not, what's important is the actual FPS of the game.. if anyone is quoting Ashes of Singularity benchmark saying AMD has better implementation, check again.. R9 390X is also performing close to R9 Fury too. (source: http://www.pcgameshardware.de/Ashes-of-the...tX-11-1167997/) It is just that AMD DX11 implementation is so bad that it makes DX12 looks very good.
One thing we know for sure, currently NVIDIA has the market share (82%!). Who knows what will happen to future DX12 games, especially those GameWorks titles.
yeah funny indeed... but NVIDIA is telling/pressure Oxide to disable async compute/shader feature on the bench. Support async or not, what's important is the actual FPS of the game.. if anyone is quoting Ashes of Singularity benchmark saying AMD has better implementation, check again.. R9 390X is also performing close to R9 Fury too. (source: http://www.pcgameshardware.de/Ashes-of-the...tX-11-1167997/) It is just that AMD DX11 implementation is so bad that it makes DX12 looks very good.
One thing we know for sure, currently NVIDIA has the market share (82%!). Who knows what will happen to future DX12 games, especially those GameWorks titles.
" The rather startling news is that Nvidia's Maxwell architecture, and yeah that would be the entire 900 range does not support it in the way AMD does. I can think of numerous scenarios as to where asynchronous shaders would help."
http://www.guru3d.com/news-story/nvidia-wa...n-settings.html
add-on: oh bro your signature correction on "MSI NVIDIA GeForce GTX970 Gaming 4GB GDDR5" is 3.5GB GDDR5
This post has been edited by Unseen83: Sep 1 2015, 10:20 PM
Sep 1 2015, 10:18 PM

Quote

0.0215sec
0.70
6 queries
GZIP Disabled