• Announcements

    • khawk

      Download the Game Design and Indie Game Marketing Freebook   07/19/17

      GameDev.net and CRC Press have teamed up to bring a free ebook of content curated from top titles published by CRC Press. The freebook, Practices of Game Design & Indie Game Marketing, includes chapters from The Art of Game Design: A Book of Lenses, A Practical Guide to Indie Game Marketing, and An Architectural Approach to Level Design. The GameDev.net FreeBook is relevant to game designers, developers, and those interested in learning more about the challenges in game development. We know game development can be a tough discipline and business, so we picked several chapters from CRC Press titles that we thought would be of interest to you, the GameDev.net audience, in your journey to design, develop, and market your next game. The free ebook is available through CRC Press by clicking here. The Curated Books The Art of Game Design: A Book of Lenses, Second Edition, by Jesse Schell Presents 100+ sets of questions, or different lenses, for viewing a game’s design, encompassing diverse fields such as psychology, architecture, music, film, software engineering, theme park design, mathematics, anthropology, and more. Written by one of the world's top game designers, this book describes the deepest and most fundamental principles of game design, demonstrating how tactics used in board, card, and athletic games also work in video games. It provides practical instruction on creating world-class games that will be played again and again. View it here. A Practical Guide to Indie Game Marketing, by Joel Dreskin Marketing is an essential but too frequently overlooked or minimized component of the release plan for indie games. A Practical Guide to Indie Game Marketing provides you with the tools needed to build visibility and sell your indie games. With special focus on those developers with small budgets and limited staff and resources, this book is packed with tangible recommendations and techniques that you can put to use immediately. As a seasoned professional of the indie game arena, author Joel Dreskin gives you insight into practical, real-world experiences of marketing numerous successful games and also provides stories of the failures. View it here. An Architectural Approach to Level Design This is one of the first books to integrate architectural and spatial design theory with the field of level design. The book presents architectural techniques and theories for level designers to use in their own work. It connects architecture and level design in different ways that address the practical elements of how designers construct space and the experiential elements of how and why humans interact with this space. Throughout the text, readers learn skills for spatial layout, evoking emotion through gamespaces, and creating better levels through architectural theory. View it here. Learn more and download the ebook by clicking here. Did you know? GameDev.net and CRC Press also recently teamed up to bring GDNet+ Members up to a 20% discount on all CRC Press books. Learn more about this and other benefits here.
Sign in to follow this  
Followers 0

Handling resolutions and optimizing? [2D game]

5 posts in this topic

So I've got my nice little 2D game, and I'd like to ask what's the best method for handling resolutions?

Setting glViewPort to my new width and height scales the graphics well enough, but the window size doesn't change, but if I create a new window (and reload the textures) while setting my view port, the graphics don't scale, just remain in the same position with the same size. And if I create a new window without setting the view port the graphics just shift positions (and they do scale) but it doesn't seem like it's working right.

Also, would I ever need to manually scale up the graphics? Because I'm using box2d for the physics and it'd be annoying to have to destroy all box2d objects and create new, scaled versions. Just playing with the view port scales up and down the graphics without any collision problems, just need to get the window to change without any problems as well.

[url="http://pastebin.com/ZD7DFeZR"]My resolution changing class.[/url]

[b]Now question 2: Optimization[/b]

The game runs quite fine at 60 fps normally, but I decided to do some stress tests and tossed about 400 box2d objects with textures, PNG, with alpha and resized falling around, and ones that exit the screen are destroyed and new ones are created (Could have probably done some object pooling I think)

Now capping the FPS at 200, it runs at 60 fps on my above average computer, and about 30 on below average computers. Now I imagined openGL could render far more than 400 moving textures, especially since it can do all that 3D magic, so I'm guessing I'm doing something wrong?

Are there any optimization tips with openGL or "gotchas" ? For example when I first implemented openGL I was creating and destroying textures every time I drew, so that was incredibly laggy. Now I create the texture once, then bind and draw every frame.

Any tips on either of these questions would be appreciated, thanks!

Share this post

Link to post
Share on other sites
1) If you want your graphics to scale when you change resolution you need to change the projection matrix aswell(Which you appear to be doing) and render using a fixed scale that is independant of the resolution. (This should basically make things appear smaller when you increase the resolution)

The rendering shouldn't affect the game simulation in any way. (You can change the scale of objects manually using glScale) (or for newer opengl versions, by modifying the transformation matrix accordingly)

First the big OpenGL one: Immediate mode is "slow", if you're using glbegin / glend you are using immediate mode. (the immediate mode overhead for 400 quads however is fairly negligable and most likely isn't the source of your performance problems).

