Skip to content

A
angle
Commit 6a026c49 by kbr@chromium.org
Options

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
parent c41bb9a2
Showing with 7 additions and 12 deletions
extensions/ANGLE_multiple_render_targets.txt
...@@ -13,6 +13,10 @@ Contributors ...@@ -13,6 +13,10 @@ Contributors
Contributors to the OpenGL ES 2.0 specification Contributors to the OpenGL ES 2.0 specification
Contributors to the OpenGLSL ES 1.0.17 specification Contributors to the OpenGLSL ES 1.0.17 specification
Contributors to the OpenGL ES 3.0 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 Contact
...@@ -47,8 +51,7 @@ Overview ...@@ -47,8 +51,7 @@ Overview
This extension is similar to the combination of the GL_NV_draw_buffers This extension is similar to the combination of the GL_NV_draw_buffers
and GL_NV_fbo_color_attachments extensions, but imposes certain and GL_NV_fbo_color_attachments extensions, but imposes certain
restrictions informed both by the OpenGL ES 3.0 API as well as the restrictions informed by the OpenGL ES 3.0 API.
current implementation of the ANGLE library.
New Procedures and Functions New Procedures and Functions
...@@ -217,9 +220,7 @@ Operations and the Frame Buffer) ...@@ -217,9 +220,7 @@ Operations and the Frame Buffer)
in <bufs> must be COLOR_ATTACHMENT<i>_ANGLE or NONE. Specifying a 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 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, greater than or equal to the value of MAX_COLOR_ATTACHMENTS_ANGLE,
will generate the error INVALID_OPERATION. If the buffer at index 0 will generate the error INVALID_OPERATION.
is NONE and any buffer at a higher index is anything other than
NONE, DrawBuffersANGLE will generate the error INVALID_OPERATION.
If a fragment shader writes to "gl_FragColor", DrawBuffersANGLE If a fragment shader writes to "gl_FragColor", DrawBuffersANGLE
specifies a set of draw buffers into which the color written to specifies a set of draw buffers into which the color written to
...@@ -310,9 +311,3 @@ New State ...@@ -310,9 +311,3 @@ New State
Issues Issues
See ARB_draw_buffers for relevant 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.
src/common/version.h
#define MAJOR_VERSION 1 #define MAJOR_VERSION 1
#define MINOR_VERSION 0 #define MINOR_VERSION 0
#define BUILD_VERSION 0 #define BUILD_VERSION 0
#define BUILD_REVISION 1291 #define BUILD_REVISION 1292
#define STRINGIFY(x) #x #define STRINGIFY(x) #x
#define MACRO_STRINGIFY(x) STRINGIFY(x) #define MACRO_STRINGIFY(x) STRINGIFY(x)
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment