Lines Matching refs:framebuffer
151 known collectively as "framebuffer-attachable images". This
152 extension provides a mechanism for attaching framebuffer-attachable
153 images to the GL framebuffer as one of the standard GL logical
155 framebuffer-attachable image to the accum logical buffer is left for
156 a future extension to define). When a framebuffer-attachable image
157 is attached to the framebuffer, it is used as the source and
160 By allowing the use of a framebuffer-attachable image as a rendering
163 of a texture to be used as framebuffer-attachable images. A
165 framebuffer-attachable image by specifying the mipmap level, cube
169 the framebuffer, followed immediately by a call to CopyTexSubImage.
177 image of renderbuffer can be used as a framebuffer-attachable image
188 framebuffer-attachable images, this extension introduces another new
189 GL object, called a framebuffer object. A framebuffer object
190 contains the state that defines the traditional GL framebuffer,
198 GL provides the function BindFramebufferARB to bind a framebuffer
200 the window-system-provided framebuffer in order to display rendered
222 ARB_render_texture, a single framebuffer object can facilitate
226 framebuffer object binding point into separate DRAW and READ
229 framebuffer to another. In addition, a new high performance blit
244 All of the framebuffer-attachable images attached to a framebuffer
245 object must have the same number of SAMPLES or else the framebuffer
246 object is not "framebuffer complete". If a framebuffer object with
247 multisample attachments is "framebuffer complete", then the
248 framebuffer object behaves as if SAMPLE_BUFFERS is one.
262 application-created framebuffer object, MULTISAMPLE is enabled, and
267 application-created framebuffer object and the destination is a
268 single-sample framebuffer object (either application-created or
285 mechanism exists for sharing a framebuffer-attachable image across
286 several framebuffer objects, as well as sharing an image between a
287 framebuffer object and a texture. If we had retained the "implicit"
376 the depth and stencil attachment points of a framebuffer object,
378 buffers of the framebuffer. This fits nicely with hardware that
384 attached to the stencil attachment of the bound framebuffer object,
386 from or writes to the framebuffer's stencil buffer.
393 framebuffer.
395 framebuffer:
421 framebuffer-attachable image:
423 buffer attachment points of a framebuffer object. Texture
425 framebuffer-attachable images.
429 framebuffer-attachable image, and allows that
430 framebuffer-attachable image to be used to store the
431 contents of a logical buffer of a framebuffer object. There
433 and stencil buffer of a framebuffer.
454 framebuffer attachment completeness:
457 framebuffer attachment points. (for complete definition,
460 framebuffer completeness:
463 relationships among the attached framebuffer-attachable
483 boolean IsFramebuffer(uint framebuffer);
484 void BindFramebuffer(enum target, uint framebuffer);
663 system-provided framebuffer at any time, referred to as the <default
664 framebuffer>. Application-created framebuffers, referred to as
665 <framebuffer objects>, may be created as desired. These two types of
666 framebuffer are distinguished primarily by the interface for configuring
669 The effects of GL commands on the default framebuffer are ultimately
670 controlled by the window system, which allocates framebuffer resources,
671 determines what portions of the default framebuffer the GL may access at
674 context or configure the default framebuffer. Similarly, display of
675 framebuffer contents on a physical display device (including the
676 transformation of individual framebuffer values by such techniques as
679 Allocation and configuration of the default framebuffer occurs outside
689 It is possible to use a GL context <without> a default framebuffer, in
690 which case a framebuffer object must be used to perform all rendering.
709 "framebuffer complete" (see section 4.4.4.2)."
756 READ_FRAMEBUFFER_BINDING is not "framebuffer complete"
778 bound to READ_FRAMEBUFFER_BINDING is not "framebuffer
812 "framebuffer complete" (see section 4.4.4.2)."
915 DRAW_FRAMEBUFFER_BINDING is not "framebuffer complete"
997 "...The image is taken from the framebuffer exactly as if these
1032 to READ_FRAMEBUFFER_BINDING is not "framebuffer complete"
1048 (i), (i,j), or (i,j,k). See Chapter 4 for discussion of framebuffer
1052 framebuffer object <F>.
1055 framebuffer object <F>.
1084 bound as a color buffer of a framebuffer object."
1147 texture are attached to a framebuffer object. See section 4.4.2.3
1200 "The framebuffer, whether it is the default framebuffer or a framebuffer
1204 discussion, each pixel in the framebuffer is simply a set of some
1206 depending on the GL implementation, the type of framebuffer
1207 selected, and parameters specified when the framebuffer was created.
1208 Creation and management of the default framebuffer is outside the scope
1209 of this specification, while creation and management of framebuffer
1212 Corresponding bits from each pixel in the framebuffer are grouped
1219 framebuffer or a framebuffer object.
1221 For the default framebuffer, the color buffers are the <front left>
1232 accumulation, depth, or stencil buffers. If no default framebuffer is
1233 associated with the GL context, the framebuffer is incomplete except
1234 when a framebuffer object is bound (see sections 4.4.1 and 4.4.4).
1237 buffers present in the default framebuffer. Instead, the buffers of an
1238 framebuffer object are specified by attaching individual textures or
1240 framebuffer object has an array of color buffer attachment points,
1243 framebuffer object must be complete, as described in section 4.4.4. Not
1244 all attachments of a framebuffer object need to be populated.
1261 buffers is dependent on the currently bound framebuffer. For the default
1262 framebuffer, the number of bitplanes is fixed. For framebuffer objects,
1266 The GL has two active framebuffers; the <draw framebuffer> is the
1267 destination for rendering operations, and the <read framebuffer> is the
1268 source for readback operations. The same framebuffer may be used for
1270 controlling framebuffer usage."
1272 The default framebuffer is initially used as the draw and read
1273 framebuffer [fn1], and the initial state of all provided bitplanes is
1284 "If the draw framebuffer is a framebuffer object (see section 4.2.1),
1285 the pixel ownership test always passes, since the pixels of framebuffer
1287 framebuffer is the default framebuffer, the window system controls pixel
1296 number of bits in the stencil buffer attached to the draw framebuffer.
1302 stored at the corresponding location in the framebuffer. The result
1303 replaces the values in the framebuffer at the fragment's (x[w],
1305 framebuffer-attachable image more than once, then the values stored
1319 the default framebuffer (i.e., DRAW_FRAMEBUFFER_BINDING is zero), or a
1320 framebuffer object (i.e., DRAW_FRAMEBUFFER_BINDING is non-zero). In the
1321 initial state, the GL is bound to the default framebuffer. For more
1322 information about framebuffer objects, see section 4.4.
1324 If the GL is bound to the default framebuffer, then
1337 If the GL is bound to a framebuffer object,
1342 to the image attached to the framebuffer at COLOR_ATTACHMENTi.
1345 application-created framebuffer objects is COLOR_ATTACHMENT0.
1355 context is bound to a framebuffer object, and
1359 If the GL is bound to the default framebuffer and
1364 If the GL is bound to a framebuffer object and <buf> is one of the
1371 the default framebuffer nor a framebuffer object, then the error
1390 framebuffer (i.e., DRAW_FRAMEBUFFER_BINDING is zero), or an
1391 framebuffer object (i.e.,
1393 framebuffer objects, see section 4.4.
1407 to the default framebuffer, and the buffers that they indicate.
1410 framebuffer, then each of the constants must be one of the
1413 If the GL is bound to a framebuffer object,
1445 For both the default framebuffer and framebuffer objects,
1452 If the GL is bound to the default framebuffer and
1457 If the GL is bound to a framebuffer object and
1476 framebuffer is an integer
1478 framebuffer, in the initial state, the draw
1480 buffers; otherwise it is BACK. For framebuffer
1483 framebuffer and framebuffers objects, the initial state
1517 is written to its indicated location in the framebuffer, subject to
1521 written to the framebuffer; the setting of DepthTest is ignored.
1533 (see section 4.4) is non-zero, the read framebuffer is framebuffer
1534 complete, and the value of SAMPLE_BUFFERS for the read framebuffer
1565 framebuffer (i.e., READ_FRAMEBUFFER_BINDING is zero), or a
1566 framebuffer object (i.e.,
1568 framebuffer objects, see section 4.4.
1570 If the object bound to READ_FRAMEBUFFER_BINDING is not <framebuffer
1574 framebuffer, nor legal for a
1575 framebuffer object, then the error INVALID_ENUM results.
1577 When READ_FRAMEBUFFER_BINDING is zero, i.e. the default framebuffer,
1583 INVALID_OPERATION is generated. For the default framebuffer, the initial
1587 When the GL is using a framebuffer object, <src> must be one of the
1590 enables reading from the image attached to the framebuffer at
1591 COLOR_ATTACHMENTi. For framebuffer objects, the initial setting for
1602 currently bound framebuffer object, then the values obtained for
1655 of the read framebuffer to another in the draw framebuffer."
1666 Values are obtained from the framebuffer, converted (if
1706 "framebuffer complete" (as defined in section 4.4.4.2).
1708 READ_FRAMEBUFFER_BINDING is "framebuffer complete" and the value
1713 4.4) is not "framebuffer complete".
1724 region of the read framebuffer to another in the draw framebuffer.
1739 buffer of the read framebuffer and written to each of the draw buffers
1740 of the draw framebuffer, just as with CopyPixels.
1742 The actual region taken from the read framebuffer is limited to the
1746 The actual region written to the draw framebuffer is limited to the
1802 not "framebuffer complete" (see section 4.4.4.2)."
1809 If SAMPLE_BUFFERS for the read framebuffer is greater than zero and
1810 SAMPLE_BUFFERS for the draw framebuffer is zero, the samples
1814 If SAMPLE_BUFFERS for the read framebuffer is zero and
1815 SAMPLE_BUFFERS for the draw framebuffer is greater than zero, the
1822 modification from the read framebuffer to the draw framebuffer.
1832 If SAMPLE_BUFFERS for either the read framebuffer or
1833 draw framebuffer is greater than zero, no copy is performed and an
1845 from) a framebuffer. GL defines two classes of framebuffers:
1847 framebuffers. For each GL context, there is a single framebuffer
1849 framebuffer objects created and managed by the application.
1851 By default, the GL uses the window-system-provided framebuffer. The
1853 to this framebuffer are managed entirely by the window-system.
1854 Consequently, the state of the window-system-provided framebuffer,
1856 window-system-provided framebuffer itself, or its images, be deleted
1861 application-created framebuffer objects.
1863 Application-created framebuffer objects encapsulate the state of a
1864 framebuffer in a similar manner to the way texture objects
1865 encapsulate the state of a texture. In particular, a framebuffer
1869 logical buffer, a framebuffer-attachable image can be attached to
1870 the framebuffer to store the rendered output for that logical
1871 buffer. Examples of framebuffer-attachable images include texture
1876 framebuffer, the GL provides a mechanism to support "off-screen"
1878 attached to a framebuffer, the GL provides a mechanism to support
1883 The default framebuffer for rendering and readback operations is
1884 provided by the window system. In addition, named framebuffer
1886 framebuffer objects is the unsigned integers, with zero reserved
1887 by the GL for the default framebuffer.
1889 A framebuffer object is created by binding
1894 void BindFramebuffer(enum target, uint framebuffer);
1896 with <target> set to the desired framebuffer target and
1897 <framebuffer> set to the framebuffer object name.
1898 The resulting framebuffer
1902 framebuffer, set to the same initial values. There are
1907 framebuffer object to DRAW_FRAMEBUFFER or
1909 to the state of the bound framebuffer object, and any previous
1913 <framebuffer> is not zero or a name returned from a previous call to
1917 If a framebuffer object is bound to DRAW_FRAMEBUFFER or
1920 framebuffer is bound to the corresponding bind point. Calling
1922 framebuffer to both the draw and read targets.
1924 While a framebuffer object is bound, GL operations on the target
1926 framebuffer object, and queries of the target to which it is bound
1930 derived from the framebuffer object bound to DRAW_FRAMEBUFFER.
1933 refers to the default framebuffer.
1934 In order that access to the default framebuffer is not
1935 lost, it is treated as a framebuffer object with the name of zero.
1936 The default framebuffer is therefore rendered to and read from
1938 implementations, the properties of the default framebuffer can
1943 name) differ from the default framebuffer in
1945 default framebuffer, framebuffer objects
1947 framebuffer. Framebuffer-attachable images can be attached to and
1955 created-framebuffer object,
1958 framebuffer objects own all of their pixels.
1965 framebuffer attachment points named COLOR_ATTACHMENT0
1969 framebuffer attachment point DEPTH_ATTACHMENT.
1972 the framebuffer attachment point STENCIL_ATTACHMENT.
1996 <framebuffers> contains <n> names of framebuffer objects to be
1997 deleted. After a framebuffer object is deleted, it has no
1998 attachments, and its name is again unused. If a framebuffer that
2002 <target> and <framebuffer> zero. Unused names in
2009 returns <n> previously unused framebuffer object names in <ids>.
2014 The names bound to the draw and read framebuffer bindings can be
2023 framebuffer objects. In contrast, the image
2024 attachments of the default framebuffer may not be
2027 A single framebuffer-attachable image may be attached to multiple
2028 framebuffer objects, potentially avoiding some
2031 For each logical buffer, a framebuffer object stores a set of
2038 There are two types of framebuffer-attachable images: the image of a
2046 renderbuffer's image to a framebuffer object.
2101 renderbuffer is attached to a framebuffer object (see section
2176 currently bound framebuffer object by calling
2188 one of the attachment points of the framebuffer listed in table
2191 to be attached to the framebuffer. <renderbuffer> must be either
2199 as the logical buffer identified by <attachment> of the framebuffer
2207 attachment to the <attachment> logical buffer of the framebuffer
2208 object bound to framebuffer <target> is broken. If
2210 the state of either the renderbuffer object or the framebuffer
2215 framebuffer currently bound to <target>. All state values of the
2221 framebuffer object to be set to <renderbuffer>, which should have
2225 one or more attachment points in the currently bound framebuffer,
2228 was attached in the currently bound framebuffer. In other words,
2230 in the currently bound framebuffer. Note that the renderbuffer
2248 GL supports copying the rendered contents of the framebuffer into
2255 currently bound framebuffer object by calling one of the following
2274 framebuffer listed in table 1.nnn.
2277 any, will be detached from the framebuffer currently bound to
2291 attached to the framebuffer.
2324 logical buffer identified by <attachment> of the framebuffer
2339 logical buffer of the framebuffer object bound to framebuffer
2342 texture object or the framebuffer object.
2346 framebuffer object to be set to <texture>. <texture> must have base
2348 framebuffer attachments will be incomplete (see section 4.4.4.1).
2367 error, the framebuffer attachment state corresponding to
2373 more attachment points in the currently bound framebuffer, then it
2376 the currently bound framebuffer. In other words, this texture image
2378 framebuffer. Note that the texture image is specifically *not*
2379 detached from any other framebuffer objects. Detaching the texture
2380 image from any other framebuffer objects is the responsibility of
2386 The mechanisms for attaching textures to a framebuffer object do not
2390 framebuffer while the same texture is bound to a texture unit. While
2400 image to the currently bound framebuffer while the texture object is
2405 this scenario, the framebuffer will be considered framebuffer
2415 bound framebuffer at attachment point <A>, and
2458 framebuffer, then the above conditions will not be met, (i.e., the
2464 A framebuffer must be <framebuffer complete> to effectively be used
2465 as the draw or read framebuffer of the GL.
2467 The default framebuffer is always complete if it exists; however, if no
2468 default framebuffer exists (no window system-provided drawable is
2471 A framebuffer object is said to be framebuffer complete if all of
2472 its attached images, and all framebuffer parameters required to
2473 utilize the framebuffer for rendering and reading, are consistently
2475 framebuffer completeness are dependent on the properties of the
2480 completeness of the framebuffer, so it is useful to first define the
2507 framebuffer attachment point <attachment> is not NONE, then it is
2508 said that a framebuffer-attachable image, named <image>, is attached
2509 to the framebuffer at the attachment point. <image> is identified
2512 The framebuffer attachment point <attachment> is said to be
2513 <framebuffer attachment complete> if the value of
2545 The framebuffer object <target> is said to be "framebuffer complete" if
2548 * <target> is the default framebuffer, and the default framebuffer
2552 * All framebuffer attachment points are framebuffer attachment
2556 * There is at least one image attached to the framebuffer.
2578 The token in { brackets } after each clause of the framebuffer
2586 framebuffer is considered complete or incomplete.
2588 - Binding to a different framebuffer with BindFramebuffer.
2590 - Attaching an image to the framebuffer with
2593 - Detaching an image from the framebuffer with
2597 to the framebuffer by calling {Copy|Compressed}TexImage{1D|2D|3D}.
2600 to the framebuffer by calling RenderbufferStorage.
2603 containing an image that is attached to a framebuffer object
2604 that is bound to the framebuffer.
2609 drawable, with the default framebuffer using a window system binding
2613 framebuffer-attachable images, such as texture images and
2616 of formats of the images attached to a framebuffer object are not
2617 supported by the implementation, then the framebuffer is not
2620 for which the framebuffer cannot be FRAMEBUFFER_UNSUPPORTED.
2622 Because of the <implementation-dependent> clause of the framebuffer
2623 completeness test in particular, and because framebuffer
2626 check to see if the framebuffer is complete prior to rendering. The
2627 status of the framebuffer object currently bound to <target> can be
2639 or not the framebuffer bound to <target> is complete, and if not
2640 complete the enum identifies one of the rules of framebuffer
2641 completeness that is violated. If the framebuffer is complete, then
2645 attachments of the currently bound framebuffer object. If the
2646 current DRAW_FRAMEBUFFER_BINDING is not framebuffer complete,
2655 Attempting to render to or read from a framebuffer which is not
2656 framebuffer complete will generate an INVALID_FRAMEBUFFER_OPERATION
2659 commands that read the framebuffer such as ReadPixels and
2661 INVALID_FRAMEBUFFER_OPERATION if called while the framebuffer is
2662 not framebuffer complete.
2669 framebuffer object, or to an image attached to the currently bound
2670 framebuffer object.
2676 framebuffer object is not framebuffer complete, then the values of
2680 framebuffer object is framebuffer complete, then the values of the
2683 framebuffer object, and the state of the images attached to the
2684 currently bound framebuffer object.
2686 defined only if all color attachments of the draw framebuffer have
2690 corresponding attachment of the draw framebuffer, respectively. The
2706 to the framebuffer modifies the image attached to the selected
2707 logical buffer, and an operation that reads from the framebuffer
2737 When an enabled color value is written to the framebuffer while the
2738 draw framebuffer binding is non-zero, for each draw buffer the R, G, B,
2741 format of the framebuffer-attachable image attached to the selected
2749 operation or blending while the read framebuffer binding is non-zero,
2750 the components of the framebuffer-attachable image that is attached to
2819 boolean IsFramebuffer( uint framebuffer );
2821 returns TRUE if <framebuffer> is the name of a framebuffer
2822 object. If <framebuffer> is zero, or if <framebuffer> is a
2823 non-zero value that is not the name of a framebuffer object,
2833 returns information about attachments of a bound framebuffer object.
2837 If the default framebuffer is bound to <target>, then <attachment>
2842 If a framebuffer object is bound to <target>, then <attachment> must
2843 be one of the attachment points of the framebuffer listed in table
2860 NONE, no framebuffer is bound to <target>. In this case
2866 NONE, these queries apply to all other framebuffer types:
2892 modified by ARB_framebuffer_sRGB). For the default framebuffer,
2894 framebuffer objects, components are sRGB-encoded if the internal
2928 Any combinations of framebuffer type and <pname> not described above
3009 draw framebuffer is not framebuffer complete.
3014 read framebuffer is not framebuffer complete.
3135 is non-zero, the read framebuffer is framebuffer complete, and the
3136 value of SAMPLE_BUFFERS for the read framebuffer is greater than
3143 If both the draw and read framebuffers are framebuffer complete and
3149 If both the draw and read framebuffers are framebuffer complete and
3155 If either the draw or read framebuffer is framebuffer complete and
3184 (add new table 3.nnn, "Framebuffer (state per framebuffer target binding point)")
3193 (insert new table 4.nnn, "Framebuffer (state per framebuffer object)")
3209 (insert new table 5.nnn, "Framebuffer (state per framebuffer object attachment point)")
3215 … framebuffer attachment
3220 … framebuffer attachment
3342 add the following new framebuffer dependent state.
3349 when using framebuffer
3441 occurs when the framebuffer object is bound for the first time, a
3442 framebuffer object can be shared across contexts only if it was first
3518 4 CARD32 framebuffer
3659 4 CARD32 framebuffer
3756 // fb - framebuffer object
3769 // Check framebuffer completeness at the end of initialization.
3840 // Check framebuffer completeness at the end of initialization.
3894 // Check framebuffer completeness at the end of initialization.
3943 // Check framebuffer completeness at the end of initialization.
3991 for (each framebuffer-attachable image)
4036 // Current framebuffer is supported and complete!!
4043 // fb - framebuffer object
4057 // Check framebuffer completeness at the end of initialization.
4073 // fb - framebuffer object
4075 // Set up the framebuffer object
4092 // Check framebuffer completeness at the end of initialization.
4115 /* Render to framebuffer object 2 */
4120 * from framebuffer object 2 to framebuffer object 1.
4131 /* Blit contents of color buffer from framebuffer object 1 to
4132 * framebuffer object 2, inverting the image in the X direction.
4141 /* Blit color buffer from framebuffer object 1 to framebuffer
4183 // Check framebuffer completeness at the end of initialization.
4229 * Gen'ed names must be used for framebuffer objects and
4239 images have framebuffer-compatible formats.
4241 * Infolog or other means for communicating framebuffer
4245 * A technique for page flipping framebuffer-attachable images.
4247 * Relaxing framebuffer completeness restrictions, possibly even
4256 * READ_BUFFER == NONE for framebuffer zero.
4259 application-created framebuffer object.
4265 not affect framebuffer completeness. (In
4266 EXT_framebuffer_object, all attachments affected framebuffer
4270 depth and stencil attachments at a framebuffer attachment point.
4271 * Added new queries for framebuffer attachment component type and
4273 * Many other minor tweaks to synchronize with the GL3 framebuffer
4290 framebuffer have identical formats, in which case the color
4307 framebuffer" functions (BindFramebuffer and BindFramebufferEXT). Are
4310 RESOLVED: Yes. Both extensions will create a new framebuffer object
4378 (10) Can ARB framebuffer objects be shared between contexts?
4406 - Explicitly state how framebuffer operations write to and read
4411 - Define the conversions to/from framebuffer in terms of the
4478 - Add framebuffer attachment queries for attachment component
4480 - Allow framebuffer incomplete if no default framebuffer is made
4481 current, with new framebuffer status error.
4482 - Allow multisample buffers in framebuffer objects.
4483 - Global renaming / simplification to "default framebuffer" and
4484 "framebuffer object". Did not yet re-flow those paragraphs for
4494 and draw framebuffer targets. Allow DEPTH_STENCIL_ATTACHMENT
4545 - Add missing framebuffer attachment state for component type /
4549 - Add missing INDEX token for legacy default framebuffer
4595 ARB_framebuffer_object / OpenGL 3.0 API framebuffer objects
4600 OpenGL 3.0 framebuffer objects so that the aliases of the
4604 - Remove STENCIL_REF from list of state moved to become framebuffer