GlVertexAttribPointer(ATTRIB_POSITION, 3, GL_FLOAT, GL_FALSE, 0, 0) GlEnableVertexAttribArray(ATTRIB_NORMAL)

GlEnableVertexAttribArray(ATTRIB_POSITION)

GlBufferData(GL_ARRAY_BUFFER, sizeof(float) * 3 * 6, gVertexNormals, GL_STATIC_DRAW) GlBufferData(GL_ELEMENT_ARRAY_BUFFER, sizeof(GLubyte) * 36, gVertexNormalIndices, GL_STATIC_DRAW) GlBufferData(GL_ARRAY_BUFFER, sizeof(float) * 3 * 8, gVertexPositions, GL_STATIC_DRAW) GlBufferData(GL_ELEMENT_ARRAY_BUFFER, sizeof(GLubyte) * 36, gVertexPositionIndices, GL_STATIC_DRAW) GlBindBuffer(GL_ELEMENT_ARRAY_BUFFER, vboIds) GlBindAttribLocation(program, ATTRIB_NORMAL, 'a_normal') I set vertex attribute state glBindAttribLocation(program, ATTRIB_POSITION, 'a_position') There are 2 arrays (as GL_ARRAY_BUFFERs) - 8 vertices and 6 normals GLfloat gVertexPositions =Ģ arrays of indices (as GL_ELEMENT_ARRAY_BUFFERs) GLubyte gVertexPositionIndices = But what about memory saving (what is purpose of glDrawElements)? I will illustrate problem that I faced. While I was writing question, I got that I can't send more then one indices array to glDrawElements, so if I use buffers, maybe only last binded GL_ELEMENT_ARRAY_BUFFER is using for drawing. Then things started getting really interesting.In OpenGL (OpenGL ES 2.0) can I use more than one GL_ELEMENT_ARRAY_BUFFER for different GL_ARRAY_BUFFER buffers? I'm reading 'OpenGL ES 2.0 Programming Guide', Chapter 6 'Vertex attributes, arrays and buffer objects', there is source example: there are several GL_ARRAY_BUFFER (for position, normal, texture coords) and one GL_ELEMENT_ARRAY_BUFFER ('used to store element indices'). Khronos recognized the opportunity and began to organize to undertake this new project. With the support of the OpenGL Architecture Board, the industry body responsible for evolving OpenGL for 10 years, 3Dlabs took the idea of defining a subset of OpenGL to the Khronos Group-an open standards consortium working on OpenGL-related standards. As interest quickly grew around 3Dlabs’ idea, the search began for a standards body able to create a 3D graphics API for embedded systems that leveraged the proven strengths of OpenGL-an API that has been used by a huge range of applications from games to CAD systems on a wide variety of workstations and PCs. It soon became clear that there was a widespread industry desire for a small footprint, cross platform API with excellent 2D and 3D functionality, particularly as 3D silicon was rapidly becoming both more capable and significantly cheaper, but such an API simply didn’t exist in 2001. OpenGL ES originated that way-in a modest 3Dlabs project in 2001 that sought to define a standardized subset of OpenGL for a range of embedded systems. Ou say you want a revolution? Well, sometimes the smallest things can create the biggest changes. Dave Durnil For Lissa, whom I ignored when she told me to stop writing these damn books.

Accumulation buffer opengl es 2.0