They havent worked with nVidia. id just sold out. What a great gift to the nVidia customers who have bought the game in the last two months. :thumbsdown:
Doom is my last game from id. :thumbsup:
it looks like id is still working with NVIDIA to build a code path for the Pascal GPUs that can take advantage of Pascal's asynchronous compute abilities/architecture.
They havent worked with nVidia. id just sold out. What a great gift to the nVidia customers who have bought the game in the last two months. :thumbsdown:
Doom is my last game from id. :thumbsup:
Be prepared to throw away your Samsung s7 and in one year your pc.They havent worked with nVidia. id just sold out. What a great gift to the nVidia customers who have bought the game in the last two months. :thumbsdown:
Doom is my last game from id.
They havent worked with AMD. Crystal Dynamic just sold out. What a great gift to the AMD customers who have bought the game in the last five months. :thumbsdown:
Rise of the Tomb Raider is my last game from Crystal Dynamic. :thumbsup:
MY GOD.
A synch is absolutely a per architecture feature. Its crazy complex stuff and my guess is the lack of granularity in pascal and lack of consoles support, little market share plus basic unfit arch will be the reason we don't see it in pascal with solid benefit besides from a few marketing cases. Its a Cuda feature. It would be good if some devs like zlatan chimed in here btw.
The only reason async is here is because the devs need to extract so much power of consoles as possible with compute power not available in the cpu. It doesn't come cheap. And there is no incentive to make it for pascal where the benefits would be slimmer.
And remember asynch is just a small part of dx12 mantle Vulcan. There can be many reasons eg the ace why gcn benefits so much.
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);
}They havent worked with AMD. Crystal Dynamic just sold out. What a great gift to the AMD customers who have bought the game in the last five months. :thumbsdown:
Rise of the Tomb Raider is my last game from Crystal Dynamic. :thumbsup:
MY GOD.
They havent worked with nVidia. id just sold out. What a great gift to the nVidia customers who have bought the game in the last two months. :thumbsdown:
Doom is my last game from id. :thumbsup:
Nvidia just had id Software come on stage at their event in Austin, TX to show Doom up and running on the GTX 1080. That may not seem like a big deal, so to kick things up a notch, id had the game running using the Vulkan API. That's the low-level OpenGL equivalent of DirectX 12, and while id didn't specifically say how much faster Vulkan allowed the game to run, they did enable the in-game FPS counter.
No one says Pascal cannot get better. It's a matter of magnitude/scaling. RX 480 shows 40-48% increase in performance, and Fury X even more at 52-66%. The more serial architecture - GCN - has Command Processors and ACE engines designed for high throughout. We have seen enough DX12 benches to see that DX11 never allowed these hardware benefits to come into play based on how the code is issued. The extra hardware in GCN was underutilized because the architecture wasn't made for serial APIs.
If you go way back to 2011 when Eric Demers unveiled GCN, he explained all of this. It's just too bad it took 5 years to see that he was 100% correct. DX11 is simply outdated and hopefully by the time PS5/XB2 come out DX12/Vulkan can put DX11/OpenGL out to pasture.
That's not even discussing the immense CPU overhead benefits for strategy games that DX12 already shows.
If NV finally designs a parallel + hardware Async Compute architecture for 2018-2019, the entire gaming industry will benefit as all major modern GPUs and consoles will be on the same page.
Under no circumstances should a Fury X be beating a 1070 by 26% in a modern game. We also already see that NV's architectures have utilization issues by comparing 1070 vs. 1080. The extra shader and TMU performance on the 1080 is just wasted. That means while Pascal is better utilized under DX11 than GCN is, Pascal itself is starting to run into its own bottlenecks.
DX11 API is already creating a CPU bottleneck for 1080 SLI based on Guru3D and TPU benches. This isn't about AMD vs. NV but the fact that DX11 is simply outdated and last gen.
They havent worked with nVidia. id just sold out. What a great gift to the nVidia customers who have bought the game in the last two months. :thumbsdown:
Doom is my last game from id. :thumbsup:
I got more salt from this post than a salt mine.
Cheer up, think of this more as having the shackles taken off of amd rather than not boosting nvidia. It just so happens that when gcn cards are allowed to operate as they were designed, they perform well.
DX12 was never promised for Rise of the Tomb Raider. Nixxess has not published a FAQ where they blamed AMD for the "bad" performance. They havent tweeted hundreds of tweets to show how great nVidia is.
I promise you you wont see any improvements for nVidia from id. Not one. Mark my words.
Is everyone saying these results are permanent with no more room for improvements for Nvidia with driver updates?
Is everyone saying these results are set in stone forevermore with no more room for improvements for Nvidia with driver updates?
bro correct ur post before u get modded. u can attack his post, but not him directly. no matter how deserving he is.Thats exactly why hes upset. Sontin, king of Nvidia f, would prefer GCN to keep its shackles on :whiste:
That is N+1No one is saying that...
As i understand it the api doesnt do the work the game engine have to. The api is ultra thin.Using Async compute doesn't require writing a whole other path. You change one of the parameters of your API calls to tell it to use async.
Code:D3D12_COMMAND_LIST_TYPE_COMPUTE or D3D12_COMMAND_LIST_TYPE_DIRECT
I mean the code can litterly look like this:
Code:if (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); }
Even if gcn have it of superior technical solution its only used because of the consoles.
I hereby herald Vulcan as GPU-Jesus!
He died so that our framerates might be high and our temperatures cool.
Yep. Translation error it seems. "Only" should have been "strictly"And the consoles drive the gaming market with huge sales numbers in comparison to PC game sales. So saying "only" is kinda funny.
Yep. Translation error it seems. "Only" should have been "strictly"
Yes. But they also have the tech for it.Strictly works! It does highlight the much improved work AMD has been doing in regards to developer relations since winning all the consoles.
They havent worked with nVidia. id just sold out. What a great gift to the nVidia customers who have bought the game in the last two months. :thumbsdown:
Doom is my last game from id. :thumbsup: