Sign in to follow this  
blutzeit

OpenGL Cel-shaded terrain and performance on iOS / OpenGL ES 2.0

Recommended Posts

blutzeit    1650

I'm experimenting with full screen terrain rendering on the iPad, using a cel shader that goes something like this:

1) render the terrain unto screen with cel lighting

2) render the depth only into a texture

3) render this texture unto the screen using a sobel filter

 

The performance of step 1 alone is currently adequate (although I haven't started optimize it yet). But I'm having a little trouble getting good performance when all passes are combined. The depth buffer is apparently rendered twice, which seems unnecessary. Is there any way to combine these passes, or otherwise optimize this approach?

 

[attachment=13699:Landscape.jpg]

Share this post


Link to post
Share on other sites
Ashaman73    13715

Don't know what is supported by OGL ES (multiple render targets ? read depth texture ? etc.) Atleast you could try to write the linear depth into the alpha channel in the first path. 8 bit is not the best resolution, but it could be enough for this kind of low-detail terrain.

Share this post


Link to post
Share on other sites
_Slin_    209

On iPad 2 and later, there is some kind of depth texture format, I am not sure, but I think you can attach it as your framebuffers depth texture target.

I would however expect the outline fullscreen shader to be the bottleneck in your case. So whatever calculations you do on the texture coordinates, do them in your vertex shader and in most cases you should unroll your loops.

Share this post


Link to post
Share on other sites
Krypt0n    4721

output the depth into the alpha channel, it's not very accurate, but enough for your filter.

 

as an optimization for your current 3 phases, swap 1 and 2. it's beneficial, especially on mobile devices, to render one screen in one go, instead of switching from it to a temporary and back, as your GPU needs to store and restore the framebuffer into internal caches. doing it in one go means 67% traffic saving (just one write, instead of write, read, write).

Share this post


Link to post
Share on other sites
L. Spiro    25622

The depth buffer is apparently rendered twice

Because it is already written during pass #1, which makes pass #2 completely superfluous. Just get rid of it.

Additionally, PowerVR chips are different from desktop cards and suffer from fill-rate more than desktops do, so eliminating pass #2 will help a lot, but it also suffers from dependent texture reads more-so than desktop cards do, so as was mentioned by _Slin_ you will want to avoid dependent texture reads (refer to IMAGINE TECHNOLOGY’s documentation) by calculating the texture coordinates you need for your sobel filter in the vertex shader, storing them in only the X and Y of the vectors you pass to the fragment shaders, and in the fragment shaders use those coordinates as-is without modifying them at all.


L. Spiro

Share this post


Link to post
Share on other sites
blutzeit    1650

Thanks for the tips, I've eliminated dependent texture reads, and will continue to experiment with alpha channels.

 

I didn't mention it, but there's a fourth pass where I render the trees using point sprites, which makes it harder to get rid of pass 2. Or is there any way to share the same depth buffer with both screen rendering and the sobel filter that I miss?

Share this post


Link to post
Share on other sites
blutzeit    1650

I managed to get this to work by a lot of optimizing, basically using the original setup.

- Going from sobel to cross filter for faster edge fragment shader (half the number of texture reads). Not as pretty but OK in this context.

- I was sloppily using a lot of fragment discards in many shaders, now I only do a few edge triangles in a special shader.

- Lots of small tweaks as suggested above and in the imgtec document.

 

I didn't use the alpha channel for the depth buffer, it seemed to produce artifacts, and I didn't notice any performance gain (although I'm not sure I did it right). I guess I could do more research to see if this is feasible some how, but the frame rate is ok now so I'm leaving it as a future to-do item.

Share this post


Link to post
Share on other sites
blueshogun96    2264

Still looks pretty darn good to me.  Tbh, I think that this would make a very interesting and educational article.  I often thought about how iOS would handle multiple rendering passes and post processing effects and now I feel encouraged to experiment for myself.

 

I do have a question for you, are you using any CPU based optimizations for your game for your post processing effects or is it all GPU/shader based?  Sorry if I'm missing something obvious.

 

Shogun.

Share this post


Link to post
Share on other sites
blutzeit    1650

It's mainly GPU-based. E.g. I kept moving color/shadow calculations up the chain, and ended up pre-calculating a color-lookup texture, so that the vertex shader does simple normal calculations and feeds the resulting brightness value to the fragment shader to use as color texture coordinate + simple step-based shadow. I'm maybe sacrificing physical realism, but as realistic rendering is not my goal, this isn't an issue.

 

For the discard optimization, I keep two vertex buffers, one for triangles that has fragments that are to be discarded, and one for all-visible fragments. Here it's the CPU that decides for each triangle which buffer it goes into. The buffers are static, so this is done during level load time.

 

As for the edge-filter-pass, it's too much for the original iPad to handle, so it's only used on newer if your running on a newer iPad.

Edited by Felix Ungman

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this  

  • Similar Content

    • By Zaphyk
      I am developing my engine using the OpenGL 3.3 compatibility profile. It runs as expected on my NVIDIA card and on my Intel Card however when I tried it on an AMD setup it ran 3 times worse than on the other setups. Could this be a AMD driver thing or is this probably a problem with my OGL code? Could a different code standard create such bad performance?
    • By Kjell Andersson
      I'm trying to get some legacy OpenGL code to run with a shader pipeline,
      The legacy code uses glVertexPointer(), glColorPointer(), glNormalPointer() and glTexCoordPointer() to supply the vertex information.
      I know that it should be using setVertexAttribPointer() etc to clearly define the layout but that is not an option right now since the legacy code can't be modified to that extent.
      I've got a version 330 vertex shader to somewhat work:
      #version 330 uniform mat4 osg_ModelViewProjectionMatrix; uniform mat4 osg_ModelViewMatrix; layout(location = 0) in vec4 Vertex; layout(location = 2) in vec4 Normal; // Velocity layout(location = 3) in vec3 TexCoord; // TODO: is this the right layout location? out VertexData { vec4 color; vec3 velocity; float size; } VertexOut; void main(void) { vec4 p0 = Vertex; vec4 p1 = Vertex + vec4(Normal.x, Normal.y, Normal.z, 0.0f); vec3 velocity = (osg_ModelViewProjectionMatrix * p1 - osg_ModelViewProjectionMatrix * p0).xyz; VertexOut.velocity = velocity; VertexOut.size = TexCoord.y; gl_Position = osg_ModelViewMatrix * Vertex; } What works is the Vertex and Normal information that the legacy C++ OpenGL code seem to provide in layout location 0 and 2. This is fine.
      What I'm not getting to work is the TexCoord information that is supplied by a glTexCoordPointer() call in C++.
      Question:
      What layout location is the old standard pipeline using for glTexCoordPointer()? Or is this undefined?
       
      Side note: I'm trying to get an OpenSceneGraph 3.4.0 particle system to use custom vertex, geometry and fragment shaders for rendering the particles.
    • By markshaw001
      Hi i am new to this forum  i wanted to ask for help from all of you i want to generate real time terrain using a 32 bit heightmap i am good at c++ and have started learning Opengl as i am very interested in making landscapes in opengl i have looked around the internet for help about this topic but i am not getting the hang of the concepts and what they are doing can some here suggests me some good resources for making terrain engine please for example like tutorials,books etc so that i can understand the whole concept of terrain generation.
       
    • By KarimIO
      Hey guys. I'm trying to get my application to work on my Nvidia GTX 970 desktop. It currently works on my Intel HD 3000 laptop, but on the desktop, every bind textures specifically from framebuffers, I get half a second of lag. This is done 4 times as I have three RGBA textures and one depth 32F buffer. I tried to use debugging software for the first time - RenderDoc only shows SwapBuffers() and no OGL calls, while Nvidia Nsight crashes upon execution, so neither are helpful. Without binding it runs regularly. This does not happen with non-framebuffer binds.
      GLFramebuffer::GLFramebuffer(FramebufferCreateInfo createInfo) { glGenFramebuffers(1, &fbo); glBindFramebuffer(GL_FRAMEBUFFER, fbo); textures = new GLuint[createInfo.numColorTargets]; glGenTextures(createInfo.numColorTargets, textures); GLenum *DrawBuffers = new GLenum[createInfo.numColorTargets]; for (uint32_t i = 0; i < createInfo.numColorTargets; i++) { glBindTexture(GL_TEXTURE_2D, textures[i]); GLint internalFormat; GLenum format; TranslateFormats(createInfo.colorFormats[i], format, internalFormat); // returns GL_RGBA and GL_RGBA glTexImage2D(GL_TEXTURE_2D, 0, internalFormat, createInfo.width, createInfo.height, 0, format, GL_FLOAT, 0); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MAG_FILTER, GL_NEAREST); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MIN_FILTER, GL_NEAREST); DrawBuffers[i] = GL_COLOR_ATTACHMENT0 + i; glBindTexture(GL_TEXTURE_2D, 0); glFramebufferTexture(GL_FRAMEBUFFER, GL_COLOR_ATTACHMENT0 + i, textures[i], 0); } if (createInfo.depthFormat != FORMAT_DEPTH_NONE) { GLenum depthFormat; switch (createInfo.depthFormat) { case FORMAT_DEPTH_16: depthFormat = GL_DEPTH_COMPONENT16; break; case FORMAT_DEPTH_24: depthFormat = GL_DEPTH_COMPONENT24; break; case FORMAT_DEPTH_32: depthFormat = GL_DEPTH_COMPONENT32; break; case FORMAT_DEPTH_24_STENCIL_8: depthFormat = GL_DEPTH24_STENCIL8; break; case FORMAT_DEPTH_32_STENCIL_8: depthFormat = GL_DEPTH32F_STENCIL8; break; } glGenTextures(1, &depthrenderbuffer); glBindTexture(GL_TEXTURE_2D, depthrenderbuffer); glTexImage2D(GL_TEXTURE_2D, 0, depthFormat, createInfo.width, createInfo.height, 0, GL_DEPTH_COMPONENT, GL_FLOAT, 0); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MAG_FILTER, GL_NEAREST); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MIN_FILTER, GL_NEAREST); glBindTexture(GL_TEXTURE_2D, 0); glFramebufferTexture(GL_FRAMEBUFFER, GL_DEPTH_ATTACHMENT, depthrenderbuffer, 0); } if (createInfo.numColorTargets > 0) glDrawBuffers(createInfo.numColorTargets, DrawBuffers); else glDrawBuffer(GL_NONE); if (glCheckFramebufferStatus(GL_FRAMEBUFFER) != GL_FRAMEBUFFER_COMPLETE) std::cout << "Framebuffer Incomplete\n"; glBindFramebuffer(GL_FRAMEBUFFER, 0); width = createInfo.width; height = createInfo.height; } // ... // FBO Creation FramebufferCreateInfo gbufferCI; gbufferCI.colorFormats = gbufferCFs.data(); gbufferCI.depthFormat = FORMAT_DEPTH_32; gbufferCI.numColorTargets = gbufferCFs.size(); gbufferCI.width = engine.settings.resolutionX; gbufferCI.height = engine.settings.resolutionY; gbufferCI.renderPass = nullptr; gbuffer = graphicsWrapper->CreateFramebuffer(gbufferCI); // Bind glBindFramebuffer(GL_DRAW_FRAMEBUFFER, fbo); // Draw here... // Bind to textures glActiveTexture(GL_TEXTURE0); glBindTexture(GL_TEXTURE_2D, textures[0]); glActiveTexture(GL_TEXTURE1); glBindTexture(GL_TEXTURE_2D, textures[1]); glActiveTexture(GL_TEXTURE2); glBindTexture(GL_TEXTURE_2D, textures[2]); glActiveTexture(GL_TEXTURE3); glBindTexture(GL_TEXTURE_2D, depthrenderbuffer); Here is an extract of my code. I can't think of anything else to include. I've really been butting my head into a wall trying to think of a reason but I can think of none and all my research yields nothing. Thanks in advance!
    • By Adrianensis
      Hi everyone, I've shared my 2D Game Engine source code. It's the result of 4 years working on it (and I still continue improving features ) and I want to share with the community. You can see some videos on youtube and some demo gifs on my twitter account.
      This Engine has been developed as End-of-Degree Project and it is coded in Javascript, WebGL and GLSL. The engine is written from scratch.
      This is not a professional engine but it's for learning purposes, so anyone can review the code an learn basis about graphics, physics or game engine architecture. Source code on this GitHub repository.
      I'm available for a good conversation about Game Engine / Graphics Programming
  • Popular Now