TESSELLATION IN GAMES PATCH
TESSELLATION IN GAMES CODE

Input geometry is made of patches and control points Not strictly vertices and polygons Each patch has several control points, from 1 to 32 The vertex shader processes each control point Likely to convert into world space But probably not into viewport space since they are not ready for rendering The hull shader also processes each control point But can access all points for a patch Used for patch-specific transforms

TESSELLATION IN GAMES CODE

The Effects framework (.fx) is not in the provided libraries Compile it ourselves (add an extra Effects11 project to our solution) DX maths libraries not in 11, now provided as an extra download No font support in the D3DX libraries (now an extra download) Or use Direct2D, DirectWrite, or a 3rd party library Minor changes to a few DX structures require code tweaksĥ New DX11 Pipeline Stages In order to support tessellation, DX11 adds three new stages to the rendering pipeline Two programmable stages: Hull Shader Domain Shader One fixed stage in between Tessellation stage No shader All three must be used together Only used when tessellating Disabled otherwise

1 Maths & Technologies for Games DirectX 11 – New Features Tessellation & Displacement MappingĢ Today’s Lecture Direct3D 11 – New featuresĭirect3D 11 – Changes from Direct3D 10 New DX11 Pipeline Tessellation Overview Patches Details: Hull Shader / Tessellation Stage / Domain Shader Displacement Mapping Technical Considerations and Issuesģ DirectX 11 – New Features DirectX 11 was introduced with Windows 7īut is also supported on Windows Vista Major new features introduced in DX11: Multithreaded rendering A single device can have several contexts Different threads that can render using the same resources Tessellation Introduced in this lecture Compute Shaders General purpose (non-graphics) programming on the GPU More recently, support has been added for DX10 hardware Shader Model 5.0 – extra shader language features High quality texture compression formatsĭirectX 11 is a strict superset of DX10.1 Nearly everything in DX10 works with minimal change Not like the huge changes from DX9 to DX10 Key points when converting: The device pointer (g_pD3DDevice) has been split in two A device pointer for overall control & a context pointer for each thread Use the immediate context pointer for single threaded work Context pointer used for most rendering: Draw, SetXXShader etc.

Tessellation in games