GlBindBuffer(GL_ARRAY_BUFFER, self.vertexBuffer) Indices : (GLushort *) TexturedQuadVAO createVertexArrayObject ') (void) createVertexArrayObject : (TexturedVertex *) vertices _textureUniformLocation = textureUniformLocation UIImage *img = createTextImage(viewSize, text, tSize, font, fgcolor, bgcolor) NSString *colorHexStr = ĬolorGL color = HexidecimalStringToColorGL(colorHexStr) NSInteger jobid = jobidstr = NULL ? -1 : (void) buildNode : (NSDictionary *) nodeDictionary I'm adding vertices to an NSMutableArray because I don't know how many quads there will be. Here is some drawing code for colored quad VAO. I have quite a bit of code so here is some (hopefully) relevant code. and then I start spinning my wheels again with that thought process.

However, since the problem only occurs when I tearDown the scene and rebuild it. I can't figure out whether it is how I am breaking my memory down (even in ARC, I need to release some of it) or if it is how I am creating my VAOs. However, from scene to scene, sometimes the artifacts show up, and sometimes everything looks lovely.

For a particular scene, the occurrence seems to be deterministic every time it is loaded. However for some reason and in no discernible pattern, weird triangles may show up on any subsequent rotation. When the scene is first created, everything looks fine. All of these drawing elements including any shaders and associated arrays of vertices, indices, etc are included in a class, so I just blow away the class each time and do a new alloc/init on rotation. The scene renders a few vertex array objects of regular colored quads and an array of textured vertex array objects. I am rendering a scene that has to get rebuilt whenever there is an orientation change in order to fill the screen appropriately.

Opengl es 2.0 vertex array object