Secondly, Avoid rebinding textures, state changes are expensive (The driver may or may not ignore redundant statechanges but there is still a cost to attempting them), Try to sort the quads based on which texture they have and render all quads using textureA first, then all quads with textureB etc, only rebind texture when you switch group, combining multiple texture into an atlas (and offsetting the texture coordinates accordingly for the objects) can let you greatly cut down on these changes.

For Box2D:
Try simply moving the objects that fall off the screen to the top instead of destroying them and recreating them, it is quite likely that this is one of the major performance hogs, You could also try running the simulation without actually rendering anything to see how slow it gets when you eliminate the rendering aspect.

Share this post

Link to post
Share on other sites
Those are some really good tips for optimization SimonForsman, I'll try them out as soon as I can. I'm guessing this means making a sprite sheet for animation is better than having a sequence of PNG images? (Even if the sprite sheets are as big as 2000x2000 ?)

About resolutions, so you're saying the way I'm doing it is working the way it should? And that I should append a function to scale the graphics using glScale? (Also, shouldn't the graphics get larger as we increase the resolution?)

Share this post

Link to post
Share on other sites
[quote name='OmarShehata' timestamp='1331473279' post='4921117']
Those are some really good tips for optimization SimonForsman, I'll try them out as soon as I can. I'm guessing this means making a sprite sheet for animation is better than having a sequence of PNG images? (Even if the sprite sheets are as big as 2000x2000 ?)

About resolutions, so you're saying the way I'm doing it is working the way it should? And that I should append a function to scale the graphics using glScale? (Also, shouldn't the graphics get larger as we increase the resolution?)

No, increasing resolution means you get more pixels on screen, if your resolution is 100x100 (very low resolution) and you got an image that is 50x50 that image will occupy 25% of the screen (or window), if you increase the resolution to 200x200 then the 50x50 image will only occupy 6.25% of the screen/window (Thus if you're using fullscreen then increasing resolution will make the graphics appear smaller, if you're using a non fullscreen window then the graphics will keep the same size relative to the monitor but not relative to the window)

If what you want to do is to have objects always occupy the same portion of the screen so that they become larger when you make the window larger then the easiest way is to pass a fixed width and height to your projection matrix (glOrtho doesn't have to take the width and height of the window as parameters, you can pass it for example 800x600 all the time and it will scale the graphics for you so that a 400x300 object always covers 25% of the window) (This will however cause the graphics to stretch if you change the aspect ratio)

Looking at your code again i think the resolution problem you have is simply that you're not using a fullscreen window (And thus its not really a problem as it is working as intended), (If you change the resolution of a normal window you are really changing its size, the actual resolution will still be whatever the desktop resolution is), You shouldn't have to use glScale unless you want to scale the graphics (scaling graphics is useful if you want two objects to use the same mesh but have different sizes).

a 2000x2000 sprite sheet shouldn't be a huge problem for modern graphicscards, older ones however will struggle though:

1) non power of two textures can be slower on old hardware (a 2048x2048 texture will often be faster than a 2000x2000 texture) and square textures are often faster than rectangular textures. newer hardware are better at dealing with odd texture sizes but can still take a serious performance hit.

2) a 2000x2000 texture might be too large for older GPUs to render using hardware acceleration or even at all . (Most new consumer cards will happily handle 4096x4096 while professional cards can often do 8192x8192 textures without problems) , you can create a proxy texture using GL_PROXY_TEXTURE_2D to see if the OpenGL implementation can use a texture of a given size, (For proxy textures the width and height will be set to 0 if the driver is unable to deal with it), there is no guarantee that it will be hardware accelerated though).

Also, you can have a sequence of png images and combine them into one or more larger textures on loadtime if you want. (This can allow you to make optimized texture atlases for each level that only includes the images you need for that specific level, or you can group the most common objects for a level into one atlas).

If for example you use sprite animations where each object always is on the same frame (so that when objectX is on frame1 objectY will also always be on frame1) it could be beneficial to keep all first frames in one texture, all second frames in another, etc (That way you only have to rebind the texture once at the start of each frame and then possibly once more to draw all non animated objects)

Share this post

Link to post
Share on other sites

I've already done a few benchmarks on the stuff you're discussing right now.

First, by compiling all of your textures into one mega-texture (or at least relevant textures), you'll help yourself out a lot. I found that by putting all of my heroes into one giant sprite sheet (which is done at run-time from several sources), you can increase your frame rate a bit. Switching between texture contexts is a somewhat expensive operation, from what I've been told.

