Are you sure that Terascale would be able to manage CBV descriptor table without any additional change of the runtime? (ie more CPU overhead which is what D3D12 want to avoid)
I know there were some runtime changes during the preview period, like the increase Tier 1 descriptor heap size to 2^20...
It's not only about the full lack of indexable resources, also Terascale cannot directly manage CBv in a table like in all other architectures while the possibility of manage SRVs would also be quite ridiculous (8 SRVs if the documentation I have is correct)... Supporting Terascale architecture...
Those GPUs are no more supported, which means games released after Terascale end support are not tested and supposed to work correctly with those cards. A 2017 game requiring DirectX 11 doesn't automatically mean "any DirectX 11 graphics card".
On hybrid (VLIW+GCN) laptops you should force the...
VLIW AMD GPUs (Terascale) never meant to have WDDM 2.x drivers, never they were advertised to be supported: they lacked of different binding features, like indexable resources, moreover the low-level binding model would be quite impossible to apply on those architecture. By some binding point of...
The big issue with Fermi DX 12 support is it comes too late. At the DX12 launch with Windows 10, it was the biggest spread architecture, but now it a deprecated architecture by a development point of view since NVIDIA dropped Fermi support from it's profiling&debug tool Nsight.
Nope, only the...
What about Kepler GPUs? I am pretty sure the bypass of # of UAV and CBV bindings can by bypassed (not sure how much the performance impact, especially on CBVs..), but at least Kepler should not allow empty slots on the root buffer (which would preclude the Tier 3 of RB) and empty slots cannot...
GCN1 asynchronous compute queues works fine again. http://www.bitsandchips.it/english/52-english-news/8053-welcome-back-asynchronous-compute-queues-gcn-1-0
I am not sure if GCN1 will support SM6. It is only mandatory for FL12_0+ GPUs. Moreover the current status of the driver causes synchronization and stability issues if you do not use an ad-hoc code path, like it was 1 year ago for Maxwell GPUs (now commands serialization under those NV GPUs...
De-ja-vou
https://twitter.com/postgoodism/status/473526169132752896
Did I win something?
This thread is a dead-end anyway. Some people do not understand the differences between introduction manual, implementation, low-level programming concepts.
An API is not a magic tool that maximize hardware performance. You - developer - have to maximize your application performance through that tool. APIs like LibGCM, Mantle, Metal, Direct3D 12 and Vulkan are meant to reduce the impact of the API runtime on your application, to reduce the driver...
I do not discredit those people, I sample state that you cannot explain well the things with a so limited number of characters. Twitter is a BAD form of communication, it limits your communication. "Very similar" doesn't mean a plagiarism or whatever have been said in these and other forums...
Mantle SDK beta access started after Mantel was out, games using Mantle were out before. DX12 EAP started when D3D12 and related technologies was still in development, an advanced state of development thought, but it was not done. DX12 EAP is not just a private and preview access to the API, we...
I said AMD, not mantle. Of course AMD had a more recent study case (Mantle) compared to NVIDIA (libCGM) or Intel, but that does not means or state that D3D12 start with Mantle as base API.
I know that without public documentation no-one cannot create a valid bullet-proof history reconstruction...
I am not a software engineer for making a major game engine, but I am a member of the DX12 EAP, I have accessed to a lot of NDA and unpublished documentation, I know piece of D3D12 API evolution that most people don't, so I am not spread fud.
That page of that stupid introduction programming...
It is always funny see people ranting about API conspiracy theories just because a single draft introduction manual page was copied from another API...
You probably have not programmed enough.
Mantle error handling is the same error handling used in tons of Win32 API, from Direct3D 11 to WioAPI...
I have a better question (for all 3 major HIVs):
Non-fault on D3D12 shader cache drivers, when?
Folks, most of upcoming DX12 games are expected to be released on 2015/2016 XMas/Winter holidays.
I am disappointed that I need to watch a full video instead to read numbers on a textual "review".
Lolj, let's wait to see how AMD HBM MC works on multi-GPU...
They will be able to work together, in concurrency. Parallelism is particular case of concurrency and it generally more difficult do achieve. On different hardware, parallelism could become a restriction compared to its general form (concurrency).
You can find some early informations with...
The feature level could have been named better or just not named at all (DX12 has still very few caps-bits compared to DX9 and the extension hell of OGL), but yes D3D12 will bring benefits to all DX12 capable systems, a lot of people still do not understand this.
Maintain such limitation would...
At the time D3D11.1 was out, FL 11.1 came with some very interesting UAV features and improvements not exposed to FL 11.0.. For some developers it was a very nice improvement.
It does not stand out for me, it simply was not the subject of that small article.
Hi, you are right, FL 12.0 requires tiled resource tier 2 and (a well-defined and rich set of) typed UAV loads in addition to FL 11.1 (as long resource binding tier 2 to brake with the old requirements inherited from DX 11).
I simply wrote that small article to make clearer the difference...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.