Skip to content

Latest commit

 

History

History
77 lines (60 loc) · 2.73 KB

ns-d3d10umddi-d3d10ddi_vertex_cache_desc.md

File metadata and controls

77 lines (60 loc) · 2.73 KB
Raw
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.D3D10DDI_VERTEX_CACHE_DESC
D3D10DDI_VERTEX_CACHE_DESC (d3d10umddi.h)
The D3D10DDI_VERTEX_CACHE_DESC structure describes mesh-optimization data.
display\d3d10ddi_vertex_cache_desc.htm
05/10/2018
D3D10DDI_VERTEX_CACHE_DESC structure
D3D10DDI_VERTEX_CACHE_DESC, D3D10DDI_VERTEX_CACHE_DESC structure [Display Devices], UMDisplayDriver_Dx10param_Structs_585c3ccc-83c7-4d3b-903d-7eac81a1c21c.xml, d3d10umddi/D3D10DDI_VERTEX_CACHE_DESC, display.d3d10ddi_vertex_cache_desc
d3d10umddi.h
D3d10umddi.h
Windows
Available in Windows Vista and later versions of the Windows operating systems.
Windows
display
D3D10DDI_VERTEX_CACHE_DESC
D3D10DDI_VERTEX_CACHE_DESC
d3d10umddi/D3D10DDI_VERTEX_CACHE_DESC
APIRef
kbSyntax
HeaderDef
d3d10umddi.h
D3D10DDI_VERTEX_CACHE_DESC

D3D10DDI_VERTEX_CACHE_DESC structure

-description

The D3D10DDI_VERTEX_CACHE_DESC structure describes mesh-optimization data.

-struct-fields

-field Pattern [out]

The bit pattern. The driver must specify the bit pattern as a CACH four-character code (FOURCC) value. The driver can use the following MAKEFOURCC macro to specify the FOURCC value as CACH:

MAKEFOURCC('C', 'A', 'C', 'H');

-field OptMethod [out]

The method of mesh optimization. The driver can use one of the following values to specify the mesh optimization that it uses.

Value Meaning
0 Longest strips optimization
1 Vertex-cache-based optimization

-field CacheSize [out]

The effective size, in entries, that the driver optimizes the vertex cache for. The actual cache size is not required to be the size that is specified in CacheSize because the actual cache size is larger in most situations. The driver specifies an optimized size in CacheSize only if it also specifies 1 in the OptMethod member.

-field MagicNumber [out]

The number that should be used as part of a trial-and-error procedure when you are determining when to restart the strips list. This number can be from 1 through the value that is specified in the CacheSize member. Typically, the best values are near CacheSize/2. The driver specifies a number in MagicNumber only if it also specifies 0 in the OptMethod member.