• 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.

Harlequin said:
DX12 is coded for the game not for the gpu - so whth it working on Xbone and later direct2metal on PS4 (with similar features as xbox) there is 0 reason to not have the option from day 1. look at ashes - turn off async and run the DX11 code path.

but they didn't and they removed it entirely AND they have added to the pc version , Nv only options.

a dev doesn't do anything without funding - and the company funding them , depending on the size of the pay , asks for and get the options they want.


same in retail - those promo`s? they are all paid for by the companies doing them
Click to expand...

I completely understand what you mean. But we have absolutely no idea of which condition their dx12 renderer was during release. Now that they only use dx11 path, it's natural async ain't in the game. DX12 is so new api that there is bound to have many problems implementing it to work flawlessy. The fact that XB-One has it, doesn't mean it works flawlessy on all pc hardware.
 
Harlequin said:
DX12 is coded for the game not for the gpu - so whth it working on Xbone and later direct2metal on PS4 (with similar features as xbox) there is 0 reason to not have the option from day 1. look at ashes - turn off async and run the DX11 code path.

but they didn't and they removed it entirely AND they have added to the pc version , Nv only options.

a dev doesn't do anything without funding - and the company funding them , depending on the size of the pay , asks for and get the options they want.


same in retail - those promo`s? they are all paid for by the companies doing them
Click to expand...

There is far more to it like I said. You can't just pop on DX12 for the PC and be done with it, it doesn't work like that. Look at Mantle as an example. It would release with a game and have many issues on a 7970 but run well on a 290 or vice versa.

What NVidia only options are in Rise of the Tomb Raider?

If you want to believe NVidia paid off the devs to remove DX12, knock yourself out. To me there is far more to it than you think but hey, your opinion is valid.
 
Its HBAO+ - nv only and it got an upgrade in the last patch;

I disagree about DX12 - If the game engine is coded for DX12 - then is down to the IHV`s to have supporting drivers , as DX12 is direct 2 metal. write a game that works properly and it works; one reason why porting games between xbox and pc should be a lot easier ; but riddle me this - why does AMD drivers work in DX12 and Nv ones don't work well (and still no Fermi ones !!)
 
Harlequin said:
Its HBAO+ - nv only and it got an upgrade in the last patch;

I disagree about DX12 - If the game engine is coded for DX12 - then is down to the IHV`s to have supporting drivers , as DX12 is direct 2 metal. write a game that works properly and it works; one reason why porting games between xbox and pc should be a lot easier ; but riddle me this - why does AMD drivers work in DX12 and Nv ones don't work well (and still no Fermi ones !!)
Click to expand...

Ermmm HBAO+ works just fine on AMD and what games don't work well on NVidia with DX12?
 
Harlequin said:
Its HBAO+ - nv only and it got an upgrade in the last patch;

I disagree about DX12 - If the game engine is coded for DX12 - then is down to the IHV`s to have supporting drivers , as DX12 is direct 2 metal. write a game that works properly and it works; one reason why porting games between xbox and pc should be a lot easier ; but riddle me this - why does AMD drivers work in DX12 and Nv ones don't work well (and still no Fermi ones !!)
Click to expand...

HBAO+ works on AMD the tech that Nvidia is adding into Tomb Raider isnt in the game yet.
 
I don't find it hard to believe at all, in actual fact, you would be silly to be so against the possibility of that being the case.... Companies are dirty when it comes to competition and at the end of the day, they will do whatever it takes to make their products look the better product as their profit relies on a good public image especially on day 1 releases.

Heck remember the time, Samsung were found to be paying people to go and slate HTC's products on forums and praise their own items etc.

http://www.theverge.com/2013/10/24/5023658/samsung-fined-340000-for-posting-negative-htc-reviews

Assuming that if ROTTR had full dx 12 and AMD had a significant lead, it wouldn't really look very good for a nvidia sponsored game with gameworks, would it?

As for DX 12 being hard to code, wasn't the whole point of it being made, to give the developers more control and making it easier for them to work with, seems odd to have a new API that will make their job even harder and take them longer to work with....

There is no doubt that nvidia paid them for the game sponsorship though, there is no way SE would give away thousands, if not more free copies of their game with nothing to show for in return.... especially when it sounds like they needed the money as without the microsoft timed exclusive deal, the game would have never happened "supposedly"....

This is how things work in the marketing/advertising/PR world, it is no different to companies paying newspapers, TV networks to show their product ads or getting an ad slot in some football stadium for a big match.

Same goes for AMD sponsored games.

If it has a sponsor logo at the beginning or/and been bundled with a product, it is safe to say that money has been exchanged. Money talks at the end of the day.


I don't see why a dx 12 option couldn't have been included in the game to start with, if it has bugs then simply switch back to the dx 11 api, like what AMD users could do with mantle games, didn't play nice, go to dx 11. Also surely would this not be better way of doing it, allow people to test it with various combinations of hardware and report back with their crash logs etc. and this would help the developers improve the dx 12 version even quicker and nail the bugs more precisely.
 
Last edited:
Harlequin said:
Its HBAO+ - nv only and it got an upgrade in the last patch;

I disagree about DX12 - If the game engine is coded for DX12 - then is down to the IHV`s to have supporting drivers , as DX12 is direct 2 metal. write a game that works properly and it works; one reason why porting games between xbox and pc should be a lot easier ; but riddle me this - why does AMD drivers work in DX12 and Nv ones don't work well (and still no Fermi ones !!)
Click to expand...

