Sign in to follow this  
wolfscaptain

OpenGL Reduce memory output of 2D tile map

Recommended Posts

wolfscaptain    200
I made a normal 2D tile map code in WebGL some time ago, having 6 vertices consisting of positions and texture coordinates per tile.

The texture coordinates pointed to a specific texture in a dynamically generated texture atlas.

And so, every tile took 96 bytes (12 2D vectors).

This weekend I finally tried instanced rendering in C++, and together with a texture buffer and a texture array, I could render any amount of tiles using merely one byte (index to the texture) per tile, which made the code quite fast, and very small in memory output.

So, I am now thinkig of ways to reduce bandwidth also for pre OpenGL 3 code.

What I have in mind is having a constant matrix in the vertex shader that will hold the four vertex positions that make a unit quad.

Each vertex sent to the shaders, then, will have the tile number it belongs to (32 bits uint), the vertex number in the tile (0, 1, 2 or 3), and the texture number.

The correct vertex position will be selected from the constant matrix;
vec2 position = positiohMatrix[vertexNumber];
With this position two things happen: first, the texture coordinate is set to it, with inversed y value (1 - position.y), and then the tile number is used to move the vertex to its correct place, assuming each tile is one unit, and using a uniform to tell how many tils there are per row.

The texture index and texture coordinate will then move on to the fragment shader.

Here, the correct texture coordinate will be generated using uniforms that tell the size of each texture in the atlas, and then it's a simple texture lookup.

While this should work, each tile is still quite big - 36 bytes (6 per vertex).

I am wondering if someone has better ideas to reduce the memory output.

Thanks :)

Share this post


Link to post
Share on other sites
mhagain    13430
You're going to quickly run out of uniforms if you take that approach (plus possible lack of uint support on older hardware will kill you).

The easiest solution is just to check for the instancing extension and use it if present. NVIDIA, for example, will make more recent functionality available on older hardware via extensions if the hardware is capable of using it, and continue to support parts back to the GeForce 6 line. So even if you've just got GL2.1 you may very well have instancing available - it was originally a SM3 feature in D3D9 (where the feature originally derived from) so it should be available on a relatively wide range of pre-GL3 hardware. Not sure how this applies to WebGL vs desktop GL though, or even if there is a difference.

In cases where it's not you can abuse immediate mode calls to do some pseudo-instancing. Just put a few glVertexAttrib4f calls before you draw and use those for data that's going to be common to everything. In general though that's more suited to more complex geometry and I've read bad things about it on AMD hardware (e.g. [url="http://sol.gfxile.net/instancing.html"]http://sol.gfxile.net/instancing.html[/url]).

The other option is to just accept the increased memory usage. You could be doing an awful lot of work to reduce memory usage which could end up being counterproductive - the overhead of the extra work could more than outweigh any gains from reduced memory usage (which are really going to be quite small anyway - memory usage is typically not a bottleneck any more and hasn't been for quite some time) - the real gain from using instancing comes from reduced draw calls, not reduced memory usage, so make sure that your profiling is giving you the right info (and that you're interpreting it correctly) before proceeding with any drastic surgery.

Share this post


Link to post
Share on other sites
wolfscaptain    200
I wasn't sure if I should write it before, but this isn't really about practicality (where I would rather work on a game than wasting time on optimizations), but rather an experiment.

I did get about 30% FPS boost when testing one draw call with 96 bytes against instancing and using one byte, but we all know how much actual speed in milliseconds that usually turns into (close to nothing). Edited by wolfscaptain

Share this post


Link to post
Share on other sites
mhagain    13430
Ah, well experimentation is good. Always positive stuff about an opportunity to learn with the freedom to make mistakes while doing so. :)

My own opinion is that even a sub-millisecond speed boost can be worthwhile if it makes the difference between hitting or missing a vsync interval, so it's definitely worth shooting for.

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 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
    • By C0dR
      I would like to introduce the first version of my physically based camera rendering library, written in C++, called PhysiCam.
      Physicam is an open source OpenGL C++ library, which provides physically based camera rendering and parameters. It is based on OpenGL and designed to be used as either static library or dynamic library and can be integrated in existing applications.
       
      The following features are implemented:
      Physically based sensor and focal length calculation Autoexposure Manual exposure Lense distortion Bloom (influenced by ISO, Shutter Speed, Sensor type etc.) Bokeh (influenced by Aperture, Sensor type and focal length) Tonemapping  
      You can find the repository at https://github.com/0x2A/physicam
       
      I would be happy about feedback, suggestions or contributions.

  • Popular Now