- Vertex Specification
- Vertex Processing
- Vertex Post-Processing
- Primitive Assembly
- Fragment Shader
- Per-Sample Processing
Primitive Assembly is the stage in the OpenGL rendering pipeline where Primitives are divided into a sequence of individual base primitives. After some minor processing, as described below, they are passed along to the rasterizer to be rendered.
Early primitive assembly
The purpose of the primitive assembly step is to convert a vertex stream into a sequence of base primitives. For example, a primitive which is a line list of 12 vertices needs to generate 11 line base primitives.
The full primitive assembly step (including the processing below) will happen during Vertex Post-Processing. However, some Vertex Processing steps require that a primitive be decomposed into a sequence of base primitives. For example, a Geometry Shader operates on each input base primitive in the primitive sequence. Therefore, a form of primitive assembly must happen before the GS can execute.
This early primitive assembly only performs the conversion to base primitives. It does not perform any of the below processing steps.
The order in which primitives are processed is well-defined (in most cases). The order is defined as follows:
- All primitives from a single Vertex Rendering command are ordered before any primitives from later such commands.
- If the drawing command is a multi-draw command, then all primitives for one sub-draw are ordered before primitives from subsequent sub-draws.
- Within a draw or a multidraw's sub-draw, if the drawing command is an Instanced Rendering command, then all primitives in one instance are ordered before the primitives with larger gl_InstanceID values.
- Within a particular draw/sub-draw/instance, the primitives are ordered based on the vertex stream and the rendering parameters for that draw, as interpreted by the Primitive type provided by the rendering command.
- If a Tessellation Evaluation Shader is active, all primitives generated by tessellating a single patch are ordered before any primitives generated by patches with larger gl_PrimitiveID values.
- The order of any given primitive generated by a particular patch is undefined relative to other primitives generated from that same patch.
- If a Geometry Shader is active, primitives generated from a particular input primitive are ordered before primitives generated by a later input primitive, per the above ordering rules.
- For a particular input primitive, if the GS uses Geometry Shader Instancing, then all primitives generated by an instance are ordered before primitives generated by instances with larger gl_InvocationID values.
- Within a GS invocation, primitives generated by a GS are ordered by the invocations ordered in which those primitives, and their component vertices, are emitted.
All primitives can be discarded by enabling GL_RASTERIZER_DISCARD. This prevents any primitives from being rasterized.
This is useful for testing the performance of prior rendering stages, but it is also useful to prevent rendering of primitives generated during Transform Feedback operations.
The culling of triangle primitives happens during this point in the pipeline.