• Advertisement
Sign in to follow this  

OpenGL how rendering works?

This topic is 4430 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

i was just wondering. all drawing for opengl prog is down under a function let's say render(); if we wanted to move a single sprite or object we would have to clear the screen, move the object and redraw everything . is this a waste? like just for a single sprite we have to render everything again? this is how i do my coding? is there a better way or this is how all drawing are done? i am not fully understanding the drawing of directx or opengl. as an example, if u create an rpg game and u press left the character animation changes, so I have to redraw the whole map, and the character again. is there a way to draw just the character again only? I find it wasteful to redraw the whole map every time since they don’t' change. or is this how all game rendering works? thx for any comments

Share this post


Link to post
Share on other sites
Advertisement
You have to clear the entire screen because you don't want old renderings to remain on screen. To use your example of an RPG, if you move your character and re-render it, but don't clear the screen and re-render everything else, then the character will still be rendered in its old position.

Share this post


Link to post
Share on other sites
Think of the screen as a painter's canvas. Each pixel can hold a little bit of paint (a combination of red, green, and blue paint to be precise). Now, say the painter want to paint an apple on his canvas. He goes about placing the colors where we feels they should be. In the case of this static painting, everything works out.

Now, let's say that this painter is not happy with the location of the apple he painted. He thinks it should be moved a little more to the left. The painter could simple repaint the apple in another location and it would appear that the apple moved. However, the area of the canvas where the apple used to be still contains the old paint. This is obviously a problem because now it appears that the apple is in two locations. So, the painter now must paint over that old space in order to cover this flaw.

Hopefully you can see from this story that if the painter had instead gotten a new canvas and painted the apple in the new location, he would not have had the problem with the old apple appearing. This is exactly how rendering to the computer screen works. In order to show motion or animation, we do not want to worry about the previous locations of objects still having "paint" on them. Because of this we clear the screen and repaint everything on each frame.

Does that clear things up for you?

Share this post


Link to post
Share on other sites
You could in principle restrict rendering to areas of changes, but it is often complicated to track where and how large these areas are. Moreover, modern games are heavily dynamic, so that it is expected that large portions of the screen will change (think of a camera move as a worst case example in this sense: there _everything_ will change simultaneously). So, in most cases, it is better to clear the screen and make a total new draw.

Share this post


Link to post
Share on other sites
you might think its wastefull however modern hardware is VERY fast when it comes to clearing the screen and they also use this moment to perform a number of per frame setups (certainly the case with the z-buffer, you should ALWAYS clear this)

In short, clearing is a good thing todo.

Share this post


Link to post
Share on other sites
Codewise, this isn't that hard to do either. In your Render function, just clear the screen and draw everything according there current positions. In another function or somewhere else, move everything according to your gameplay physics and input. In most games these days, you won't gain anything trying to only draw what changed. I remember on graphing calculators(TI Series) you could speed it up a little by erasing what was drawn and then drawing the new location, but with the advances in 3d cards, if we do that it will just slow things down due to how rendering is done now. So I can understand where you get the idea from.

Share this post


