High-Level Shading Language

The High-Level Shader Language[1] or High-Level Shading Language[2] (HLSL) is a proprietary shading language developed by Microsoft for the Direct3D 9 API to augment the shader assembly language, and went on to become the required shading language for the unified shader model of Direct3D 10 and higher.

A scene containing several different 2D HLSL shaders. Distortion of the statue is achieved purely physically, while the texture of the rectangular frame beside it is based on color intensity. The square in the background has been transformed and rotated. The partial transparency and reflection of the water in the foreground are added by a shader applied finally to the entire scene.

HLSL is analogous to the GLSL shading language used with the OpenGL standard. It is very similar to the Nvidia Cg shading language, as it was developed alongside it. Early versions of the two languages were considered identical, only marketed differently.[3] HLSL shaders can enable profound speed and detail increases as well as many special effects in both 2D and 3D computer graphics.

HLSL programs come in six forms: pixel shaders (fragment in GLSL), vertex shaders, geometry shaders, compute shaders, tessellation shaders (Hull and Domain shaders), and raytracing shaders (Ray Generation Shaders, Intersection Shaders, Any Hit/Closest Hit/Miss Shaders). A vertex shader is executed for each vertex that is submitted by the application, and is primarily responsible for transforming the vertex from object space to view space, generating texture coordinates, and calculating lighting coefficients such as the vertex's tangent, binormal and normal vectors. When a group of vertices (normally 3, to form a triangle) come through the vertex shader, their output position is interpolated to form pixels within its area; this process is known as rasterization.

Optionally, an application using a Direct3D 10/11/12 interface and Direct3D 10/11/12 hardware may also specify a geometry shader. This shader takes as its input some vertices of a primitive (triangle/line/point) and uses this data to generate/degenerate (or tessellate) additional primitives or to change the type of primitives, which are each then sent to the rasterizer.

D3D11.3 and D3D12 introduced Shader Model 5.1[4] and later 6.0.[5]

Shader model comparison

GPUs listed are the hardware that first supported the given specifications. Manufacturers generally support all lower shader models through drivers. Note that games may claim to require a certain DirectX version, but don't necessarily require a GPU conforming to the full specification of that version, as developers can use a higher DirectX API version to target lower-Direct3D-spec hardware; for instance DirectX 9 exposes features of DirectX7-level hardware that DirectX7 did not, targeting their fixed-function T&L pipeline.

Pixel shader comparison
Pixel shader version 1.0 to 1.3[6] 1.4[6]2.0[6][7]2.0a[6][7][8]2.0b[6][7][9]3.0[6][10]4.0[11]
4.1[12]
5.0[13]
Dependent texture limit 468Unlimited8UnlimitedUnlimited
Texture instruction limit 46*232UnlimitedUnlimitedUnlimitedUnlimited
Position register NoNoNoNoNoYesYes
Instruction slots 8+48+432 + 64512512≥ 512≥ 65536
Executed instructions 8+46*2+8*232 + 6451251265536Unlimited
Texture indirections 444Unlimited4UnlimitedUnlimited
Interpolated registers 2 + 42 + 62 + 82 + 82 + 81032
Instruction predication NoNoNoYesNoYesNo
Index input registers NoNoNoNoNoYesYes
Temp registers 2612 to 322232324096
Constant registers 8832323222416×4096
Arbitrary swizzling NoNoNoYesNoYesYes
Gradient instructions NoNoNoYesNoYesYes
Loop count register NoNoNoNoNoYesYes
Face register (2-sided lighting) NoNoNoNoYesYesYes
Dynamic flow control NoNoNoNoNoYes (24)Yes (64)
Bitwise Operators NoNoNoNoNoNoYes
Native Integers NoNoNoNoNoNoYes
  • PS 1.0 — Unreleased 3dfx Rampage, DirectX 8.
  • PS 1.1 — GeForce 3, DirectX 8.
  • PS 1.2 — 3Dlabs Wildcat VP, DirectX 8.0a.
  • PS 1.3 — GeForce 4 Ti, DirectX 8.0a.
  • PS 1.4 — Radeon 8500-9250, Matrox Parhelia, DirectX 8.1.
  • Shader Model 2.0 — Radeon 9500-9800/X300-X600, DirectX 9.
  • Shader Model 2.0a — GeForce FX/PCX-optimized model, DirectX 9.0a.
  • Shader Model 2.0b — Radeon X700-X850 shader model, DirectX 9.0b.
  • Shader Model 3.0 — Radeon X1000 and GeForce 6, DirectX 9.0c.
  • Shader Model 4.0 — Radeon HD 2000 and GeForce 8, DirectX 10.
  • Shader Model 4.1 — Radeon HD 3000 and GeForce 200, DirectX 10.1.
  • Shader Model 5.0 — Radeon HD 5000 and GeForce 400, DirectX 11.
  • Shader Model 5.1 — GCN 1+, Fermi+, DirectX 12 (11_0+) with WDDM 2.0.
  • Shader Model 6.0 — GCN 1+, Kepler+, DirectX 12 (11_0+) with WDDM 2.1.
  • Shader Model 6.1 — GCN 1+, Kepler+, DirectX 12 (11_0+) with WDDM 2.3.
  • Shader Model 6.2 — GCN 1+, Kepler+, DirectX 12 (11_0+) with WDDM 2.4.
  • Shader Model 6.3 — GCN 1+, Kepler+, DirectX 12 (11_0+) with WDDM 2.5.
  • Shader Model 6.4 — GCN 1+, Kepler+, Skylake+, DirectX 12 (11_0+) with WDDM 2.6.
  • Shader Model 6.5 — GCN 1+, Kepler+, Skylake+, DirectX 12 (11_0+) with WDDM 2.7.

