It's the game, not the driver, IIRC. NV's drivers have had async compute for a few months now, I believe. It's the games that need to turn it on.
Why doesn't it turn on for NV cards to begin with? I though Nvidia always have game ready driver on time?
You didn't answer my question, nVidia always has game ready drivers on launch or on major patches. nVidia had faster driver support for DOOM btw, then why not now. Why nVidia still haven't had Async Compute?
I read around a lot and I cannot find a SINGLE statement from nVidia regarding the matter. Peterson didn't even comment on this matter. It seems to me nVidia's trying to avoid the matter.
Note that iD Software didn't even mention Maxwell at all, na dah, zero. Where's Async Compute Game Ready Driver that Nvidia promised.
Don't you find it weird that a company has a history of putting out drivers precisely on time, has failed to deliver Game Ready driver with Async Compute ready AND enabled in games, in every single game with Async Comoute so far?
I sell computers as a side hobby. About 5 hours from now, a buyer will come and pick up a 960 system. What am I going to say if he asks about the new Doom? I want massive boost AS PROMISED by nVidia. But no. That PC is dead upon arrival. And I have to sell it.
And that's bullshit on nVidia's part.
Edit: What the fuck is this: https://twitter.com/PellyNV/status/752889939730149376 Is he basically saying there won't be any more improvements?
Edit: What the fuck is this: https://twitter.com/PellyNV/status/752889939730149376 Is he basically saying there won't be any more improvements?
You didn't answer my question, nVidia always has game ready drivers on launch or on major patches. nVidia had faster driver support for DOOM btw, then why not now. Why nVidia still haven't had Async Compute?
I read around a lot and I cannot find a SINGLE statement from nVidia regarding the matter. Peterson didn't even comment on this matter. It seems to me nVidia's trying to avoid the matter.
Note that iD Software didn't even mention Maxwell at all, na dah, zero. Where's Async Compute Game Ready Driver that Nvidia promised.
Don't you find it weird that a company has a history of putting out drivers precisely on time, has failed to deliver Game Ready driver with Async Compute ready AND enabled in games, in every single game with Async Comoute so far?
I sell computers as a side hobby. About 5 hours from now, a buyer will come and pick up a 960 system. What am I going to say if he asks about the new Doom? I want massive boost AS PROMISED by nVidia. But no. That PC is dead upon arrival. And I have to sell it.
And that's bullshit on nVidia's part.
Edit: What the fuck is this: https://twitter.com/PellyNV/status/752889939730149376 Is he basically saying there won't be any more improvements?
It's the game, not the driver, IIRC. NV's drivers have had async compute for a few months now, I believe. It's the games that need to turn it on.
Async Compute is NOT enabled on the driver-side
No its quite clear, Async is turned on in the games, but not enabled in the drivers (because support does not exist?)
http://twitter.com/PellyNV/status/702556025816125440
That was February, though?
Why doesn't it turn on for NV cards to begin with? I though Nvidia always have game ready driver on time?
The question is, why Async Compute is not turned on for Nvidia in Doom, even though they always deliver driver on time. Assuming Nvidia driver has Async Compute, which I do not know.
No one question Nvidia's support for Vulkan, it's all about Async Compute.
And they've never made a statement saying they have been enabled, and as we've seen from ashes, no improvements for Maxwell at all so they can't be enabled yet driver side.
So it's very possible that Nvidia doesn't have anything to improve on.
Well, we'd expect to see some tangible gains with async compute active, and we don't.
It's pretty hard to believe a zero gain with async compute, so I'm going to have to say it must not be working, for whatever reason.
And we know that Pascal does have the capability.
Logically it falls to drivers or apps.
What surprises me is the lack of an AMD ad campaign on the issue? I'd be pushing hard on it if I were AMD.
Well, we'd expect to see some tangible gains with async compute active, and we don't.
It's pretty hard to believe a zero gain with async compute, so I'm going to have to say it must not be working, for whatever reason.
And we know that Pascal does have the capability.
Logically it falls to drivers or apps.
What surprises me is the lack of an AMD ad campaign on the issue? I'd be pushing hard on it if I were AMD.
It's not up to NVIDIA. With these low level APIs, the work is pushed onto the developer to enable a feature/take advantage of particular features in the architecture.
It's clear from all of the PR around Vulkan for Doom coming from AMD that AMD worked closely with id on the GCN codepath using the Vulkan API.
If NVIDIA wants a speedup on Vulkan for Pascal, they're going to have to work closely with id to do a separate codepath that plays to the strengths of the Pascal architecture.
They are pushing it hard, see Twitter. Also, in the Bethesda PR for this patch, there is a link to an AMD Youtube video explaining Async Compute.
AMD's fingers are all over this, good marketing move from them.
How do we know that Async compute does work on Pascal? When Nvidia tried to show it off they used a DX11 test (fraps overlay running)
Adds utilization of DirectX 12 Asynchronous Compute, on AMD GCN 1.1 GPUs and NVIDIA Pascal-based GPUs, for improved GPU performance.
was that why performance was lowered across the board for that game?Well, ROTR game developers wrote an update for it.
Seems odd to write an update for something that doesn't exist or work?
https://steamcommunity.com/app/391220/discussions/0/358417008720278827/
Well it is to an extent as you say here:It's not up to NVIDIA.
I find it hard to believe that AMD worked closely with ID and Nvidia just stood around doing nothing. Something is missing here...If NVIDIA wants a speedup on Vulkan for Pascal, they're going to have to work closely with id to do a separate codepath that plays to the strengths of the Pascal architecture.
Are you saying ALL devs with games that have Async Compute just out right REFUSE to turn on Async Compute for nVidia? it's been 10 months since the first AotS was released. Are you saying Oxide refused to work with nVidia on Async Compute?
If not, there must be a hint, a suggestion from the devs and nVidia themselves to clear out the myst. There has been none so far.
What do you make of this?
Why wouldn't they? AMD cards got yuge performance increase, better min FPS, better CPU ultilization etc. As PROMISED.
What did nVidia say about Vulkan? What promises did they delivered? How about some honesty folks?
It's not up to NVIDIA. With these low level APIs, the work is pushed onto the developer to enable a feature/take advantage of particular features in the architecture.
It's clear from all of the PR around Vulkan for Doom coming from AMD that AMD worked closely with id on the GCN codepath using the Vulkan API.
If NVIDIA wants a speedup on Vulkan for Pascal, they're going to have to work closely with id to do a separate codepath that plays to the strengths of the Pascal architecture.
D3D12_COMMAND_LIST_TYPE_COMPUTE
or
D3D12_COMMAND_LIST_TYPE_DIRECTif (AsynchronousComputeEnabled)
{
D3D12_COMMAND_QUEUE_DESC queueDesc = { D3D12_COMMAND_LIST_TYPE_COMPUTE, 0, D3D12_COMMAND_QUEUE_FLAG_NONE };
ThrowIfFailed (m_device->CreateCommandQueue (&queueDesc, IID_PPV_ARGS (&m_computeCommandQueue)));
NAME_D3D12_OBJECT (m_computeCommandQueue);
RenderStuff(D3D12_COMMAND_LIST_TYPE_COMPUTE);
}
else
{
RenderStuff(D3D12_COMMAND_LIST_TYPE_DIRECT);
}