// d3d10umddi.h

PFND3DWDDM2_0DDI_CREATESHADERRESOURCEVIEW Pfnd3dwddm20DdiCreateshaderresourceview;

VOID Pfnd3dwddm20DdiCreateshaderresourceview(
  D3D10DDI_HDEVICE unnamedParam1,
  const D3DWDDM2_0DDIARG_CREATESHADERRESOURCEVIEW *unnamedParam2,
  D3D10DDI_HSHADERRESOURCEVIEW unnamedParam3,
  D3D10DDI_HRTSHADERRESOURCEVIEW unnamedParam4
)
{...}
View the official Windows Driver Kit DDI reference

NtDoc

No description available.

Edit description on GitHub

Windows Driver Kit DDI reference (nc-d3d10umddi-pfnd3dwddm2_0ddi_createshaderresourceview)

Description

CreateShaderResourceView(WDDM 2.0) creates a shader resource view.

Parameters

`unnamedParam1`

[in] hDevice is a handle to the display device (graphics context).

`unnamedParam2`

[in] pCreateShaderResourceView is a pointer to a D3DWDDM2_0DDIARG_CREATESHADERRESOURCEVIEW structure that describes the parameters that the user-mode display driver uses to create a shader resource view.

`unnamedParam3`

[in] hShaderResourceView is a handle to the driver's private data for the shader resource view.

`unnamedParam4`

[in] hRTShaderResourceView is a handle to the shader resource view that the driver should use when it calls back into the Direct3D runtime.

Remarks

The driver might run out of memory. Therefore, the driver can pass E_OUTOFMEMORY or D3DDDIERR_DEVICEREMOVED in a call to the pfnSetErrorCb function. The Direct3D runtime determines that any other errors are critical. If the driver passes any errors, which includes D3DDDIERR_DEVICEREMOVED, the Direct3D runtime determines that the handle is invalid; therefore, the runtime does not call the DestroyShaderResourceView function to destroy the handle that the hShaderResourceView parameter specifies.

PFND3DWDDM2_0DDI_CREATESHADERRESOURCEVIEW - NtDoc