I try to compile all textures into relevant layers -- i.e. tiles/world graphics in one might suit your needs; heroes in another; maybe a "monster" one for regional monsters that appear in different areas. Just depends on what you're using. But you can knock down all of the differing calls to glBindTexture() to your sprite sheet once for each layer. i.e. Draw World; Draw Heroes; Draw Monsters. You'd glBindTexture three times.

By doing this (I have a few more layers than that), I jumped my frame-rate pretty drastically. Somewhere around 20-25%. I was rendering a lot of objects, though.

Another note is that the engine I'm working on runs fine on an old netbook (Intel Celeron low voltage processor) with 2048x2048 compiled sprite sheets just fine. The engine also ran fine on an Intel Pentium 4, which supported up to that 2048x2048 texture. These machines did *not* have dedicated GPU's. Of course, I limited how much of the screen was drawn (about 1/2 the real estate -- from 800x600 to 640x480) to maintain frame rates. However, I'm still getting some good frame-rates, so I may jump it back up after using Drawing Arrays. Food for thought.

Share this post

Link to post
Share on other sites
Thanks for the help so far everyone! I really really appreciate it!

I'm still fiddling with the resolution stuff. I've passed a fixed height and width to my glOrtho function as SimonForsman suggested, (960,540 as it's my minimum resolution) and everything's working. The problem is when I go into full screen. Sometimes there will be black strips on the left and right, which makes sense if the game's resolution doesn't match the screen resolution right? The game's aspect ratio is always 16:9. So far so good.

Now testing on a 5:4 monitor, the results are pretty haywire. Pic:


Left: 960x540

The middle picture I think is exactly how it should be working. The game's screen and graphics are not stretched, and there is a black bar at the top (should be half at the top, half at the bottom if I figure out how to center the game screen).

The picture on left isn't stretched, which is good, but it doesn't scale enough. I still don't really think that's a problem.

The problem is with the picture on the right. The game's screen is now stretched. Why would it be stretched? There's no reason for it to be stretched, the aspect ratio hasn't changed.

I'd really like to understand exactly what glOrtho, glViewport and full screen work and why things are doing what they're currently doing. I know glOrtho is the camera, and glViewport is like, the window in which I render things. So my keeping glOrtho a constant size and width, the graphics should never scale right? Or do I need to keep my view port constant as well? But then I'd see a larger area as the screen gets larger...which I don't want. The glViewport should always be 16:9, so why does it stretch?

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  
Followers 0

  • Similar Content

    • By Toastmastern
      So it's been a while since I took a break from my whole creating a planet in DX11. Last time around I got stuck on fixing a nice LOD.
      A week back or so I got help to find this:
      In general this is what I'm trying to recreate in DX11, he that made that planet LOD uses OpenGL but that is a minor issue and something I can solve. But I have a question regarding the code
      He gets the position using this row
      vec4d pos = b.var.vec4d["position"]; Which is then used further down when he sends the variable "center" into the drawing function:
      if (pos.len() < 1) pos.norm(); world::draw(vec3d(pos.x, pos.y, pos.z));  
      Inside the draw function this happens:
      draw_recursive(p3[0], p3[1], p3[2], center); Basically the 3 vertices of the triangle and the center of details that he sent as a parameter earlier: vec3d(pos.x, pos.y, pos.z)
      Now onto my real question, he does vec3d edge_center[3] = { (p1 + p2) / 2, (p2 + p3) / 2, (p3 + p1) / 2 }; to get the edge center of each edge, nothing weird there.
      But this is used later on with:
      vec3d d = center + edge_center[i]; edge_test[i] = d.len() > ratio_size; edge_test is then used to evaluate if there should be a triangle drawn or if it should be split up into 3 new triangles instead. Why is it working for him? shouldn't it be like center - edge_center or something like that? Why adding them togheter? I asume here that the center is the center of details for the LOD. the position of the camera if stood on the ground of the planet and not up int he air like it is now.

      Full code can be seen here:
      If anyone would like to take a look and try to help me understand this code I would love this person. I'm running out of ideas on how to solve this in my own head, most likely twisted it one time to many up in my head
      Thanks in advance
    • By fllwr0491
      I googled around but are unable to find source code or details of implementation.
      What keywords should I search for this topic?
      Things I would like to know:
      A. How to ensure that partially covered pixels are rasterized?
         Apparently by expanding each triangle by 1 pixel or so, rasterization problem is almost solved.
         But it will result in an unindexable triangle list without tons of overlaps. Will it incur a large performance penalty?
      B. A-buffer like bitmask needs a read-modiry-write operation.
         How to ensure proper synchronizations in GLSL?
         GLSL seems to only allow int32 atomics on image.
      C. Is there some simple ways to estimate coverage on-the-fly?
         In case I am to draw 2D shapes onto an exisitng target:
         1. A multi-pass whatever-buffer seems overkill.
         2. Multisampling could cost a lot memory though all I need is better coverage.
            Besides, I have to blit twice, if draw target is not multisampled.
    • By mapra99

      I am working on a recent project and I have been learning how to code in C# using OpenGL libraries for some graphics. I have achieved some quite interesting things using TAO Framework writing in Console Applications, creating a GLUT Window. But my problem now is that I need to incorporate the Graphics in a Windows Form so I can relate the objects that I render with some .NET Controls.

      To deal with this problem, I have seen in some forums that it's better to use OpenTK instead of TAO Framework, so I can use the glControl that OpenTK libraries offer. However, I haven't found complete articles, tutorials or source codes that help using the glControl or that may insert me into de OpenTK functions. Would somebody please share in this forum some links or files where I can find good documentation about this topic? Or may I use another library different of OpenTK?

    • By Solid_Spy
      Hello, I have been working on SH Irradiance map rendering, and I have been using a GLSL pixel shader to render SH irradiance to 2D irradiance maps for my static objects. I already have it working with 9 3D textures so far for the first 9 SH functions.
      In my GLSL shader, I have to send in 9 SH Coefficient 3D Texures that use RGBA8 as a pixel format. RGB being used for the coefficients for red, green, and blue, and the A for checking if the voxel is in use (for the 3D texture solidification shader to prevent bleeding).
      My problem is, I want to knock this number of textures down to something like 4 or 5. Getting even lower would be a godsend. This is because I eventually plan on adding more SH Coefficient 3D Textures for other parts of the game map (such as inside rooms, as opposed to the outside), to circumvent irradiance probe bleeding between rooms separated by walls. I don't want to reach the 32 texture limit too soon. Also, I figure that it would be a LOT faster.
      Is there a way I could, say, store 2 sets of SH Coefficients for 2 SH functions inside a texture with RGBA16 pixels? If so, how would I extract them from inside GLSL? Let me know if you have any suggestions ^^.
    • By KarimIO
      EDIT: I thought this was restricted to Attribute-Created GL contexts, but it isn't, so I rewrote the post.
      Hey guys, whenever I call SwapBuffers(hDC), I get a crash, and I get a "Too many posts were made to a semaphore." from Windows as I call SwapBuffers. What could be the cause of this?
      Update: No crash occurs if I don't draw, just clear and swap.
      static PIXELFORMATDESCRIPTOR pfd = // pfd Tells Windows How We Want Things To Be { sizeof(PIXELFORMATDESCRIPTOR), // Size Of This Pixel Format Descriptor 1, // Version Number PFD_DRAW_TO_WINDOW | // Format Must Support Window PFD_SUPPORT_OPENGL | // Format Must Support OpenGL PFD_DOUBLEBUFFER, // Must Support Double Buffering PFD_TYPE_RGBA, // Request An RGBA Format 32, // Select Our Color Depth 0, 0, 0, 0, 0, 0, // Color Bits Ignored 0, // No Alpha Buffer 0, // Shift Bit Ignored 0, // No Accumulation Buffer 0, 0, 0, 0, // Accumulation Bits Ignored 24, // 24Bit Z-Buffer (Depth Buffer) 0, // No Stencil Buffer 0, // No Auxiliary Buffer PFD_MAIN_PLANE, // Main Drawing Layer 0, // Reserved 0, 0, 0 // Layer Masks Ignored }; if (!(hDC = GetDC(windowHandle))) return false; unsigned int PixelFormat; if (!(PixelFormat = ChoosePixelFormat(hDC, &pfd))) return false; if (!SetPixelFormat(hDC, PixelFormat, &pfd)) return false; hRC = wglCreateContext(hDC); if (!hRC) { std::cout << "wglCreateContext Failed!\n"; return false; } if (wglMakeCurrent(hDC, hRC) == NULL) { std::cout << "Make Context Current Second Failed!\n"; return false; } ... // OGL Buffer Initialization glClear(GL_DEPTH_BUFFER_BIT | GL_COLOR_BUFFER_BIT); glBindVertexArray(vao); glUseProgram(myprogram); glDrawElements(GL_TRIANGLES, indexCount, GL_UNSIGNED_SHORT, (void *)indexStart); SwapBuffers(GetDC(window_handle));  
  • Popular Now