diff options
| author | Wladimir J. van der Laan <laanwj@gmail.com> | 2013-02-21 20:56:34 +0100 |
|---|---|---|
| committer | Wladimir J. van der Laan <laanwj@gmail.com> | 2013-02-22 19:06:20 +0100 |
| commit | f07aa6ed6f85bec0adcc97267d69a6e3106ab4b8 (patch) | |
| tree | 256c1cdea001f9bd98db718a38bcdaa5fe8efc2c /doc | |
| parent | bae923bf240bcd3186eb2153d8c10dad166a1f5d (diff) | |
vs particle system using etna_pipe
- get pointcoord x/y to work
- point size output
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/hardware.md | 15 |
1 files changed, 15 insertions, 0 deletions
diff --git a/doc/hardware.md b/doc/hardware.md index dd327a7..e315b26 100644 --- a/doc/hardware.md +++ b/doc/hardware.md @@ -446,3 +446,18 @@ input is likely added to the end. [1] http://www.faqs.org/patents/app/20110249901 +Rendering points +------------------ +When rendering points (PRIMITIVE_TYPE_POINTS) there are some differences: + +- VS can have an extra output, the size of the point `gl_pointSize` + if `PA_CONFIG.POINT_SIZE_ENABLE` is set. This will be the last output in `VS_OUTPUT`. + +- There is an extra varying for `gl_pointCoord` with two components. This varying has + its components in `GL_VARYING_COMPONENT_USE` set to `POINTCOORD_X` and `POINTCOORD_Y`. + Its `PA_SHADER_ATTRIBUTES` is set to `0x000002f1`. + The VS output associated to this varying in `VS_OUTPUT` is discarded, so can be set + to any output register. + +- `rasterizer.point_size_per_vertex` affects number of vs outputs (just like MSAA!). + |