Create a domain shader .
HRESULT CreateDomainShader( [in] const void *pShaderBytecode, [in] SIZE_T BytecodeLength, [in] ID3D11ClassLinkage *pClassLinkage, [out] ID3D11DomainShader **ppDomainShader );
- pShaderBytecode [in]
Type: const void*
A pointer to a compiled shader.
- BytecodeLength [in]
Size of the compiled shader.
- pClassLinkage [in]
A pointer to a class linkage interface (see ID3D11ClassLinkage); the value can be NULL.
- ppDomainShader [out]
Address of a pointer to a ID3D11DomainShader interface. If this is NULL, all other parameters will be validated, and if all parameters pass validation this API will return S_FALSE instead of S_OK.
This method returns one of the following Direct3D 11 Return Codes.
The Direct3D 11.1 runtime, which is available starting with Windows 8, provides the following new functionality for CreateDomainShader.
The following shader model 5.0 instructions are available to just pixel shaders and compute shaders in the Direct3D 11.0 runtime. For the Direct3D 11.1 runtime, because unordered access views (UAV) are available at all shader stages, you can use these instructions in all shader stages.
Therefore, if you use the following shader model 5.0 instructions in a domain shader, you can successfully pass the compiled domain shader to pShaderBytecode. That is, the call to CreateDomainShader succeeds.
If you pass a compiled shader to pShaderBytecode that uses any of the following instructions on a device that doesn’t support UAVs at every shader stage (including existing drivers that are not implemented to support UAVs at every shader stage), CreateDomainShader fails. CreateDomainShader also fails if the shader tries to use a UAV slot beyond the set of UAV slots that the hardware supports.
- All atomics and immediate atomics (for example, atomic_and and imm_atomic_and)
Windows Phone 8: This API is supported.
Build date: 11/28/2012