diff options
| author | kbr@chromium.org <kbr@chromium.org@736b8ea6-26fd-11df-bfd4-992fa37f6226> | 2012-10-16 21:54:27 +0000 |
|---|---|---|
| committer | kbr@chromium.org <kbr@chromium.org@736b8ea6-26fd-11df-bfd4-992fa37f6226> | 2012-10-16 21:54:27 +0000 |
| commit | 6a026c49e9947d1a485777457631c5f3ed774619 (patch) | |
| tree | fd2eee47ce7e5ab515833849f5045d1e1050cc80 /extensions | |
| parent | c41bb9a21b3bbd1d0f0e68d9d59a03eb7445500a (diff) | |
| download | angle-6a026c49e9947d1a485777457631c5f3ed774619.tar.gz | |
Based on feedback from Al Patrick, Nicolas Capens and Daniel Koch,
removed the restriction about draw buffer 0 having to be non-NULL if
any higher draw buffers are non-NULL. Appears this can be supported
with a NULL FOURCC render target. Removed issue and adjusted
introductory text.
Review URL: https://codereview.appspot.com/6725048
git-svn-id: https://angleproject.googlecode.com/svn/trunk@1292 736b8ea6-26fd-11df-bfd4-992fa37f6226
Diffstat (limited to 'extensions')
| -rw-r--r-- | extensions/ANGLE_multiple_render_targets.txt | 17 |
1 files changed, 6 insertions, 11 deletions
diff --git a/extensions/ANGLE_multiple_render_targets.txt b/extensions/ANGLE_multiple_render_targets.txt index 458801bf..21df2ab3 100644 --- a/extensions/ANGLE_multiple_render_targets.txt +++ b/extensions/ANGLE_multiple_render_targets.txt @@ -13,6 +13,10 @@ Contributors Contributors to the OpenGL ES 2.0 specification Contributors to the OpenGLSL ES 1.0.17 specification Contributors to the OpenGL ES 3.0 specification + Nicolas Capens, TransGaming Inc. + Daniel Koch, TransGaming Inc. + Alastair Patrick, Google Inc. + Members of the WebGL working group Contact @@ -47,8 +51,7 @@ Overview This extension is similar to the combination of the GL_NV_draw_buffers and GL_NV_fbo_color_attachments extensions, but imposes certain - restrictions informed both by the OpenGL ES 3.0 API as well as the - current implementation of the ANGLE library. + restrictions informed by the OpenGL ES 3.0 API. New Procedures and Functions @@ -217,9 +220,7 @@ Operations and the Frame Buffer) in <bufs> must be COLOR_ATTACHMENT<i>_ANGLE or NONE. Specifying a buffer out of order, BACK, or COLOR_ATTACHMENT<m>_ANGLE where <m> is greater than or equal to the value of MAX_COLOR_ATTACHMENTS_ANGLE, - will generate the error INVALID_OPERATION. If the buffer at index 0 - is NONE and any buffer at a higher index is anything other than - NONE, DrawBuffersANGLE will generate the error INVALID_OPERATION. + will generate the error INVALID_OPERATION. If a fragment shader writes to "gl_FragColor", DrawBuffersANGLE specifies a set of draw buffers into which the color written to @@ -310,9 +311,3 @@ New State Issues See ARB_draw_buffers for relevant issues. - - 1. Why does DrawBuffersANGLE restrict draw buffer index 0 to be - non-NULL if any of the other buffers are non-NULL? - - RESOLVED: In order to conform to D3D9 restrictions for - implementation in ANGLE. |