Link to post
Share on other sites
Sign in to follow this  

  • Advertisement
  • Advertisement
  • Popular Tags

  • Advertisement
  • Popular Now

  • Similar Content

    • By LifeArtist
      Good Evening,
      I want to make a 2D game which involves displaying some debug information. Especially for collision, enemy sights and so on ...
      First of I was thinking about all those shapes which I need will need for debugging purposes: circles, rectangles, lines, polygons.
      I am really stucked right now because of the fundamental question:
      Where do I store my vertices positions for each line (object)? Currently I am not using a model matrix because I am using orthographic projection and set the final position within the VBO. That means that if I add a new line I would have to expand the "points" array and re-upload (recall glBufferData) it every time. The other method would be to use a model matrix and a fixed vbo for a line but it would be also messy to exactly create a line from (0,0) to (100,20) calculating the rotation and scale to make it fit.
      If I proceed with option 1 "updating the array each frame" I was thinking of having 4 draw calls every frame for the lines vao, polygons vao and so on. 
      In addition to that I am planning to use some sort of ECS based architecture. So the other question would be:
      Should I treat those debug objects as entities/components?
      For me it would make sense to treat them as entities but that's creates a new issue with the previous array approach because it would have for example a transform and render component. A special render component for debug objects (no texture etc) ... For me the transform component is also just a matrix but how would I then define a line?
      Treating them as components would'nt be a good idea in my eyes because then I would always need an entity. Well entity is just an id !? So maybe its a component?
      Regards,
      LifeArtist
    • By QQemka
      Hello. I am coding a small thingy in my spare time. All i want to achieve is to load a heightmap (as the lowest possible walking terrain), some static meshes (elements of the environment) and a dynamic character (meaning i can move, collide with heightmap/static meshes and hold a varying item in a hand ). Got a bunch of questions, or rather problems i can't find solution to myself. Nearly all are deal with graphics/gpu, not the coding part. My c++ is on high enough level.
      Let's go:
      Heightmap - i obviously want it to be textured, size is hardcoded to 256x256 squares. I can't have one huge texture stretched over entire terrain cause every pixel would be enormous. Thats why i decided to use 2 specified textures. First will be a tileset consisting of 16 square tiles (u v range from 0 to 0.25 for first tile and so on) and second a 256x256 buffer with 0-15 value representing index of the tile from tileset for every heigtmap square. Problem is, how do i blend the edges nicely and make some computationally cheap changes so its not obvious there are only 16 tiles? Is it possible to generate such terrain with some existing program?
      Collisions - i want to use bounding sphere and aabb. But should i store them for a model or entity instance? Meaning i have 20 same trees spawned using the same tree model, but every entity got its own transformation (position, scale etc). Storing collision component per instance grats faster access + is precalculated and transformed (takes additional memory, but who cares?), so i stick with this, right? What should i do if object is dynamically rotated? The aabb is no longer aligned and calculating per vertex min/max everytime object rotates/scales is pretty expensive, right?
      Drawing aabb - problem similar to above (storing aabb data per instance or model). This time in my opinion per model is enough since every instance also does not have own vertex buffer but uses the shared one (so 20 trees share reference to one tree model). So rendering aabb is about taking the model's aabb, transforming with instance matrix and voila. What about aabb vertex buffer (this is more of a cosmetic question, just curious, bumped onto it in time of writing this). Is it better to make it as 8 points and index buffer (12 lines), or only 2 vertices with min/max x/y/z and having the shaders dynamically generate 6 other vertices and draw the box? Or maybe there should be just ONE 1x1x1 cube box template moved/scaled per entity?
      What if one model got a diffuse texture and a normal map, and other has only diffuse? Should i pass some bool flag to shader with that info, or just assume that my game supports only diffuse maps without fancy stuff?
      There were several more but i forgot/solved them at time of writing
      Thanks in advance
    • By RenanRR
      Hi All,
      I'm reading the tutorials from learnOpengl site (nice site) and I'm having a question on the camera (https://learnopengl.com/Getting-started/Camera).
      I always saw the camera being manipulated with the lookat, but in tutorial I saw the camera being changed through the MVP arrays, which do not seem to be camera, but rather the scene that changes:
      Vertex Shader:
      #version 330 core layout (location = 0) in vec3 aPos; layout (location = 1) in vec2 aTexCoord; out vec2 TexCoord; uniform mat4 model; uniform mat4 view; uniform mat4 projection; void main() { gl_Position = projection * view * model * vec4(aPos, 1.0f); TexCoord = vec2(aTexCoord.x, aTexCoord.y); } then, the matrix manipulated:
      ..... glm::mat4 projection = glm::perspective(glm::radians(fov), (float)SCR_WIDTH / (float)SCR_HEIGHT, 0.1f, 100.0f); ourShader.setMat4("projection", projection); .... glm::mat4 view = glm::lookAt(cameraPos, cameraPos + cameraFront, cameraUp); ourShader.setMat4("view", view); .... model = glm::rotate(model, glm::radians(angle), glm::vec3(1.0f, 0.3f, 0.5f)); ourShader.setMat4("model", model);  
      So, some doubts:
      - Why use it like that?
      - Is it okay to manipulate the camera that way?
      -in this way, are not the vertex's positions that changes instead of the camera?
      - I need to pass MVP to all shaders of object in my scenes ?
       
      What it seems, is that the camera stands still and the scenery that changes...
      it's right?
       
       
      Thank you
       
    • By dpadam450
      Sampling a floating point texture where the alpha channel holds 4-bytes of packed data into the float. I don't know how to cast the raw memory to treat it as an integer so I can perform bit-shifting operations.

      int rgbValue = int(textureSample.w);//4 bytes of data packed as color
      // algorithm might not be correct and endianness might need switching.
      vec3 extractedData = vec3(  rgbValue & 0xFF000000,  (rgbValue << 8) & 0xFF000000, (rgbValue << 16) & 0xFF000000);
      extractedData /= 255.0f;
    • By Devashish Khandelwal
      While writing a simple renderer using OpenGL, I faced an issue with the glGetUniformLocation function. For some reason, the location is coming to be -1.
      Anyone has any idea .. what should I do?
  • Advertisement