• Advertisement
Sign in to follow this  

OpenGL Different speeds on different pc's all using Windows

This topic is 2351 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 made a program that has some moving objects, It seemed that they were moving a bit slow in the beginning since their moving vectors where quite big in relation to their positions, but I thought it was some openGL limiter or something. When I started mailing my friends(windows users) the link to the zipped file (which contains the .exe and the glut32.dll and a readme.txt) some of them said the it looks cool, and others said that the balls where spinning VERY fast.

I then thought it can't be because there pc's are that much faster, it had to be some setting. I've been reading about "vsync" and the "wgl" functions that can be used to set vsync, but some guys on these forums say that you should not change "vsync" unless you really need to. I this a good enough reason? to have my program run at the same speed on all windows computers, is very important to me, and I don't want to ask everbody to go change some setting in the control panel or graphics card options. I want to tell the program exactly how to look and how fast the objects must move in the code in a legit way.

If I do understand vsync and it is not to taboo to set it to "0", I would like to turn it of, so that the program draws as fast as it possibly can, and I can decrease my movement vectors, for even smaller position changes more often. Is this the right way of reasoning?

Here is the link I was forwarding to my friends:

The program code is very basic, maths, vectors, matrix stuff, trig. It uses double buffering, and glSwapbuffers at the end of my display function. I also use the following functions:
glutGameModeString( "1280×1024:32@75" );

Please. Go easy on me.


Share this post

Link to post
Share on other sites
For beginner projects, you should simply update your object positions/rotation passing the time difference (deltaT) since last frame and calculate all movement accordingly, then render after every update. It will allow you to go as fast as you can, while keeping the same speed everywhere.

Problem is, in complex physic libraries (PhysX, Box2D, Bullet, etc), you can't do that. Since the deltaT between frames will be highly variable depending on the computer power, it's called "variable timesteps", and you could happens to lose some precision. As an example, the player might be able to jump slightly higher on one machine than the other. People might even take advantage of that and create lag spikes to get hard to reach secrets.

Physics engine recommend to fix your timestep to a certain number (let's say 60hz, so 60 frames per second, fixed). Problem with implementing this method directly is that your rendering will be fixed too, and if the computer is fast enough it will render the 60 frames in a few milliseconds, then wait the whole second before starting the new batch, hence a jerking effect.

The real solution is fix the physic, and allow rendering as fast you can. To do it, you use an accumulator (see lot of threads about that, I got to agree none are very clear to understand). If the physic is not calculated fast enough, you can skip rendering frames between physic updates, if the physics is fast enough you have spare time to render multiple frames between physic update. To allow smoother movement between physic updates, you need a position/rotation interpolation between the two physic steps.

Hope I did not make the matter more complicated than it was :)

edit: As for the vsync, it should be an user option more than anything, you don't force it on or off, it's always over-writable in the graphic card drivers anyway. If you render faster than the vsync rate and it's enabled, it will work (cap the frames, remove tearing) without the programmer needing to do anything.

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?
    • 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