Explore >> Select a destination
|
You are here 
|
therealmjp.github.io | ||
| | | | |
microsoft.github.io
|
|
| | | | | Engineering specs for DirectX features. | |
| | | | |
acko.net
|
|
| | | | | Reinventing rendering one shader at a time | |
| | | | |
www.khronos.org
|
|
| | | | | We've just released an extension that I think will completely change how engines approach descriptors going forward. Descriptor sets are now backed by VkBuffer objects where you memcpy in descriptors. Delete VkDescriptorPool and VkDescriptorSet from the API, and have fun! | |
| | | | |
logins.github.io
|
|
| | | Why talking about the Root Signature? The Root Signature is the object that represents the link between the command list and the resources used by the pipeline. It specifies the data types that shaders should expect from the application, and also which pipeline state objects are compatible (those compiled with the same layout) for the next draw/dispatch calls. To check a practical usage of the root signature you can refer to my github repo FirstDX12Renderer by clicking here. Composition of the root signature will be described next. Note: Reader here is assumed to have a general understanding of D3D12 graphics pipeline and resources. You can read my article about the Pipeline State Object (PSO) and an article fully dedicated to shader resources will come late... | ||