"32 + 64" for Executed Instructions means "32 texture instructions and 64 arithmetic instructions."

Vertex shader comparison
Vertex shader version VS 1.1[14] VS 2.0[7][14][15]VS 2.0a[7][14][15]VS 3.0[10][14]VS 4.0[11]
VS 4.1[16]
VS 5.0[13]
# of instruction slots 128256256≥ 512≥ 65536
Max # of instructions executed 12810246553665536Unlimited
Instruction predication NoNoYesYesYes
Temp registers 121216324096
# constant registers ≥ 96≥ 256256≥ 25616×4096
Static flow control NoYesYesYesYes
Dynamic flow control NoNoYesYesYes
Dynamic flow control depth N/AN/A242464
Vertex texture fetch NoNoNoYesYes
# of texture samplers N/AN/AN/A4128
Geometry instancing support NoNoNoYesYes
Bitwise operators NoNoNoNoYes
Native integers NoNoNoNoYes
gollark: Biotech? To some extent, sure.
gollark: DNA is basically horrible spaghetti code with absolutely no comments and which seems like it may be partly self-modifying.
gollark: If you tweak them at all, they probably stop working properly for unfathomable chemistry/physics reasons.
gollark: I mean, consider enzymes. They can do things which regular non-biochemist chemists could only dream of, and often do multiple functions at once and interact with each other in bizarre ways.
gollark: Much of the foolish human body is like this, because it's hyperoptimized in some ways by a design process which doesn't care if our brains can actually make sense of it.

See also

Footnotes
  1. "Writing HLSL Shaders in Direct3D 9 (Windows)". msdn.microsoft.com.
  2. "HLSL". MSDN. Microsoft. Retrieved 5 January 2015.
  3. "Fusion Industries :: Cg and HLSL FAQ ::". 24 August 2012. Archived from the original on 24 August 2012.
  4. "Shader Model 5.1 Objects (Windows)". msdn.microsoft.com.
  5. "HLSL Shader Model 6.0 (Windows)". msdn.microsoft.com.
  6. "Pixel Shader Differences". msdn.microsoft.com. 2011-02-08.
  7. Peeper, Craig (2004-03-15). "Microsoft DirectX High Level Shader Language (HLSL)" (PPT). microsoft.com. pp. 5–8, 24–25.
  8. Shimpi, Anand Lal. "NVIDIA Introduces GeForce FX (NV30)".
  9. Wilson, Derek. "ATI Radeon X800 Pro and XT Platinum Edition: R420 Arrives".
  10. Shader Model 3.0, Ashu Rege, NVIDIA Developer Technology Group, 2004.
  11. The Direct3D 10 System, David Blythe, Microsoft Corporation, 2006.
  12. "Registers - ps_4_1 (Windows)". msdn.microsoft.com.
  13. "Registers - ps_5_0 (Windows)". msdn.microsoft.com.
  14. "Vertex Shader Differences". msdn.microsoft.com. 2011-02-08.
  15. Shimpi, Anand Lal. "NVIDIA Introduces GeForce FX (NV30)".
  16. "Registers - vs_4_1 (Windows)". msdn.microsoft.com.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.