Shader code can work well on one vendors hardware but not another's. This was no different in DX11. The difference now is that AMD and Nvidia cannot substitute this code with better code in the driver. NVIDIA was more likely to do this while AMD would work with the dev and modify the code in source.

With DX12 the driver is a thin abstraction layer. It should do nothing but convert api call to hardware calls and back. In other words, the shader code can still be bad but only the AMD source change method will work with DX12.

And code can still be made to work well on both, even if it does not bring out best on any vendors hardware.
 
Thunnylaf said:
Apparently, async isn't enabled in the latest drivers.

"Update 02/24: NVIDIA sent a note over this afternoon letting us know that asynchornous shading is not enabled in their current drivers, hence the performance we are seeing here. Unfortunately they are not providing an ETA for when this feature will be enabled."
http://www.anandtech.com/show/10067/ashes-of-the-singularity-revisited-beta/6
Click to expand...

Didn't we hear the same thing last year when initial AoS benchmark was released??? nVidia promised to sort it out. Now so many months later, they issue another statement that async is not enabled. Why can't they just stop this bull**** and admit that maxwell does not have hardware async implemented. Surely wonderful nvidia software engineers would have already sorted driver issues in such long time? Last I checked AMD driver team is clueless here, not nvidia...
 
Hey look guys, as a lot of people have said in past threads AMD designed their cards to work in a certain way. It just so happens that DX12 and Vulkan etc.. are designed to work in that way too. So obviously and logically this should pan out that the AMD cards should get performance gains if any new games come out written for DX12 etc...

Nvidia's cards were designed to get the best out of DX11 and single queue processing and still are the best DX11 cards in the highest tier. But the times they are a changing and it looks like AMD who seem to have gambled on DX12 and low level API's will have their moment in the sun....at least for a little while....which is nice.

However, if Pascal doesnt have any hardware solution in place for Async Shaders then I think AMD might just claw a bit of that consumer market back in the next round. Which will be good for everyone. :) Personally I think this is fantastic news as I put my money where my mouth was and bought a Fury Tri-X which will hopefully keep me going for a while yet. :D
 
Last edited:
maonayze said:
Nvidia's cards were designed to get the best out of DX11 and single queue processing and still are the best DX11 cards in the highest tier. But the times they are a changing and it looks like AMD who seem to have gambled on DX12 and low level API's will have their moment in the sun....at least for a little while....which is nice.
Click to expand...

This is a good point, the Kepler cards which have hardware scheduling see performance improvements in DX12, was shown on anandtech. The main problem is that Maxwell was cut down to bare bones for graphics processing which is why it is such a good over clocker and the main reason for its power savings.
 
Last edited:
eddyr said:
Whoa, chill buddy.


Shouldn't Finland be pretty cold this time of year :D
Click to expand...

Nothing wrong in exploring and trying to point out faults and image quality differencies. But details need to be right, especially game version and settings. This thing has been spreading for quite awhile now, and you see that video link posted on multiple forums. Even it's not valid proof.

I'm not saying there isn't differencies, but we need reliable source before we can even have a real discussion.

And about Finland, it's so cold that I have to heat up my Fury X before starting my computer since water is frozen. Nah not really, it's not cold here now, just very snowy.
 
muziqaz said:
Didn't we hear the same thing last year when initial AoS benchmark was released??? nVidia promised to sort it out. Now so many months later, they issue another statement that async is not enabled. Why can't they just stop this bull**** and admit that maxwell does not have hardware async implemented. Surely wonderful nvidia software engineers would have already sorted driver issues in such long time? Last I checked AMD driver team is clueless here, not nvidia...
Click to expand...

Maybe they have more pressing things to do than sort out drivers for a beta benchmark ?
 
You must log in or register to reply here.
Back
Top Bottom