SDL_GL_SetAttribute(SDL_GL_DEPTH_SIZE, 24) SDL_GL_SetAttribute(SDL_GL_DOUBLEBUFFER, 1)

SDL_GL_SetAttribute(SDL_GL_ACCELERATED_VISUAL, 1) SDL_GL_SetAttribute(SDL_GL_CONTEXT_MINOR_VERSION, 0) SDL_GL_SetAttribute(SDL_GL_CONTEXT_MAJOR_VERSION, 2) SDL_GL_SetAttribute(SDL_GL_CONTEXT_PROFILE_MASK, SDL_GL_CONTEXT_PROFILE_ES) SDL_LogSetAllPriority(SDL_LOG_PRIORITY_VERBOSE) I've stripped out all of my rendering code and have gone back to basics - rendering a textured square (in a not particularly optimised manner). 64圆4, 128x128, 256x256 etc.) or some wacky compression stuff which doesn't apply here. While there are similar problems on the net, much of it involves ES 1.0 and regards a different issue - texture dimensions not being powers of two (e.g. This is OpenGL ES 2.0, doing an SDL/C++/ndk thing. Textures are being loaded okay, but they're not being rendered - not the usual black squares you often get with OpenGL when something goes wrong - nothing at all. I've since got ahold of one of the offending tablets (a Samsung Galaxy Tab 2 7.0) and it turns out it does run, it just wasn't rendering things properly.Ī few digs later and I've discovered that it's a texturing issue. Sign up to my newsletter and get OpenGL development tips.I recently published a game for Android (/store/apps/details?id=com.quackers if you want to witness the problems first hand), and initial feedback suggests that the thing doesn't run properly on some devices. I hope this helps in case you plan to port your OpenGL ES 2.0 project to use OpenGL ES 3.0 variable that will sent data to framebuffer

For example: Fragment Shader #version 300 es You can now set your own out variable that will sent data to the framebuffer. You no longer need to use gl_FragColor in fragment shaders You can set the location of the vertex attribute by using the following: Vertex Shader #version 300 es Remember how you needed to find the location of a vertex attribute by calling glGetAttribLocation()? That is no longer necessary. You no longer need to find the location of a vertex attribute The keyword out replaces the keyword varying in shaders.įor example: Vertex Shader #version 300 es The keyword in replaces the keyword attribute in vertex shaders. Instead, you now use the keywords in and out. You no longer use the keyword attribute in vertex shaders It turns out that porting an application to OpenGL ES 3.0 is not that complicated. Part of that fear was not knowing answers to questions such as: How much did the OpenGL API changed? Will I have to change all my Shaders? How much will I have to change in the engine? But I was afraid of porting over to this version. I was aware that iOS devices now supported OpenGL ES 3.0. For a long time I focused in using OpenGL ES 2.0 in my game engine.

Opengl es 2.0 devices