• Competitor rules

    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.

Ashes of the Singularity Coming, with DX12 Benchmark in thread.

The numbers are all over the palc,e so indeed on same websites, some combos of settings, CPU and GPU make some sense, but other combos and websites ther is completely wrong scaling.

Then when you say things likes Nvidia dx12 drivers are poorly optimized that is disproven by other results. E.g. The 770 in a CPU bound setting got a 180% boost going from DX11 to Dx12, but the 980ti lost something like 5%. DX12 should have the biggest positive impact on a combo that is CPU limited and has mountains of additional GPU resources untapped, low end GPUs should see minimal irmpovements, yet he result are the exact oposite because quite frankly, the game engine is completely flawed and no meaningful conclusions can be drawn from it.
Its the same story with DX11 in pretty much anything Kepler vs Maxwell.

For whatever reason, be it Drivers or Something in the Hardware Kepler does not pull as many Draw Calls as Maxwell.
 
Last edited:
and possibly affect any DirectX 12 game/benchmark

Yeah it didn't make much sense Nvidia pointing the finger of blame at Oxide, MSAA is part of DX11/12, it has nothing to do with the engine code.
Nvidia should know this.
 
Last edited:
The irony at least for me is that Ashes is/will be the quintessential DX12 vehicle. You don't need DX12 to see strands of wavy hair on a middle aged swashbuckler, but for the thousands of assets in a large scale rts battle.


Or 900 Thousand strands of Grass, 80 Thousand Tress and Shrubs to make ones world of vegetation looks like something that actually resembles reality.
 
Kaap

There is an option to enable AFR but it does not appear to work as the results were similar to my single gpu scores.

One thing i did notice though, with AFR ticked the cpu load dropped over all threads, even though the FPS remained the same. I made the mistake of running a lower Temporal AA setting from earlier, so that explains the slight difference in FPS from my first results.

All four gpu's showed usage in AB, but this is normal as CrossFire was not physically disabled in CCC.

20ieuqe.jpg
 
The above is a good point about DX11, the 390X is a very good card and often beats out the GTX 980 at high resolutions which begs the question -

If most users who buy the game will still be using DX11 why have the game devs made so little effort to look after them ?

The above also questions how reliable this bench is for DX12 if the devs have given so little thought to DX11 users.

Why would anyone with a DX12 capable card use DX11?

I'm sure there are still some VLM and Fermi GPU's out there in rigs but it can't be many, those cards belong in a museum.
 
Because the majority of windows users won't all be upgrading to Win 10, there will be loads who stay on Win 7 and 8 for reasons of their own.

Point taken and agreed, but really its their loss, Windows 10 with Classic Shell is just like Windows 8.1 with Classic Shell which is a lot like windows 7..... and its free right now.
 
The DX11 performance on the AMD cards in the bench is shocking and nothing to do with the hardware, this is an epic and arrogant fail by the game devs.

I still use 290Xs and I fully expect them to best GTX 980s @2160p using DX11.

Kaap, Mate :) even i accept AMD's DX11 Driver overheads still need work.

i also think AMD have largely ignored their own DX11 optimization for this to put as much resource as they can into getting DX12 Drivers right, which seems to have paid off.... but somewhat compounded the DX11 problem.
 
I wonder how this thread would have gone had Nvidia not made such a public fracas with Oxide Games.

Just looking at the results it looks like a good thing for both and there is no reason why that would have been the conclusion of the debate.

Yup.:D



100% agree with Joel Hruska's conclusion opeth, thanks mate.:)

On another note:

Any mods able to step in here and help put a stop with the hating in here please:



^
This, as greg said, the discussions were better than now, because you can't have a discussion any more, only fights n snipes@OcUK.:o

Iv'e not been posting in here much due to the relentless arguments, please sort it out, this used to be a great place to come:( and we really need it back.:)

The 3 strike rule launched, and it was great, everyone got on and it was good again, is it still enforced, or could you re-instate it again???

+1 ^^^^
 
Last edited:
They didn't make a fracas and most of the talk has come from here and accusing Nvidia of this and that. I read through this thread again earlier to see if I was right to get annoyed and my annoyance was nothing to do with the thread or Nvidia or AMD but the way some people are over reacting and frankly quite personal in their responses. I did some quick looking when I got in from work last night and Oxide Games is made up of some knowledgeable people from the industry and they are sided with AMD but that doesn't make them wrong. They and AMD have done well on their DX12 implementation and Nvidia do need to do some work on their DX12 in this but neither is doing badly, so I don't get why all the fuss?

This whole debate, including you is about Nvidia accusing Oxide Games of having Code issues that put Nvidia at a disadvantage.

Now personally i don't see any disadvantage for Nvidia in this, AMD are a little ahead in DX12 efficiency but not much at all and they have that same little advantage in FutureMark's API overhead.

As for the apparent MSAA bug, that was Nvidia's Driver.

All of that has sparked arguments in this thread, you were also involved, Greg.

If you just look at the results without Nvidia's whinging they look like a good thing for both Nvidia and AMD.
That ultimately is what they are.
 
You have failed to read my post Humbug. My annoyance is with the way people are treating each other and dumbass remarks like Fanboy etc. I used to enjoy a good debate and me and you have been involved in many but some of the comments in here are pathetic and in the olden days, me and you would have seen a 3 month suspension if we said those things.

That is my point and the reason I got annoyed.

I'm not quite that far in the crap as to get a 3 Month suspension, i have had 1 strike but i take your point, Moderating seems very inconsistent in here, its why i +1 Tommy.
 
Nope: You must be reading the wrong numbers:

GTX 960 DX11: 32.4FPS
GTX 770 DX11: 32.8 FPS
FuryX DX11: 30.6 FPS



So in which current games does a 960 and 770 beat a FuryX and a TitanX?

Do you understand Draw Calls? it really doesn't look like you do, if you did you would understand why this happened, a little phenomena called "CPU Bound"

why are you clutching at this so hard? its insane.
 
Last edited:
I keep saying there is nothing in this that looks in anyway bad for Nvidia.

Would we be having these ridiculous arguments had Nvidia just not said anything? its like some mad merry-go-round to justify Nvidia's moaning.
 
2% margins Kaap, there is no reason as to why the 980TI should fall further behind with Nvidia's DX11 Drivers..

@ D.P

Do you understand Draw Calls? it really doesn't look like you do, if you did you would understand why this happened, a little phenomena called "CPU Bound"

why are you clutching at this so hard? its insane.

Now i know you do, you are one of the few people on here who understand whats going on at the back end of these things, so when you see something like that it should be immediately obvious to you what is going on, why you opt to pretend you don't understand it and have half the forum explain it to you is beyond me.

This thread is bonkers. like a lot of threads around here of late.
 
Last edited:
Back
Top Bottom