| UID | title | description | old-location | ms.date | keywords | ms.keywords | req.header | req.include-header | req.target-type | req.target-min-winverclnt | req.target-min-winversvr | req.kmdf-ver | req.umdf-ver | req.ddi-compliance | req.unicode-ansi | req.idl | req.max-support | req.namespace | req.assembly | req.type-library | req.lib | req.dll | req.irql | targetos | tech.root | req.typenames | f1_keywords | topic_type | api_type | api_location | api_name | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
NS:d3d10umddi.D3D11DDIARG_TESSELLATION_IO_SIGNATURES |
D3D11DDIARG_TESSELLATION_IO_SIGNATURES (d3d10umddi.h) |
The D3D11DDIARG_TESSELLATION_IO_SIGNATURES structure describes a tessellation I/O signature. |
display\d3d11ddiarg_tessellation_io_signatures.htm |
05/10/2018 |
|
D3D11DDIARG_TESSELLATION_IO_SIGNATURES, D3D11DDIARG_TESSELLATION_IO_SIGNATURES structure [Display Devices], UMDisplayDriver_Dx11param_Structs_5fb8a2b5-8291-4c80-a529-303f50f34cac.xml, d3d10umddi/D3D11DDIARG_TESSELLATION_IO_SIGNATURES, display.d3d11ddiarg_tessellation_io_signatures |
d3d10umddi.h |
D3d10umddi.h |
Windows |
D3D11DDIARG_TESSELLATION_IO_SIGNATURES is supported beginning with the Windows 7 operating system. |
Windows |
display |
D3D11DDIARG_TESSELLATION_IO_SIGNATURES |
|
|
|
|
|
The D3D11DDIARG_TESSELLATION_IO_SIGNATURES structure describes a tessellation I/O signature.
An array of D3D10DDIARG_SIGNATURE_ENTRY structures for the input part of a signature.
The number of entries in the array that the pInputSignature member specifies.
An array of D3D10DDIARG_SIGNATURE_ENTRY structures for the output part of a signature.
The number of entries in the array that the pOutputSignature member specifies.
An array of D3D10DDIARG_SIGNATURE_ENTRY structures for the signature patches.
The number of entries in the array that the pPatchConstantSignature member specifies.
A signature is basically the union of all registers that are input and output by any shader that shares the signature. Therefore, a signature might be a superset of what a given shader might actually input or output.
Hardware should determine that the upstream stage in the pipeline might provide some or all of the data in the signature that is laid out as the pInputSignature and NumInputSignatureEntries members specify. Similarly, hardware should determine that the downstream stage in the pipeline might consume some or all of the data in the signature that is laid out as the pOutputSignature and NumInputSignatureEntries members specify.
To comply with the requirement for the event input and output registers to be reordered during shader compilation, the full signature is passed to the driver. Such reordering might depend on the driver being able to determine all of the registers in the signature, as well as which registers have system names (for example, names that the SystemValue member of the D3D10DDIARG_SIGNATURE_ENTRY structure specifies). Such reordering might also depend on the driver being able to determine registers that are not present in the current shader.
The declarations within the shader code itself also show which registers are actually used by a particular shader. These registers are possibly a subset of the input and output parts of the signature. If some hardware is not required to reorder input and output registers at compile time, the driver for that hardware can completely ignore the full signature that the D3D11DDIARG_TESSELLATION_IO_SIGNATURES structure provides. The reference rasterizer, for example, does not require the information that the D3D11DDIARG_TESSELLATION_IO_SIGNATURES structure provides.