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.
How does the pricing work for this? You pay £40 for one level (with some replay value)? And have to pay for each episode/level that comes out?
How does the pricing work for this? You pay £40 for one level (with some replay value)? And have to pay for each episode/level that comes out?
Computerbase benchmarks
More Async compute in game, you should expect to see it in a lot of DX12 titles going forward.
I would like to see benches like this revisited when Asycn is on in the Nvidia drivers as (my understanding) it is not enabled currently.
A-sync will only become widespread when Nvidia do it proper in Hardware as well, until then, forget it.
I'm not sure you understand the nature of this feature. There are 2 main types of tasks for a GPU, graphics and compute. D3D12 exposes main 2 queue types, a universal queue (compute and graphics), and a compute queue. For Ashes, use of this feature involves taking compute jobs which are already part of the frame and marking them up in a way such that hardware is free to coexecute it with other work. Hopefully, this is a relatively straightfoward tasks. No additional compute tasks were created to exploit async compute. It is merely moving work that already exists so that it can run more optimally. That is, if async compute was not present, the work would be added to the universal queue rather than the compute queue. The work still has to be done, however.
The best way to think about it is that the scene that is rendered remains (virtually) unchanged. In D3D12 the work items are simply arranged and marked in a manner that allows parallel execution. Thus, not using it when you could is seems very close to intentionally sandbagging performance.
I would like to see benches like this revisited when Asycn is on in the Nvidia drivers as (my understanding) it is not enabled currently.
So you get interested and finish that part of the game and you have to wait 1 week to 3 months to carry on your game?
Just NO! Dx12 or not that's just ridiculous.
I laughed when one of the nvidia reps tweeted that nvidia not enabling the a-sync shaders yet is a FUN fact. It is a sad fact: for one if a-sync are functional on nvidia and nvidia is holding it away from their customers, and second - if it is not functional, but they are lying about it to their customers that they are functional. And 3rd, that fun fact is still happening since Ashes initial Alpha release, where they said they are preparing the driver fix for async.