Soldato
Lols.
Good find Neil.
Just like the gpu vendors-fact or economical with the truth?
Good find Neil.
Just like the gpu vendors-fact or economical with the truth?
Last edited:
Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.
all we know right now is with proper DX12 AMD's old generation makes Nvidia latest and greatest tremble.
You seem more like a walking evangelical Nvidia commercial telling us to worship the Nvidia faith. "Oh lord praise the NVIDIA, i say PRAISE THE NVIDIA"
Vega maybe crap or it may utterly kill the 1080TI, all we know right now is with proper DX12 AMD's old generation makes Nvidia latest and greatest tremble.
Under the hood, the engine only makes use of FL 11_0 features, which means it can run on video cards as far back as GeForce GTX 680 and Radeon HD 7970. At the same time it doesn't use any of the features from the newer feature levels, so while it ensures a consistent test between all cards, it doesn't push the very newest graphics features such as conservative rasterization.
That said, Futuremark has definitely set out to make full use of FL 11_0. Futuremark has published an excellent technical guide for the benchmark, which should go live at the same time as this article, so I won't recap it verbatim. But in brief, everything from asynchronous compute to resource heaps get used. In the case of async compute, Futuremark is using it to overlap rendering passes, though they do note that "the asynchronous compute workload per frame varies between 10-20%." On the work submission front, they're making full use of multi-threaded command queue submission, noting that every logical core in a system is used to submit work.
3DMark Time Spy engine is specifically written to be a neutral, "reference implementation" engine for DX12 FL11_0.
Average consumers take it REALLY badly if a new benchmark says "you can't run it on your brand new (well, 3 year old) system because of X". This also directed to supporting FL11. On CPU test we took a "bold step" of requiring SSSE3 and.. uuh.. I've apologized today already to four customers that no, their Phenom II or Opteron can't run the test.*
A FL12 benchmark with fallbacks to FL11 would not really be feasible - it would basically be two separate benchmarks. FL12 adds some interesting features and fully exploiting those would take a dedicated approach.
Pretty much all games target DX12 FL11 and even there most current game engines are doing DX12 in a way that is "oh we just ported our DX11 code". Time Spy is at least taking one step further with an engine developed from the ground up 'the DX12 way' (which is one of the reasons why it took a while - oh the tales our engine team could tell of DX12 features where spec says one thing and driver implementations do... other things. A phrase "What? Nobody is doing it like this" is something that was told to us by driver developers more than once...). ( Yeah probably NVIDIA as the FM devs have stated NVIDIA drivers purposely disable anything related to Preemption, or Async Compute on Maxwell; despite NVIDIA claiming several times it is supported.)
So I'd say Time Spy is a legit tool that will reflect how games could perform when a pure DX12 engine targets the most widely used hardware base (ie, DX12 FL11).
It is actually somewhat similar to how 3DMark 11 vs. 3DMark Fire Strike tested DX11. You could say that Time Spy is the "3DMark 11" or "Sky Diver" for DX12. Doesn't try to use every possible feature, aims to measure the common use case. Fire Strike went way further with DX11 and is still probably more complex/advanced than just about any DX11 game out there.
Yup, here's the FM dev himself saying that. Also the whole point of DX12 being so low level is to allow for separate code paths which are Needed to get the best out of the hardware, but instead FutureMark opted for a "neutral" path.
http://forums.anandtech.com/showpost.php?p=38363396&postcount=82
Also the following.
http://forums.anandtech.com/showthread.php?t=2480259&page=2
1070 and 1080 are still ahead in every DX12 game.
All I can say is that is one of the most amateurish PowerPoint slides I have ever seen.
This thread is fanboi gold, everyone is an instant API expert
Not by a massive amount though, and they cost twice as much.
Not by a massive amount though, and they cost twice as much.
Not by a massive amount though, and they cost twice as much.
Your own Guru3D slides back there contradict this statement, lol...As has always been the case in the gpu world. You want the best, you want that extra 20-25% over a Fury X? Then you pay for it.
I don't really understand the furore over this Timespy DX12 thing. It seems to give similar results to other DX12 titles in terms of where the cards sit in the pecking order.
I'm not sure what people were expecting
Your own Guru3D slides back there contradict this statement, lol...
How?
https://forums.overclockers.co.uk/showthread.php?t=18740536
1080's at the top. overclocked 1070's and 980Tis next, then Fury X's (as they don't overclock for a toffee), then 290p,390p and 290x's beating 970's and 980's.
Look at the 390X score in the Guru3D slide, in it its beating the 980TI while in Time Spy its way behind.
What in Hitman?
You can't just judge it one game. Better to look at the bigger picture.
Also, our own thread here has loads of very heavily overclocked 980Ti's which skew things somewhat
http://www.guru3d.com/articles-pages/futuremark-3dmark-timespy-benchmark-review,1.html
^ Those are stock scores and the 390x is pretty close to the 980Ti - in fact getting pretty much the same score ( or at least very close) as the Fury's so very much like Hitman in that regard...http://www.guru3d.com/articles_pages/amd_radeon_r9_rx_480_8gb_review,11.html - just like in Timespy, not much between the 390x and the Fury's/nano's
That is a point, why are the 390X, Fury-Nano and Fury-X all within 5% of each other, what is going on there?
I don't know but it seems to be a slight trend in DX12 games/benches so far.
That is a point, why are the 390X, Fury-Nano and Fury-X all within 5% of each other, what is going on there?
Its like A-Sync isn't working at all.
Its absolutely a trend with DX11, the Fury-X tops out with DX11 overheads before it can pull out a lead over the 390X.
Its like DX12 in Time Spy isn't doing anything at all for AMD.