2009-03-30 12:07:31 -04:00
|
|
|
/*
|
|
|
|
* Cogl
|
|
|
|
*
|
2009-04-27 10:48:12 -04:00
|
|
|
* An object oriented GL/GLES Abstraction/Utility Layer
|
2009-03-30 12:07:31 -04:00
|
|
|
*
|
2009-04-27 10:48:12 -04:00
|
|
|
* Copyright (C) 2007,2008,2009 Intel Corporation.
|
2009-03-30 12:07:31 -04:00
|
|
|
*
|
|
|
|
* This library is free software; you can redistribute it and/or
|
|
|
|
* modify it under the terms of the GNU Lesser General Public
|
|
|
|
* License as published by the Free Software Foundation; either
|
|
|
|
* version 2 of the License, or (at your option) any later version.
|
|
|
|
*
|
|
|
|
* This library is distributed in the hope that it will be useful,
|
|
|
|
* but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
|
|
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
|
|
|
|
* Lesser General Public License for more details.
|
|
|
|
*
|
|
|
|
* You should have received a copy of the GNU Lesser General Public
|
|
|
|
* License along with this library; if not, write to the
|
|
|
|
* Free Software Foundation, Inc., 59 Temple Place - Suite 330,
|
|
|
|
* Boston, MA 02111-1307, USA.
|
|
|
|
*/
|
|
|
|
|
|
|
|
#ifdef HAVE_CONFIG_H
|
|
|
|
#include "config.h"
|
|
|
|
#endif
|
|
|
|
|
|
|
|
#include "cogl.h"
|
|
|
|
|
|
|
|
#include <string.h>
|
|
|
|
#include <math.h>
|
|
|
|
#include <stdlib.h>
|
|
|
|
|
|
|
|
#ifdef HAVE_CLUTTER_GLX
|
|
|
|
#include <dlfcn.h>
|
|
|
|
#include <GL/glx.h>
|
|
|
|
|
|
|
|
typedef CoglFuncPtr (*GLXGetProcAddressProc) (const guint8 *procName);
|
|
|
|
#endif
|
|
|
|
|
2009-05-19 09:44:29 -04:00
|
|
|
#include "cogl-debug.h"
|
2009-03-30 12:07:31 -04:00
|
|
|
#include "cogl-internal.h"
|
|
|
|
#include "cogl-util.h"
|
|
|
|
#include "cogl-context.h"
|
2009-05-23 12:42:10 -04:00
|
|
|
#include "cogl-material-private.h"
|
2009-03-30 12:07:31 -04:00
|
|
|
|
|
|
|
#if defined (HAVE_COGL_GLES2) || defined (HAVE_COGL_GLES)
|
|
|
|
#include "cogl-gles2-wrapper.h"
|
|
|
|
#endif
|
|
|
|
|
2009-05-19 09:44:29 -04:00
|
|
|
#ifdef COGL_GL_DEBUG
|
2009-03-30 12:07:31 -04:00
|
|
|
/* GL error to string conversion */
|
2009-05-18 14:38:03 -04:00
|
|
|
static const struct {
|
|
|
|
GLuint error_code;
|
|
|
|
const gchar *error_string;
|
|
|
|
} gl_errors[] = {
|
|
|
|
{ GL_NO_ERROR, "No error" },
|
|
|
|
{ GL_INVALID_ENUM, "Invalid enumeration value" },
|
|
|
|
{ GL_INVALID_VALUE, "Invalid value" },
|
|
|
|
{ GL_INVALID_OPERATION, "Invalid operation" },
|
|
|
|
{ GL_STACK_OVERFLOW, "Stack overflow" },
|
|
|
|
{ GL_STACK_UNDERFLOW, "Stack underflow" },
|
|
|
|
{ GL_OUT_OF_MEMORY, "Out of memory" },
|
2009-03-30 12:07:31 -04:00
|
|
|
|
|
|
|
#ifdef GL_INVALID_FRAMEBUFFER_OPERATION_EXT
|
2009-05-18 14:38:03 -04:00
|
|
|
{ GL_INVALID_FRAMEBUFFER_OPERATION_EXT, "Invalid framebuffer operation" }
|
2009-03-30 12:07:31 -04:00
|
|
|
#endif
|
|
|
|
};
|
|
|
|
|
2009-05-18 14:38:03 -04:00
|
|
|
static const guint n_gl_errors = G_N_ELEMENTS (gl_errors);
|
|
|
|
|
|
|
|
const gchar *
|
|
|
|
cogl_gl_error_to_string (GLenum error_code)
|
2009-03-30 12:07:31 -04:00
|
|
|
{
|
2009-05-18 14:38:03 -04:00
|
|
|
gint i;
|
|
|
|
|
|
|
|
for (i = 0; i < n_gl_errors; i++)
|
|
|
|
{
|
|
|
|
if (gl_errors[i].error_code == error_code)
|
|
|
|
return gl_errors[i].error_string;
|
|
|
|
}
|
|
|
|
|
2009-05-19 09:44:29 -04:00
|
|
|
return "Unknown GL error";
|
2009-03-30 12:07:31 -04:00
|
|
|
}
|
2009-05-19 09:44:29 -04:00
|
|
|
#endif /* COGL_GL_DEBUG */
|
2009-03-30 12:07:31 -04:00
|
|
|
|
|
|
|
void
|
2009-04-24 13:09:52 -04:00
|
|
|
cogl_clear (const CoglColor *color, gulong buffers)
|
2009-03-30 12:07:31 -04:00
|
|
|
{
|
2009-04-24 13:09:52 -04:00
|
|
|
GLbitfield gl_buffers = 0;
|
|
|
|
|
2009-05-19 09:44:29 -04:00
|
|
|
COGL_NOTE (DRAW, "Clear begin");
|
2009-03-30 12:07:31 -04:00
|
|
|
|
2009-05-08 11:32:01 -04:00
|
|
|
cogl_clip_ensure ();
|
|
|
|
|
2009-04-24 13:09:52 -04:00
|
|
|
if (buffers & COGL_BUFFER_BIT_COLOR)
|
|
|
|
{
|
|
|
|
GE( glClearColor (cogl_color_get_red_float (color),
|
|
|
|
cogl_color_get_green_float (color),
|
|
|
|
cogl_color_get_blue_float (color),
|
|
|
|
0.0) );
|
|
|
|
gl_buffers |= GL_COLOR_BUFFER_BIT;
|
|
|
|
}
|
2009-05-19 09:44:29 -04:00
|
|
|
|
2009-04-24 13:09:52 -04:00
|
|
|
if (buffers & COGL_BUFFER_BIT_DEPTH)
|
|
|
|
gl_buffers |= GL_DEPTH_BUFFER_BIT;
|
2009-05-19 09:44:29 -04:00
|
|
|
|
2009-04-24 13:09:52 -04:00
|
|
|
if (buffers & COGL_BUFFER_BIT_STENCIL)
|
|
|
|
gl_buffers |= GL_STENCIL_BUFFER_BIT;
|
|
|
|
|
|
|
|
if (!gl_buffers)
|
|
|
|
{
|
|
|
|
static gboolean shown = FALSE;
|
2009-05-19 09:44:29 -04:00
|
|
|
|
2009-04-24 13:09:52 -04:00
|
|
|
if (!shown)
|
2009-05-19 09:44:29 -04:00
|
|
|
{
|
|
|
|
g_warning ("You should specify at least one auxiliary buffer "
|
|
|
|
"when calling cogl_clear");
|
|
|
|
}
|
|
|
|
|
2009-04-24 13:09:52 -04:00
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
|
|
|
glClear (gl_buffers);
|
2009-05-19 09:44:29 -04:00
|
|
|
|
|
|
|
COGL_NOTE (DRAW, "Clear end");
|
2009-03-30 12:07:31 -04:00
|
|
|
}
|
|
|
|
|
|
|
|
static inline gboolean
|
|
|
|
cogl_toggle_flag (CoglContext *ctx,
|
|
|
|
gulong new_flags,
|
|
|
|
gulong flag,
|
|
|
|
GLenum gl_flag)
|
|
|
|
{
|
|
|
|
/* Toggles and caches a single enable flag on or off
|
|
|
|
* by comparing to current state
|
|
|
|
*/
|
|
|
|
if (new_flags & flag)
|
|
|
|
{
|
|
|
|
if (!(ctx->enable_flags & flag))
|
|
|
|
{
|
|
|
|
GE( glEnable (gl_flag) );
|
|
|
|
ctx->enable_flags |= flag;
|
|
|
|
return TRUE;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
else if (ctx->enable_flags & flag)
|
|
|
|
{
|
|
|
|
GE( glDisable (gl_flag) );
|
|
|
|
ctx->enable_flags &= ~flag;
|
|
|
|
}
|
|
|
|
|
|
|
|
return FALSE;
|
|
|
|
}
|
|
|
|
|
|
|
|
static inline gboolean
|
|
|
|
cogl_toggle_client_flag (CoglContext *ctx,
|
|
|
|
gulong new_flags,
|
|
|
|
gulong flag,
|
|
|
|
GLenum gl_flag)
|
|
|
|
{
|
|
|
|
/* Toggles and caches a single client-side enable flag
|
|
|
|
* on or off by comparing to current state
|
|
|
|
*/
|
|
|
|
if (new_flags & flag)
|
|
|
|
{
|
|
|
|
if (!(ctx->enable_flags & flag))
|
|
|
|
{
|
|
|
|
GE( glEnableClientState (gl_flag) );
|
|
|
|
ctx->enable_flags |= flag;
|
|
|
|
return TRUE;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
else if (ctx->enable_flags & flag)
|
|
|
|
{
|
|
|
|
GE( glDisableClientState (gl_flag) );
|
|
|
|
ctx->enable_flags &= ~flag;
|
|
|
|
}
|
|
|
|
|
|
|
|
return FALSE;
|
|
|
|
}
|
|
|
|
|
|
|
|
void
|
|
|
|
cogl_enable (gulong flags)
|
|
|
|
{
|
|
|
|
/* This function essentially caches glEnable state() in the
|
|
|
|
* hope of lessening number GL traffic.
|
|
|
|
*/
|
|
|
|
_COGL_GET_CONTEXT (ctx, NO_RETVAL);
|
|
|
|
|
|
|
|
cogl_toggle_flag (ctx, flags,
|
|
|
|
COGL_ENABLE_BLEND,
|
|
|
|
GL_BLEND);
|
|
|
|
|
|
|
|
cogl_toggle_flag (ctx, flags,
|
|
|
|
COGL_ENABLE_BACKFACE_CULLING,
|
|
|
|
GL_CULL_FACE);
|
|
|
|
|
|
|
|
cogl_toggle_client_flag (ctx, flags,
|
|
|
|
COGL_ENABLE_VERTEX_ARRAY,
|
|
|
|
GL_VERTEX_ARRAY);
|
|
|
|
|
|
|
|
cogl_toggle_client_flag (ctx, flags,
|
|
|
|
COGL_ENABLE_COLOR_ARRAY,
|
|
|
|
GL_COLOR_ARRAY);
|
|
|
|
}
|
|
|
|
|
|
|
|
gulong
|
|
|
|
cogl_get_enable ()
|
|
|
|
{
|
|
|
|
_COGL_GET_CONTEXT (ctx, 0);
|
|
|
|
|
|
|
|
return ctx->enable_flags;
|
|
|
|
}
|
|
|
|
|
|
|
|
void
|
2009-05-26 11:55:11 -04:00
|
|
|
cogl_set_depth_test_enabled (gboolean setting)
|
2009-03-30 12:07:31 -04:00
|
|
|
{
|
[cogl] Improving Cogl journal to minimize driver overheads + GPU state changes
Previously the journal was always flushed at the end of
_cogl_rectangles_with_multitexture_coords, (i.e. the end of any
cogl_rectangle* calls) but now we have broadened the potential for batching
geometry. In ideal circumstances we will only flush once per scene.
In summary the journal works like this:
When you use any of the cogl_rectangle* APIs then nothing is emitted to the
GPU at this point, we just log one or more quads into the journal. A
journal entry consists of the quad coordinates, an associated material
reference, and a modelview matrix. Ideally the journal only gets flushed
once at the end of a scene, but in fact there are things to consider that
may cause unwanted flushing, including:
- modifying materials mid-scene
This is because each quad in the journal has an associated material
reference (i.e. not copy), so if you try and modify a material that is
already referenced in the journal we force a flush first)
NOTE: For now this means you should avoid using cogl_set_source_color()
since that currently uses a single shared material. Later we
should change it to use a pool of materials that is recycled
when the journal is flushed.
- modifying any state that isn't currently logged, such as depth, fog and
backface culling enables.
The first thing that happens when flushing, is to upload all the vertex data
associated with the journal into a single VBO.
We then go through a process of splitting up the journal into batches that
have compatible state so they can be emitted to the GPU together. This is
currently broken up into 3 levels so we can stagger the state changes:
1) we break the journal up according to changes in the number of material layers
associated with logged quads. The number of layers in a material determines
the stride of the associated vertices, so we have to update our vertex
array offsets at this level. (i.e. calling gl{Vertex,Color},Pointer etc)
2) we further split batches up according to material compatability. (e.g.
materials with different textures) We flush material state at this level.
3) Finally we split batches up according to modelview changes. At this level
we update the modelview matrix and actually emit the actual draw command.
This commit is largely about putting the initial design in-place; this will be
followed by other changes that take advantage of the extended batching.
2009-06-17 13:46:42 -04:00
|
|
|
/* Currently the journal can't track changes to depth state... */
|
|
|
|
_cogl_journal_flush ();
|
|
|
|
|
2009-03-30 12:07:31 -04:00
|
|
|
if (setting)
|
|
|
|
{
|
|
|
|
glEnable (GL_DEPTH_TEST);
|
|
|
|
glDepthFunc (GL_LEQUAL);
|
|
|
|
}
|
|
|
|
else
|
2009-05-26 11:55:11 -04:00
|
|
|
glDisable (GL_DEPTH_TEST);
|
|
|
|
}
|
|
|
|
|
|
|
|
gboolean
|
|
|
|
cogl_get_depth_test_enabled (void)
|
|
|
|
{
|
|
|
|
return glIsEnabled (GL_DEPTH_TEST) == GL_TRUE ? TRUE : FALSE;
|
2009-03-30 12:07:31 -04:00
|
|
|
}
|
|
|
|
|
|
|
|
void
|
2009-05-26 11:55:11 -04:00
|
|
|
cogl_set_backface_culling_enabled (gboolean setting)
|
2009-03-30 12:07:31 -04:00
|
|
|
{
|
|
|
|
_COGL_GET_CONTEXT (ctx, NO_RETVAL);
|
|
|
|
|
[cogl] Improving Cogl journal to minimize driver overheads + GPU state changes
Previously the journal was always flushed at the end of
_cogl_rectangles_with_multitexture_coords, (i.e. the end of any
cogl_rectangle* calls) but now we have broadened the potential for batching
geometry. In ideal circumstances we will only flush once per scene.
In summary the journal works like this:
When you use any of the cogl_rectangle* APIs then nothing is emitted to the
GPU at this point, we just log one or more quads into the journal. A
journal entry consists of the quad coordinates, an associated material
reference, and a modelview matrix. Ideally the journal only gets flushed
once at the end of a scene, but in fact there are things to consider that
may cause unwanted flushing, including:
- modifying materials mid-scene
This is because each quad in the journal has an associated material
reference (i.e. not copy), so if you try and modify a material that is
already referenced in the journal we force a flush first)
NOTE: For now this means you should avoid using cogl_set_source_color()
since that currently uses a single shared material. Later we
should change it to use a pool of materials that is recycled
when the journal is flushed.
- modifying any state that isn't currently logged, such as depth, fog and
backface culling enables.
The first thing that happens when flushing, is to upload all the vertex data
associated with the journal into a single VBO.
We then go through a process of splitting up the journal into batches that
have compatible state so they can be emitted to the GPU together. This is
currently broken up into 3 levels so we can stagger the state changes:
1) we break the journal up according to changes in the number of material layers
associated with logged quads. The number of layers in a material determines
the stride of the associated vertices, so we have to update our vertex
array offsets at this level. (i.e. calling gl{Vertex,Color},Pointer etc)
2) we further split batches up according to material compatability. (e.g.
materials with different textures) We flush material state at this level.
3) Finally we split batches up according to modelview changes. At this level
we update the modelview matrix and actually emit the actual draw command.
This commit is largely about putting the initial design in-place; this will be
followed by other changes that take advantage of the extended batching.
2009-06-17 13:46:42 -04:00
|
|
|
/* Currently the journal can't track changes to backface culling state... */
|
|
|
|
_cogl_journal_flush ();
|
|
|
|
|
2009-03-30 12:07:31 -04:00
|
|
|
ctx->enable_backface_culling = setting;
|
|
|
|
}
|
|
|
|
|
2009-05-26 11:55:11 -04:00
|
|
|
gboolean
|
|
|
|
cogl_get_backface_culling_enabled (void)
|
|
|
|
{
|
|
|
|
_COGL_GET_CONTEXT (ctx, FALSE);
|
|
|
|
|
|
|
|
return ctx->enable_backface_culling;
|
|
|
|
}
|
|
|
|
|
2009-03-30 12:07:31 -04:00
|
|
|
void
|
|
|
|
cogl_set_source_color (const CoglColor *color)
|
|
|
|
{
|
2009-05-09 14:39:01 -04:00
|
|
|
CoglColor premultiplied;
|
|
|
|
|
2009-03-30 12:07:31 -04:00
|
|
|
_COGL_GET_CONTEXT (ctx, NO_RETVAL);
|
|
|
|
|
|
|
|
/* In case cogl_set_source_texture was previously used... */
|
|
|
|
cogl_material_remove_layer (ctx->default_material, 0);
|
|
|
|
|
2009-05-09 14:39:01 -04:00
|
|
|
premultiplied = *color;
|
|
|
|
cogl_color_premultiply (&premultiplied);
|
|
|
|
cogl_material_set_color (ctx->default_material, &premultiplied);
|
|
|
|
|
2009-03-30 12:07:31 -04:00
|
|
|
cogl_set_source (ctx->default_material);
|
|
|
|
}
|
|
|
|
|
|
|
|
static void
|
|
|
|
project_vertex (const CoglMatrix *modelview_matrix,
|
|
|
|
const CoglMatrix *projection_matrix,
|
|
|
|
float *vertex)
|
|
|
|
{
|
|
|
|
int i;
|
|
|
|
|
|
|
|
/* Apply the modelview matrix */
|
|
|
|
cogl_matrix_transform_point (modelview_matrix,
|
|
|
|
&vertex[0], &vertex[1],
|
|
|
|
&vertex[2], &vertex[3]);
|
|
|
|
/* Apply the projection matrix */
|
|
|
|
cogl_matrix_transform_point (projection_matrix,
|
|
|
|
&vertex[0], &vertex[1],
|
|
|
|
&vertex[2], &vertex[3]);
|
|
|
|
/* Convert from homogenized coordinates */
|
|
|
|
for (i = 0; i < 4; i++)
|
|
|
|
vertex[i] /= vertex[3];
|
|
|
|
}
|
|
|
|
|
|
|
|
static void
|
|
|
|
set_clip_plane (GLint plane_num,
|
|
|
|
const float *vertex_a,
|
|
|
|
const float *vertex_b)
|
|
|
|
{
|
|
|
|
#if defined (HAVE_COGL_GLES2) || defined (HAVE_COGL_GLES)
|
|
|
|
GLfloat plane[4];
|
|
|
|
#else
|
|
|
|
GLdouble plane[4];
|
|
|
|
#endif
|
|
|
|
GLfloat angle;
|
|
|
|
CoglMatrix inverse_projection;
|
|
|
|
_COGL_GET_CONTEXT (ctx, NO_RETVAL);
|
|
|
|
|
|
|
|
/* Calculate the angle between the axes and the line crossing the
|
|
|
|
two points */
|
|
|
|
angle = atan2f (vertex_b[1] - vertex_a[1],
|
|
|
|
vertex_b[0] - vertex_a[0]) * (180.0/G_PI);
|
|
|
|
|
|
|
|
_cogl_current_matrix_push ();
|
|
|
|
/* Load the identity matrix and multiply by the reverse of the
|
|
|
|
projection matrix so we can specify the plane in screen
|
|
|
|
coordinates */
|
|
|
|
_cogl_current_matrix_identity ();
|
|
|
|
cogl_matrix_init_from_array (&inverse_projection,
|
|
|
|
ctx->inverse_projection);
|
|
|
|
_cogl_current_matrix_multiply (&inverse_projection);
|
|
|
|
/* Rotate about point a */
|
|
|
|
_cogl_current_matrix_translate (vertex_a[0], vertex_a[1], vertex_a[2]);
|
|
|
|
/* Rotate the plane by the calculated angle so that it will connect
|
|
|
|
the two points */
|
|
|
|
_cogl_current_matrix_rotate (angle, 0.0f, 0.0f, 1.0f);
|
|
|
|
_cogl_current_matrix_translate (-vertex_a[0], -vertex_a[1], -vertex_a[2]);
|
|
|
|
|
2009-07-02 19:34:10 -04:00
|
|
|
_cogl_flush_matrix_stacks ();
|
2009-03-30 12:07:31 -04:00
|
|
|
|
|
|
|
plane[0] = 0;
|
|
|
|
plane[1] = -1.0;
|
|
|
|
plane[2] = 0;
|
|
|
|
plane[3] = vertex_a[1];
|
|
|
|
#if defined (HAVE_COGL_GLES2) || defined (HAVE_COGL_GLES)
|
|
|
|
GE( glClipPlanef (plane_num, plane) );
|
|
|
|
#else
|
|
|
|
GE( glClipPlane (plane_num, plane) );
|
|
|
|
#endif
|
|
|
|
|
|
|
|
_cogl_current_matrix_pop ();
|
|
|
|
}
|
|
|
|
|
|
|
|
void
|
|
|
|
_cogl_set_clip_planes (float x_offset,
|
|
|
|
float y_offset,
|
|
|
|
float width,
|
|
|
|
float height)
|
|
|
|
{
|
|
|
|
CoglMatrix modelview_matrix;
|
|
|
|
CoglMatrix projection_matrix;
|
|
|
|
|
|
|
|
float vertex_tl[4] = { x_offset, y_offset, 0, 1.0 };
|
|
|
|
float vertex_tr[4] = { x_offset + width, y_offset, 0, 1.0 };
|
|
|
|
float vertex_bl[4] = { x_offset, y_offset + height, 0, 1.0 };
|
|
|
|
float vertex_br[4] = { x_offset + width, y_offset + height,
|
|
|
|
0, 1.0 };
|
|
|
|
|
|
|
|
_cogl_get_matrix (COGL_MATRIX_PROJECTION,
|
|
|
|
&projection_matrix);
|
|
|
|
_cogl_get_matrix (COGL_MATRIX_MODELVIEW,
|
|
|
|
&modelview_matrix);
|
|
|
|
|
|
|
|
project_vertex (&modelview_matrix, &projection_matrix, vertex_tl);
|
|
|
|
project_vertex (&modelview_matrix, &projection_matrix, vertex_tr);
|
|
|
|
project_vertex (&modelview_matrix, &projection_matrix, vertex_bl);
|
|
|
|
project_vertex (&modelview_matrix, &projection_matrix, vertex_br);
|
|
|
|
|
|
|
|
/* If the order of the top and bottom lines is different from the
|
|
|
|
order of the left and right lines then the clip rect must have
|
|
|
|
been transformed so that the back is visible. We therefore need
|
|
|
|
to swap one pair of vertices otherwise all of the planes will be
|
|
|
|
the wrong way around */
|
|
|
|
if ((vertex_tl[0] < vertex_tr[0] ? 1 : 0)
|
|
|
|
!= (vertex_bl[1] < vertex_tl[1] ? 1 : 0))
|
|
|
|
{
|
|
|
|
float temp[4];
|
|
|
|
memcpy (temp, vertex_tl, sizeof (temp));
|
|
|
|
memcpy (vertex_tl, vertex_tr, sizeof (temp));
|
|
|
|
memcpy (vertex_tr, temp, sizeof (temp));
|
|
|
|
memcpy (temp, vertex_bl, sizeof (temp));
|
|
|
|
memcpy (vertex_bl, vertex_br, sizeof (temp));
|
|
|
|
memcpy (vertex_br, temp, sizeof (temp));
|
|
|
|
}
|
|
|
|
|
|
|
|
set_clip_plane (GL_CLIP_PLANE0, vertex_tl, vertex_tr);
|
|
|
|
set_clip_plane (GL_CLIP_PLANE1, vertex_tr, vertex_br);
|
|
|
|
set_clip_plane (GL_CLIP_PLANE2, vertex_br, vertex_bl);
|
|
|
|
set_clip_plane (GL_CLIP_PLANE3, vertex_bl, vertex_tl);
|
|
|
|
}
|
|
|
|
|
|
|
|
void
|
|
|
|
_cogl_add_stencil_clip (float x_offset,
|
|
|
|
float y_offset,
|
|
|
|
float width,
|
|
|
|
float height,
|
|
|
|
gboolean first)
|
|
|
|
{
|
[cogl] Improving Cogl journal to minimize driver overheads + GPU state changes
Previously the journal was always flushed at the end of
_cogl_rectangles_with_multitexture_coords, (i.e. the end of any
cogl_rectangle* calls) but now we have broadened the potential for batching
geometry. In ideal circumstances we will only flush once per scene.
In summary the journal works like this:
When you use any of the cogl_rectangle* APIs then nothing is emitted to the
GPU at this point, we just log one or more quads into the journal. A
journal entry consists of the quad coordinates, an associated material
reference, and a modelview matrix. Ideally the journal only gets flushed
once at the end of a scene, but in fact there are things to consider that
may cause unwanted flushing, including:
- modifying materials mid-scene
This is because each quad in the journal has an associated material
reference (i.e. not copy), so if you try and modify a material that is
already referenced in the journal we force a flush first)
NOTE: For now this means you should avoid using cogl_set_source_color()
since that currently uses a single shared material. Later we
should change it to use a pool of materials that is recycled
when the journal is flushed.
- modifying any state that isn't currently logged, such as depth, fog and
backface culling enables.
The first thing that happens when flushing, is to upload all the vertex data
associated with the journal into a single VBO.
We then go through a process of splitting up the journal into batches that
have compatible state so they can be emitted to the GPU together. This is
currently broken up into 3 levels so we can stagger the state changes:
1) we break the journal up according to changes in the number of material layers
associated with logged quads. The number of layers in a material determines
the stride of the associated vertices, so we have to update our vertex
array offsets at this level. (i.e. calling gl{Vertex,Color},Pointer etc)
2) we further split batches up according to material compatability. (e.g.
materials with different textures) We flush material state at this level.
3) Finally we split batches up according to modelview changes. At this level
we update the modelview matrix and actually emit the actual draw command.
This commit is largely about putting the initial design in-place; this will be
followed by other changes that take advantage of the extended batching.
2009-06-17 13:46:42 -04:00
|
|
|
CoglHandle current_source;
|
|
|
|
|
2009-03-30 12:07:31 -04:00
|
|
|
_COGL_GET_CONTEXT (ctx, NO_RETVAL);
|
|
|
|
|
[cogl] Improving Cogl journal to minimize driver overheads + GPU state changes
Previously the journal was always flushed at the end of
_cogl_rectangles_with_multitexture_coords, (i.e. the end of any
cogl_rectangle* calls) but now we have broadened the potential for batching
geometry. In ideal circumstances we will only flush once per scene.
In summary the journal works like this:
When you use any of the cogl_rectangle* APIs then nothing is emitted to the
GPU at this point, we just log one or more quads into the journal. A
journal entry consists of the quad coordinates, an associated material
reference, and a modelview matrix. Ideally the journal only gets flushed
once at the end of a scene, but in fact there are things to consider that
may cause unwanted flushing, including:
- modifying materials mid-scene
This is because each quad in the journal has an associated material
reference (i.e. not copy), so if you try and modify a material that is
already referenced in the journal we force a flush first)
NOTE: For now this means you should avoid using cogl_set_source_color()
since that currently uses a single shared material. Later we
should change it to use a pool of materials that is recycled
when the journal is flushed.
- modifying any state that isn't currently logged, such as depth, fog and
backface culling enables.
The first thing that happens when flushing, is to upload all the vertex data
associated with the journal into a single VBO.
We then go through a process of splitting up the journal into batches that
have compatible state so they can be emitted to the GPU together. This is
currently broken up into 3 levels so we can stagger the state changes:
1) we break the journal up according to changes in the number of material layers
associated with logged quads. The number of layers in a material determines
the stride of the associated vertices, so we have to update our vertex
array offsets at this level. (i.e. calling gl{Vertex,Color},Pointer etc)
2) we further split batches up according to material compatability. (e.g.
materials with different textures) We flush material state at this level.
3) Finally we split batches up according to modelview changes. At this level
we update the modelview matrix and actually emit the actual draw command.
This commit is largely about putting the initial design in-place; this will be
followed by other changes that take advantage of the extended batching.
2009-06-17 13:46:42 -04:00
|
|
|
_cogl_journal_flush ();
|
|
|
|
|
|
|
|
/* temporarily swap in our special stenciling material */
|
|
|
|
current_source = cogl_handle_ref (ctx->source_material);
|
|
|
|
cogl_set_source (ctx->stencil_material);
|
2009-03-30 12:07:31 -04:00
|
|
|
|
|
|
|
if (first)
|
|
|
|
{
|
|
|
|
GE( glEnable (GL_STENCIL_TEST) );
|
|
|
|
|
|
|
|
/* Initially disallow everything */
|
|
|
|
GE( glClearStencil (0) );
|
|
|
|
GE( glClear (GL_STENCIL_BUFFER_BIT) );
|
|
|
|
|
|
|
|
/* Punch out a hole to allow the rectangle */
|
|
|
|
GE( glStencilFunc (GL_NEVER, 0x1, 0x1) );
|
|
|
|
GE( glStencilOp (GL_REPLACE, GL_REPLACE, GL_REPLACE) );
|
|
|
|
|
|
|
|
cogl_rectangle (x_offset, y_offset,
|
|
|
|
x_offset + width, y_offset + height);
|
|
|
|
}
|
|
|
|
else
|
|
|
|
{
|
|
|
|
/* Add one to every pixel of the stencil buffer in the
|
|
|
|
rectangle */
|
|
|
|
GE( glStencilFunc (GL_NEVER, 0x1, 0x3) );
|
|
|
|
GE( glStencilOp (GL_INCR, GL_INCR, GL_INCR) );
|
|
|
|
cogl_rectangle (x_offset, y_offset,
|
|
|
|
x_offset + width, y_offset + height);
|
|
|
|
|
|
|
|
/* Subtract one from all pixels in the stencil buffer so that
|
|
|
|
only pixels where both the original stencil buffer and the
|
|
|
|
rectangle are set will be valid */
|
|
|
|
GE( glStencilOp (GL_DECR, GL_DECR, GL_DECR) );
|
|
|
|
|
|
|
|
_cogl_set_current_matrix (COGL_MATRIX_PROJECTION);
|
|
|
|
_cogl_current_matrix_push ();
|
|
|
|
_cogl_current_matrix_identity ();
|
|
|
|
|
|
|
|
/* Cogl generally assumes the modelview matrix is current, so since
|
|
|
|
* cogl_rectangle will be flushing GL state and emitting geometry
|
|
|
|
* to OpenGL it will be confused if we leave the projection matrix
|
|
|
|
* active... */
|
|
|
|
_cogl_set_current_matrix (COGL_MATRIX_MODELVIEW);
|
|
|
|
_cogl_current_matrix_push ();
|
|
|
|
_cogl_current_matrix_identity ();
|
|
|
|
|
|
|
|
cogl_rectangle (-1.0, -1.0, 1.0, 1.0);
|
|
|
|
|
|
|
|
_cogl_current_matrix_pop ();
|
|
|
|
|
|
|
|
_cogl_set_current_matrix (COGL_MATRIX_PROJECTION);
|
|
|
|
_cogl_current_matrix_pop ();
|
|
|
|
|
|
|
|
_cogl_set_current_matrix (COGL_MATRIX_MODELVIEW);
|
|
|
|
}
|
|
|
|
|
[cogl] Improving Cogl journal to minimize driver overheads + GPU state changes
Previously the journal was always flushed at the end of
_cogl_rectangles_with_multitexture_coords, (i.e. the end of any
cogl_rectangle* calls) but now we have broadened the potential for batching
geometry. In ideal circumstances we will only flush once per scene.
In summary the journal works like this:
When you use any of the cogl_rectangle* APIs then nothing is emitted to the
GPU at this point, we just log one or more quads into the journal. A
journal entry consists of the quad coordinates, an associated material
reference, and a modelview matrix. Ideally the journal only gets flushed
once at the end of a scene, but in fact there are things to consider that
may cause unwanted flushing, including:
- modifying materials mid-scene
This is because each quad in the journal has an associated material
reference (i.e. not copy), so if you try and modify a material that is
already referenced in the journal we force a flush first)
NOTE: For now this means you should avoid using cogl_set_source_color()
since that currently uses a single shared material. Later we
should change it to use a pool of materials that is recycled
when the journal is flushed.
- modifying any state that isn't currently logged, such as depth, fog and
backface culling enables.
The first thing that happens when flushing, is to upload all the vertex data
associated with the journal into a single VBO.
We then go through a process of splitting up the journal into batches that
have compatible state so they can be emitted to the GPU together. This is
currently broken up into 3 levels so we can stagger the state changes:
1) we break the journal up according to changes in the number of material layers
associated with logged quads. The number of layers in a material determines
the stride of the associated vertices, so we have to update our vertex
array offsets at this level. (i.e. calling gl{Vertex,Color},Pointer etc)
2) we further split batches up according to material compatability. (e.g.
materials with different textures) We flush material state at this level.
3) Finally we split batches up according to modelview changes. At this level
we update the modelview matrix and actually emit the actual draw command.
This commit is largely about putting the initial design in-place; this will be
followed by other changes that take advantage of the extended batching.
2009-06-17 13:46:42 -04:00
|
|
|
/* make sure our rectangles hit the stencil buffer before we restore
|
|
|
|
* the stencil function / operation */
|
|
|
|
_cogl_journal_flush ();
|
|
|
|
|
2009-03-30 12:07:31 -04:00
|
|
|
/* Restore the stencil mode */
|
|
|
|
GE( glStencilFunc (GL_EQUAL, 0x1, 0x1) );
|
|
|
|
GE( glStencilOp (GL_KEEP, GL_KEEP, GL_KEEP) );
|
[cogl] Improving Cogl journal to minimize driver overheads + GPU state changes
Previously the journal was always flushed at the end of
_cogl_rectangles_with_multitexture_coords, (i.e. the end of any
cogl_rectangle* calls) but now we have broadened the potential for batching
geometry. In ideal circumstances we will only flush once per scene.
In summary the journal works like this:
When you use any of the cogl_rectangle* APIs then nothing is emitted to the
GPU at this point, we just log one or more quads into the journal. A
journal entry consists of the quad coordinates, an associated material
reference, and a modelview matrix. Ideally the journal only gets flushed
once at the end of a scene, but in fact there are things to consider that
may cause unwanted flushing, including:
- modifying materials mid-scene
This is because each quad in the journal has an associated material
reference (i.e. not copy), so if you try and modify a material that is
already referenced in the journal we force a flush first)
NOTE: For now this means you should avoid using cogl_set_source_color()
since that currently uses a single shared material. Later we
should change it to use a pool of materials that is recycled
when the journal is flushed.
- modifying any state that isn't currently logged, such as depth, fog and
backface culling enables.
The first thing that happens when flushing, is to upload all the vertex data
associated with the journal into a single VBO.
We then go through a process of splitting up the journal into batches that
have compatible state so they can be emitted to the GPU together. This is
currently broken up into 3 levels so we can stagger the state changes:
1) we break the journal up according to changes in the number of material layers
associated with logged quads. The number of layers in a material determines
the stride of the associated vertices, so we have to update our vertex
array offsets at this level. (i.e. calling gl{Vertex,Color},Pointer etc)
2) we further split batches up according to material compatability. (e.g.
materials with different textures) We flush material state at this level.
3) Finally we split batches up according to modelview changes. At this level
we update the modelview matrix and actually emit the actual draw command.
This commit is largely about putting the initial design in-place; this will be
followed by other changes that take advantage of the extended batching.
2009-06-17 13:46:42 -04:00
|
|
|
|
|
|
|
/* restore the original source material */
|
|
|
|
cogl_set_source (current_source);
|
|
|
|
cogl_handle_unref (current_source);
|
2009-03-30 12:07:31 -04:00
|
|
|
}
|
|
|
|
|
|
|
|
void
|
|
|
|
_cogl_disable_stencil_buffer (void)
|
|
|
|
{
|
|
|
|
GE( glDisable (GL_STENCIL_TEST) );
|
|
|
|
}
|
|
|
|
|
|
|
|
void
|
|
|
|
_cogl_enable_clip_planes (void)
|
|
|
|
{
|
|
|
|
GE( glEnable (GL_CLIP_PLANE0) );
|
|
|
|
GE( glEnable (GL_CLIP_PLANE1) );
|
|
|
|
GE( glEnable (GL_CLIP_PLANE2) );
|
|
|
|
GE( glEnable (GL_CLIP_PLANE3) );
|
|
|
|
}
|
|
|
|
|
|
|
|
void
|
|
|
|
_cogl_disable_clip_planes (void)
|
|
|
|
{
|
|
|
|
GE( glDisable (GL_CLIP_PLANE3) );
|
|
|
|
GE( glDisable (GL_CLIP_PLANE2) );
|
|
|
|
GE( glDisable (GL_CLIP_PLANE1) );
|
|
|
|
GE( glDisable (GL_CLIP_PLANE0) );
|
|
|
|
}
|
|
|
|
|
2009-07-01 07:57:30 -04:00
|
|
|
/* XXX: This should be deprecated and Cogl should be left to manage
|
|
|
|
* the glViewport automatically when switching draw buffers. */
|
2009-03-30 12:07:31 -04:00
|
|
|
void
|
|
|
|
cogl_viewport (guint width,
|
|
|
|
guint height)
|
|
|
|
{
|
2009-07-01 07:57:30 -04:00
|
|
|
_COGL_GET_CONTEXT (ctx, NO_RETVAL);
|
|
|
|
|
2009-06-25 09:39:57 -04:00
|
|
|
COGL_NOTE (MISC, "glViewport(0, 0, %u, %u)", width, height);
|
2009-03-30 12:07:31 -04:00
|
|
|
GE( glViewport (0, 0, width, height) );
|
2009-07-01 07:57:30 -04:00
|
|
|
|
|
|
|
ctx->viewport_width = width;
|
|
|
|
ctx->viewport_height = height;
|
2009-03-30 12:07:31 -04:00
|
|
|
}
|
|
|
|
|
|
|
|
void
|
2009-05-28 08:03:19 -04:00
|
|
|
_cogl_setup_viewport (guint width,
|
|
|
|
guint height,
|
|
|
|
float fovy,
|
|
|
|
float aspect,
|
|
|
|
float z_near,
|
|
|
|
float z_far)
|
2009-03-30 12:07:31 -04:00
|
|
|
{
|
|
|
|
float z_camera;
|
|
|
|
CoglMatrix projection_matrix;
|
|
|
|
|
2009-07-01 07:57:30 -04:00
|
|
|
cogl_viewport (width, height);
|
2009-03-30 12:07:31 -04:00
|
|
|
|
|
|
|
/* For Ortho projection.
|
2009-05-28 08:03:19 -04:00
|
|
|
* _cogl_current_matrix_ortho (0, width, 0, height, -1, 1);
|
2009-03-30 12:07:31 -04:00
|
|
|
*/
|
|
|
|
|
|
|
|
cogl_perspective (fovy, aspect, z_near, z_far);
|
|
|
|
|
|
|
|
/*
|
|
|
|
* In theory, we can compute the camera distance from screen as:
|
|
|
|
*
|
|
|
|
* 0.5 * tan (FOV)
|
|
|
|
*
|
|
|
|
* However, it's better to compute the z_camera from our projection
|
|
|
|
* matrix so that we get a 1:1 mapping at the screen distance. Consider
|
|
|
|
* the upper-left corner of the screen. It has object coordinates
|
|
|
|
* (0,0,0), so by the transform below, ends up with eye coordinate
|
|
|
|
*
|
|
|
|
* x_eye = x_object / width - 0.5 = - 0.5
|
|
|
|
* y_eye = (height - y_object) / width - 0.5 = 0.5
|
|
|
|
* z_eye = z_object / width - z_camera = - z_camera
|
|
|
|
*
|
|
|
|
* From cogl_perspective(), we know that the projection matrix has
|
|
|
|
* the form:
|
|
|
|
*
|
|
|
|
* (x, 0, 0, 0)
|
|
|
|
* (0, y, 0, 0)
|
|
|
|
* (0, 0, c, d)
|
|
|
|
* (0, 0, -1, 0)
|
|
|
|
*
|
|
|
|
* Applied to the above, we get clip coordinates of
|
|
|
|
*
|
|
|
|
* x_clip = x * (- 0.5)
|
|
|
|
* y_clip = y * 0.5
|
|
|
|
* w_clip = - 1 * (- z_camera) = z_camera
|
|
|
|
*
|
|
|
|
* Dividing through by w to get normalized device coordinates, we
|
|
|
|
* have, x_nd = x * 0.5 / z_camera, y_nd = - y * 0.5 / z_camera.
|
|
|
|
* The upper left corner of the screen has normalized device coordinates,
|
|
|
|
* (-1, 1), so to have the correct 1:1 mapping, we have to have:
|
|
|
|
*
|
|
|
|
* z_camera = 0.5 * x = 0.5 * y
|
|
|
|
*
|
|
|
|
* If x != y, then we have a non-uniform aspect ration, and a 1:1 mapping
|
|
|
|
* doesn't make sense.
|
|
|
|
*/
|
|
|
|
|
|
|
|
cogl_get_projection_matrix (&projection_matrix);
|
|
|
|
z_camera = 0.5 * projection_matrix.xx;
|
|
|
|
|
2009-07-02 19:34:10 -04:00
|
|
|
_cogl_set_current_matrix (COGL_MATRIX_MODELVIEW);
|
2009-03-30 12:07:31 -04:00
|
|
|
_cogl_current_matrix_identity ();
|
|
|
|
_cogl_current_matrix_translate (-0.5f, -0.5f, -z_camera);
|
|
|
|
_cogl_current_matrix_scale (1.0f / width, -1.0f / height, 1.0f / width);
|
|
|
|
_cogl_current_matrix_translate (0.0f, -1.0 * height, 0.0f);
|
|
|
|
}
|
|
|
|
|
|
|
|
CoglFeatureFlags
|
2009-05-28 08:03:19 -04:00
|
|
|
cogl_get_features (void)
|
2009-03-30 12:07:31 -04:00
|
|
|
{
|
|
|
|
_COGL_GET_CONTEXT (ctx, 0);
|
|
|
|
|
|
|
|
if (!ctx->features_cached)
|
|
|
|
_cogl_features_init ();
|
|
|
|
|
2009-06-16 20:46:06 -04:00
|
|
|
if (cogl_debug_flags & COGL_DEBUG_DISABLE_VBOS)
|
|
|
|
ctx->feature_flags &= ~COGL_FEATURE_VBOS;
|
|
|
|
|
2009-03-30 12:07:31 -04:00
|
|
|
return ctx->feature_flags;
|
|
|
|
}
|
|
|
|
|
|
|
|
gboolean
|
|
|
|
cogl_features_available (CoglFeatureFlags features)
|
|
|
|
{
|
|
|
|
_COGL_GET_CONTEXT (ctx, 0);
|
|
|
|
|
|
|
|
if (!ctx->features_cached)
|
|
|
|
_cogl_features_init ();
|
|
|
|
|
|
|
|
return (ctx->feature_flags & features) == features;
|
|
|
|
}
|
|
|
|
|
2009-07-01 07:57:30 -04:00
|
|
|
/* XXX: This function should be deprecated, and replaced with a
|
|
|
|
* cogl_draw_buffer_get_size() API instead. We don't support offset
|
|
|
|
* viewports, and you can't have floating point viewport sizes. */
|
2009-03-30 12:07:31 -04:00
|
|
|
void
|
|
|
|
cogl_get_viewport (float v[4])
|
|
|
|
{
|
2009-07-01 07:57:30 -04:00
|
|
|
_COGL_GET_CONTEXT (ctx, NO_RETVAL);
|
2009-03-30 12:07:31 -04:00
|
|
|
|
2009-07-01 07:57:30 -04:00
|
|
|
v[0] = 0;
|
|
|
|
v[1] = 0;
|
|
|
|
v[2] = ctx->viewport_width;
|
|
|
|
v[3] = ctx->viewport_height;
|
2009-03-30 12:07:31 -04:00
|
|
|
}
|
|
|
|
|
|
|
|
void
|
2009-05-19 09:44:29 -04:00
|
|
|
cogl_get_bitmasks (gint *red,
|
|
|
|
gint *green,
|
|
|
|
gint *blue,
|
|
|
|
gint *alpha)
|
2009-03-30 12:07:31 -04:00
|
|
|
{
|
|
|
|
GLint value;
|
2009-05-19 09:44:29 -04:00
|
|
|
|
2009-03-30 12:07:31 -04:00
|
|
|
if (red)
|
|
|
|
{
|
|
|
|
GE( glGetIntegerv(GL_RED_BITS, &value) );
|
|
|
|
*red = value;
|
|
|
|
}
|
2009-05-19 09:44:29 -04:00
|
|
|
|
2009-03-30 12:07:31 -04:00
|
|
|
if (green)
|
|
|
|
{
|
|
|
|
GE( glGetIntegerv(GL_GREEN_BITS, &value) );
|
|
|
|
*green = value;
|
|
|
|
}
|
2009-05-19 09:44:29 -04:00
|
|
|
|
2009-03-30 12:07:31 -04:00
|
|
|
if (blue)
|
|
|
|
{
|
|
|
|
GE( glGetIntegerv(GL_BLUE_BITS, &value) );
|
|
|
|
*blue = value;
|
|
|
|
}
|
2009-05-19 09:44:29 -04:00
|
|
|
|
2009-03-30 12:07:31 -04:00
|
|
|
if (alpha)
|
|
|
|
{
|
|
|
|
GE( glGetIntegerv(GL_ALPHA_BITS, &value ) );
|
|
|
|
*alpha = value;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
void
|
|
|
|
cogl_set_fog (const CoglColor *fog_color,
|
|
|
|
CoglFogMode mode,
|
|
|
|
float density,
|
|
|
|
float z_near,
|
|
|
|
float z_far)
|
|
|
|
{
|
|
|
|
GLfloat fogColor[4];
|
|
|
|
GLenum gl_mode = GL_LINEAR;
|
|
|
|
|
[cogl] Improving Cogl journal to minimize driver overheads + GPU state changes
Previously the journal was always flushed at the end of
_cogl_rectangles_with_multitexture_coords, (i.e. the end of any
cogl_rectangle* calls) but now we have broadened the potential for batching
geometry. In ideal circumstances we will only flush once per scene.
In summary the journal works like this:
When you use any of the cogl_rectangle* APIs then nothing is emitted to the
GPU at this point, we just log one or more quads into the journal. A
journal entry consists of the quad coordinates, an associated material
reference, and a modelview matrix. Ideally the journal only gets flushed
once at the end of a scene, but in fact there are things to consider that
may cause unwanted flushing, including:
- modifying materials mid-scene
This is because each quad in the journal has an associated material
reference (i.e. not copy), so if you try and modify a material that is
already referenced in the journal we force a flush first)
NOTE: For now this means you should avoid using cogl_set_source_color()
since that currently uses a single shared material. Later we
should change it to use a pool of materials that is recycled
when the journal is flushed.
- modifying any state that isn't currently logged, such as depth, fog and
backface culling enables.
The first thing that happens when flushing, is to upload all the vertex data
associated with the journal into a single VBO.
We then go through a process of splitting up the journal into batches that
have compatible state so they can be emitted to the GPU together. This is
currently broken up into 3 levels so we can stagger the state changes:
1) we break the journal up according to changes in the number of material layers
associated with logged quads. The number of layers in a material determines
the stride of the associated vertices, so we have to update our vertex
array offsets at this level. (i.e. calling gl{Vertex,Color},Pointer etc)
2) we further split batches up according to material compatability. (e.g.
materials with different textures) We flush material state at this level.
3) Finally we split batches up according to modelview changes. At this level
we update the modelview matrix and actually emit the actual draw command.
This commit is largely about putting the initial design in-place; this will be
followed by other changes that take advantage of the extended batching.
2009-06-17 13:46:42 -04:00
|
|
|
/* The cogl journal doesn't currently track fog state changes */
|
|
|
|
_cogl_journal_flush ();
|
|
|
|
|
2009-03-30 12:07:31 -04:00
|
|
|
fogColor[0] = cogl_color_get_red_float (fog_color);
|
|
|
|
fogColor[1] = cogl_color_get_green_float (fog_color);
|
|
|
|
fogColor[2] = cogl_color_get_blue_float (fog_color);
|
|
|
|
fogColor[3] = cogl_color_get_alpha_float (fog_color);
|
|
|
|
|
|
|
|
glEnable (GL_FOG);
|
|
|
|
|
|
|
|
glFogfv (GL_FOG_COLOR, fogColor);
|
|
|
|
|
|
|
|
#if HAVE_COGL_GLES
|
|
|
|
switch (mode)
|
|
|
|
{
|
|
|
|
case COGL_FOG_MODE_LINEAR:
|
|
|
|
gl_mode = GL_LINEAR;
|
|
|
|
break;
|
|
|
|
case COGL_FOG_MODE_EXPONENTIAL:
|
|
|
|
gl_mode = GL_EXP;
|
|
|
|
break;
|
|
|
|
case COGL_FOG_MODE_EXPONENTIAL_SQUARED:
|
|
|
|
gl_mode = GL_EXP2;
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
#endif
|
|
|
|
/* TODO: support other modes for GLES2 */
|
|
|
|
|
|
|
|
/* NB: GLES doesn't have glFogi */
|
|
|
|
glFogf (GL_FOG_MODE, gl_mode);
|
|
|
|
glHint (GL_FOG_HINT, GL_NICEST);
|
|
|
|
|
|
|
|
glFogf (GL_FOG_DENSITY, (GLfloat) density);
|
|
|
|
glFogf (GL_FOG_START, (GLfloat) z_near);
|
|
|
|
glFogf (GL_FOG_END, (GLfloat) z_far);
|
|
|
|
}
|
|
|
|
|
|
|
|
void
|
|
|
|
cogl_disable_fog (void)
|
|
|
|
{
|
[cogl] Improving Cogl journal to minimize driver overheads + GPU state changes
Previously the journal was always flushed at the end of
_cogl_rectangles_with_multitexture_coords, (i.e. the end of any
cogl_rectangle* calls) but now we have broadened the potential for batching
geometry. In ideal circumstances we will only flush once per scene.
In summary the journal works like this:
When you use any of the cogl_rectangle* APIs then nothing is emitted to the
GPU at this point, we just log one or more quads into the journal. A
journal entry consists of the quad coordinates, an associated material
reference, and a modelview matrix. Ideally the journal only gets flushed
once at the end of a scene, but in fact there are things to consider that
may cause unwanted flushing, including:
- modifying materials mid-scene
This is because each quad in the journal has an associated material
reference (i.e. not copy), so if you try and modify a material that is
already referenced in the journal we force a flush first)
NOTE: For now this means you should avoid using cogl_set_source_color()
since that currently uses a single shared material. Later we
should change it to use a pool of materials that is recycled
when the journal is flushed.
- modifying any state that isn't currently logged, such as depth, fog and
backface culling enables.
The first thing that happens when flushing, is to upload all the vertex data
associated with the journal into a single VBO.
We then go through a process of splitting up the journal into batches that
have compatible state so they can be emitted to the GPU together. This is
currently broken up into 3 levels so we can stagger the state changes:
1) we break the journal up according to changes in the number of material layers
associated with logged quads. The number of layers in a material determines
the stride of the associated vertices, so we have to update our vertex
array offsets at this level. (i.e. calling gl{Vertex,Color},Pointer etc)
2) we further split batches up according to material compatability. (e.g.
materials with different textures) We flush material state at this level.
3) Finally we split batches up according to modelview changes. At this level
we update the modelview matrix and actually emit the actual draw command.
This commit is largely about putting the initial design in-place; this will be
followed by other changes that take advantage of the extended batching.
2009-06-17 13:46:42 -04:00
|
|
|
/* Currently the journal can't track changes to fog state... */
|
|
|
|
_cogl_journal_flush ();
|
|
|
|
|
2009-03-30 12:07:31 -04:00
|
|
|
glDisable (GL_FOG);
|
|
|
|
}
|
|
|
|
|
2009-05-23 12:52:18 -04:00
|
|
|
#if 0
|
2009-03-30 12:07:31 -04:00
|
|
|
void
|
|
|
|
cogl_flush_gl_state (int flags)
|
|
|
|
{
|
2009-07-02 19:34:10 -04:00
|
|
|
_cogl_flush_matrix_stacks ();
|
2009-03-30 12:07:31 -04:00
|
|
|
}
|
2009-05-23 12:52:18 -04:00
|
|
|
#endif
|
2009-03-30 12:07:31 -04:00
|
|
|
|
[cogl] Improving Cogl journal to minimize driver overheads + GPU state changes
Previously the journal was always flushed at the end of
_cogl_rectangles_with_multitexture_coords, (i.e. the end of any
cogl_rectangle* calls) but now we have broadened the potential for batching
geometry. In ideal circumstances we will only flush once per scene.
In summary the journal works like this:
When you use any of the cogl_rectangle* APIs then nothing is emitted to the
GPU at this point, we just log one or more quads into the journal. A
journal entry consists of the quad coordinates, an associated material
reference, and a modelview matrix. Ideally the journal only gets flushed
once at the end of a scene, but in fact there are things to consider that
may cause unwanted flushing, including:
- modifying materials mid-scene
This is because each quad in the journal has an associated material
reference (i.e. not copy), so if you try and modify a material that is
already referenced in the journal we force a flush first)
NOTE: For now this means you should avoid using cogl_set_source_color()
since that currently uses a single shared material. Later we
should change it to use a pool of materials that is recycled
when the journal is flushed.
- modifying any state that isn't currently logged, such as depth, fog and
backface culling enables.
The first thing that happens when flushing, is to upload all the vertex data
associated with the journal into a single VBO.
We then go through a process of splitting up the journal into batches that
have compatible state so they can be emitted to the GPU together. This is
currently broken up into 3 levels so we can stagger the state changes:
1) we break the journal up according to changes in the number of material layers
associated with logged quads. The number of layers in a material determines
the stride of the associated vertices, so we have to update our vertex
array offsets at this level. (i.e. calling gl{Vertex,Color},Pointer etc)
2) we further split batches up according to material compatability. (e.g.
materials with different textures) We flush material state at this level.
3) Finally we split batches up according to modelview changes. At this level
we update the modelview matrix and actually emit the actual draw command.
This commit is largely about putting the initial design in-place; this will be
followed by other changes that take advantage of the extended batching.
2009-06-17 13:46:42 -04:00
|
|
|
void
|
2009-06-29 12:10:34 -04:00
|
|
|
cogl_flush (void)
|
[cogl] Improving Cogl journal to minimize driver overheads + GPU state changes
Previously the journal was always flushed at the end of
_cogl_rectangles_with_multitexture_coords, (i.e. the end of any
cogl_rectangle* calls) but now we have broadened the potential for batching
geometry. In ideal circumstances we will only flush once per scene.
In summary the journal works like this:
When you use any of the cogl_rectangle* APIs then nothing is emitted to the
GPU at this point, we just log one or more quads into the journal. A
journal entry consists of the quad coordinates, an associated material
reference, and a modelview matrix. Ideally the journal only gets flushed
once at the end of a scene, but in fact there are things to consider that
may cause unwanted flushing, including:
- modifying materials mid-scene
This is because each quad in the journal has an associated material
reference (i.e. not copy), so if you try and modify a material that is
already referenced in the journal we force a flush first)
NOTE: For now this means you should avoid using cogl_set_source_color()
since that currently uses a single shared material. Later we
should change it to use a pool of materials that is recycled
when the journal is flushed.
- modifying any state that isn't currently logged, such as depth, fog and
backface culling enables.
The first thing that happens when flushing, is to upload all the vertex data
associated with the journal into a single VBO.
We then go through a process of splitting up the journal into batches that
have compatible state so they can be emitted to the GPU together. This is
currently broken up into 3 levels so we can stagger the state changes:
1) we break the journal up according to changes in the number of material layers
associated with logged quads. The number of layers in a material determines
the stride of the associated vertices, so we have to update our vertex
array offsets at this level. (i.e. calling gl{Vertex,Color},Pointer etc)
2) we further split batches up according to material compatability. (e.g.
materials with different textures) We flush material state at this level.
3) Finally we split batches up according to modelview changes. At this level
we update the modelview matrix and actually emit the actual draw command.
This commit is largely about putting the initial design in-place; this will be
followed by other changes that take advantage of the extended batching.
2009-06-17 13:46:42 -04:00
|
|
|
{
|
|
|
|
_cogl_journal_flush ();
|
|
|
|
}
|
|
|
|
|
2009-06-17 09:30:44 -04:00
|
|
|
void
|
|
|
|
cogl_read_pixels (int x,
|
|
|
|
int y,
|
|
|
|
int width,
|
|
|
|
int height,
|
|
|
|
CoglReadPixelsFlags source,
|
|
|
|
CoglPixelFormat format,
|
|
|
|
guint8 *pixels)
|
|
|
|
{
|
|
|
|
GLint viewport[4];
|
|
|
|
GLint viewport_height;
|
|
|
|
int rowstride = width * 4;
|
|
|
|
guint8 temprow[rowstride];
|
|
|
|
|
|
|
|
g_return_if_fail (format == COGL_PIXEL_FORMAT_RGBA_8888);
|
|
|
|
g_return_if_fail (source == COGL_READ_PIXELS_COLOR_BUFFER);
|
|
|
|
|
|
|
|
glGetIntegerv (GL_VIEWPORT, viewport);
|
|
|
|
viewport_height = viewport[3];
|
|
|
|
|
|
|
|
/* The y co-ordinate should be given in OpenGL's coordinate system
|
|
|
|
so 0 is the bottom row */
|
|
|
|
y = viewport_height - y - height;
|
|
|
|
|
|
|
|
/* Setup the pixel store parameters that may have been changed by
|
|
|
|
Cogl */
|
|
|
|
glPixelStorei (GL_PACK_ALIGNMENT, 4);
|
|
|
|
#ifdef HAVE_COGL_GL
|
|
|
|
glPixelStorei (GL_PACK_ROW_LENGTH, 0);
|
|
|
|
glPixelStorei (GL_PACK_SKIP_PIXELS, 0);
|
|
|
|
glPixelStorei (GL_PACK_SKIP_ROWS, 0);
|
|
|
|
#endif /* HAVE_COGL_GL */
|
|
|
|
|
[cogl] Improving Cogl journal to minimize driver overheads + GPU state changes
Previously the journal was always flushed at the end of
_cogl_rectangles_with_multitexture_coords, (i.e. the end of any
cogl_rectangle* calls) but now we have broadened the potential for batching
geometry. In ideal circumstances we will only flush once per scene.
In summary the journal works like this:
When you use any of the cogl_rectangle* APIs then nothing is emitted to the
GPU at this point, we just log one or more quads into the journal. A
journal entry consists of the quad coordinates, an associated material
reference, and a modelview matrix. Ideally the journal only gets flushed
once at the end of a scene, but in fact there are things to consider that
may cause unwanted flushing, including:
- modifying materials mid-scene
This is because each quad in the journal has an associated material
reference (i.e. not copy), so if you try and modify a material that is
already referenced in the journal we force a flush first)
NOTE: For now this means you should avoid using cogl_set_source_color()
since that currently uses a single shared material. Later we
should change it to use a pool of materials that is recycled
when the journal is flushed.
- modifying any state that isn't currently logged, such as depth, fog and
backface culling enables.
The first thing that happens when flushing, is to upload all the vertex data
associated with the journal into a single VBO.
We then go through a process of splitting up the journal into batches that
have compatible state so they can be emitted to the GPU together. This is
currently broken up into 3 levels so we can stagger the state changes:
1) we break the journal up according to changes in the number of material layers
associated with logged quads. The number of layers in a material determines
the stride of the associated vertices, so we have to update our vertex
array offsets at this level. (i.e. calling gl{Vertex,Color},Pointer etc)
2) we further split batches up according to material compatability. (e.g.
materials with different textures) We flush material state at this level.
3) Finally we split batches up according to modelview changes. At this level
we update the modelview matrix and actually emit the actual draw command.
This commit is largely about putting the initial design in-place; this will be
followed by other changes that take advantage of the extended batching.
2009-06-17 13:46:42 -04:00
|
|
|
/* make sure any batched primitives get emitted to the GL driver before
|
|
|
|
* issuing our read pixels... */
|
2009-06-29 12:10:34 -04:00
|
|
|
cogl_flush ();
|
[cogl] Improving Cogl journal to minimize driver overheads + GPU state changes
Previously the journal was always flushed at the end of
_cogl_rectangles_with_multitexture_coords, (i.e. the end of any
cogl_rectangle* calls) but now we have broadened the potential for batching
geometry. In ideal circumstances we will only flush once per scene.
In summary the journal works like this:
When you use any of the cogl_rectangle* APIs then nothing is emitted to the
GPU at this point, we just log one or more quads into the journal. A
journal entry consists of the quad coordinates, an associated material
reference, and a modelview matrix. Ideally the journal only gets flushed
once at the end of a scene, but in fact there are things to consider that
may cause unwanted flushing, including:
- modifying materials mid-scene
This is because each quad in the journal has an associated material
reference (i.e. not copy), so if you try and modify a material that is
already referenced in the journal we force a flush first)
NOTE: For now this means you should avoid using cogl_set_source_color()
since that currently uses a single shared material. Later we
should change it to use a pool of materials that is recycled
when the journal is flushed.
- modifying any state that isn't currently logged, such as depth, fog and
backface culling enables.
The first thing that happens when flushing, is to upload all the vertex data
associated with the journal into a single VBO.
We then go through a process of splitting up the journal into batches that
have compatible state so they can be emitted to the GPU together. This is
currently broken up into 3 levels so we can stagger the state changes:
1) we break the journal up according to changes in the number of material layers
associated with logged quads. The number of layers in a material determines
the stride of the associated vertices, so we have to update our vertex
array offsets at this level. (i.e. calling gl{Vertex,Color},Pointer etc)
2) we further split batches up according to material compatability. (e.g.
materials with different textures) We flush material state at this level.
3) Finally we split batches up according to modelview changes. At this level
we update the modelview matrix and actually emit the actual draw command.
This commit is largely about putting the initial design in-place; this will be
followed by other changes that take advantage of the extended batching.
2009-06-17 13:46:42 -04:00
|
|
|
|
2009-06-17 09:30:44 -04:00
|
|
|
glReadPixels (x, y, width, height, GL_RGBA, GL_UNSIGNED_BYTE, pixels);
|
|
|
|
|
|
|
|
/* TODO: consider using the GL_MESA_pack_invert extension in the future
|
|
|
|
* to avoid this flip... */
|
|
|
|
|
|
|
|
/* vertically flip the buffer in-place */
|
|
|
|
for (y = 0; y < height / 2; y++)
|
|
|
|
{
|
|
|
|
if (y != height - y - 1) /* skip center row */
|
|
|
|
{
|
|
|
|
memcpy (temprow,
|
|
|
|
pixels + y * rowstride, rowstride);
|
|
|
|
memcpy (pixels + y * rowstride,
|
|
|
|
pixels + (height - y - 1) * rowstride, rowstride);
|
|
|
|
memcpy (pixels + (height - y - 1) * rowstride,
|
|
|
|
temprow,
|
|
|
|
rowstride);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2009-06-29 17:32:05 -04:00
|
|
|
void
|
|
|
|
cogl_begin_gl (void)
|
|
|
|
{
|
|
|
|
CoglMaterialFlushOptions options;
|
|
|
|
gulong enable_flags;
|
|
|
|
int i;
|
|
|
|
|
|
|
|
_COGL_GET_CONTEXT (ctx, NO_RETVAL);
|
|
|
|
|
|
|
|
if (ctx->in_begin_gl_block)
|
|
|
|
{
|
|
|
|
static gboolean shown = FALSE;
|
|
|
|
if (!shown)
|
|
|
|
g_warning ("You should not nest cogl_begin_gl/cogl_end_gl blocks");
|
|
|
|
shown = TRUE;
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
ctx->in_begin_gl_block = TRUE;
|
|
|
|
|
|
|
|
/* Flush all batched primitives */
|
|
|
|
cogl_flush ();
|
|
|
|
|
|
|
|
/* Flush our clipping state to GL */
|
|
|
|
cogl_clip_ensure ();
|
|
|
|
|
|
|
|
/* Flush any client side matrix state */
|
2009-07-02 19:34:10 -04:00
|
|
|
_cogl_flush_matrix_stacks ();
|
2009-06-29 17:32:05 -04:00
|
|
|
|
|
|
|
|
|
|
|
/* Setup the state for the current material */
|
|
|
|
|
|
|
|
/* We considered flushing a specific, minimal material here to try and
|
|
|
|
* simplify the GL state, but decided to avoid special cases and second
|
|
|
|
* guessing what would be actually helpful.
|
|
|
|
*
|
|
|
|
* A user should instead call cogl_set_source_color4ub() before
|
|
|
|
* cogl_begin_gl() to simplify the state flushed.
|
|
|
|
*/
|
|
|
|
options.flags = 0;
|
|
|
|
_cogl_material_flush_gl_state (ctx->source_material, &options);
|
|
|
|
|
|
|
|
/* FIXME: This api is a bit yukky, ideally it will be removed if we
|
|
|
|
* re-work the cogl_enable mechanism */
|
|
|
|
enable_flags |= _cogl_material_get_cogl_enable_flags (ctx->source_material);
|
|
|
|
|
|
|
|
if (ctx->enable_backface_culling)
|
|
|
|
enable_flags |= COGL_ENABLE_BACKFACE_CULLING;
|
|
|
|
|
|
|
|
cogl_enable (enable_flags);
|
|
|
|
|
|
|
|
/* Disable all client texture coordinate arrays */
|
|
|
|
for (i = 0; i < ctx->n_texcoord_arrays_enabled; i++)
|
|
|
|
{
|
|
|
|
GE (glClientActiveTexture (GL_TEXTURE0 + i));
|
|
|
|
GE (glDisableClientState (GL_TEXTURE_COORD_ARRAY));
|
|
|
|
}
|
|
|
|
ctx->n_texcoord_arrays_enabled = 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
void
|
|
|
|
cogl_end_gl (void)
|
|
|
|
{
|
|
|
|
_COGL_GET_CONTEXT (ctx, NO_RETVAL);
|
|
|
|
|
|
|
|
if (!ctx->in_begin_gl_block)
|
|
|
|
{
|
|
|
|
static gboolean shown = FALSE;
|
|
|
|
if (!shown)
|
|
|
|
g_warning ("cogl_end_gl is being called before cogl_begin_gl");
|
|
|
|
shown = TRUE;
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
ctx->in_begin_gl_block = FALSE;
|
|
|
|
}
|
|
|
|
|