• Advertisement
Sign in to follow this  

OpenGL [edit] choppy panning animation

This topic is 4098 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

hello, I am creating a maximized windowed application (meaning that it plays nice with other windowed application, but occupies the whole screen and does not change the resolution) that pans large textured rectangle (close to 1600x1200) across the screen. My frame rate is decent enough (capped at 35fps), and movement rate is constant. However, the animation is still choppy (it's not unbearable, but just not up to par)... I have the identical app implemented in OpenGL (with frame rate capped at 30) and the animation is far smoother. i logged the application and the biggest difference between the two version is that blt in directx (have to use dx7 for compatibility =/ ) is way slower than SwapBuffers in the opengl version. Whereas swapbuffers takes about 5-15ms per frame, blt/bltfast averages at 25ms. any insights or ideas on why this is the case would be greatly appreciated ^^;; thanks, ~dAviD [Edited by - chpstcks on November 30, 2006 4:02:22 PM]

Share this post


Link to post
Share on other sites
Advertisement
If you're doing it in 3D using textured quads in OpenGL, I think it will almost certainly be faster than blitting using DirectDraw.

Share this post


Link to post
Share on other sites
OpenGL will use hardware for rendering, DirectDraw will almost certainly be software. The equivalent to OpenGL would be Direct3D, not DirectDraw - and you should get performance pretty much identical to OpenGL.

Share this post


Link to post
Share on other sites
Quote:
Original post by Evil Steve
OpenGL will use hardware for rendering, DirectDraw will almost certainly be software. The equivalent to OpenGL would be Direct3D, not DirectDraw - and you should get performance pretty much identical to OpenGL.


hmmm... well, I'm using direct3d to draw quads to the offscreen surface, then blt'ing it to the primary; wasn't aware there's another way to do this.... or am i just confused? o_O

Share this post


Link to post
Share on other sites
Quote:
Original post by chpstcks
Quote:
Original post by Evil Steve
OpenGL will use hardware for rendering, DirectDraw will almost certainly be software. The equivalent to OpenGL would be Direct3D, not DirectDraw - and you should get performance pretty much identical to OpenGL.


hmmm... well, I'm using direct3d to draw quads to the offscreen surface, then blt'ing it to the primary; wasn't aware there's another way to do this.... or am i just confused? o_O
It's been years since I used DDraw - If you're fullscreen, you can flip the surfaces I think. In windowed mode you need to blit the backbuffer to the window, yes.

However, there shouldn't be much of a speed difference between D3D and OpenGL if things are done correctly. I imagine OpenGL has to do something similar to what D3D does behind the scenes too...

Share this post


Link to post
Share on other sites
Quote:
Original post by Evil Steve
It's been years since I used DDraw - If you're fullscreen, you can flip the surfaces I think. In windowed mode you need to blit the backbuffer to the window, yes.

However, there shouldn't be much of a speed difference between D3D and OpenGL if things are done correctly. I imagine OpenGL has to do something similar to what D3D does behind the scenes too...


Right, SwapBuffers does functionally the same thing for OpenGL in Windows as Blt does for directX. My blt speed doesn't seems to be dependent on what i'm blt'ing, but what size the primary surface is... i can blt from a 32x32 back surface to a 1200x1600 front surface (or even a blank screen) and it still takes 25ms. I guess this is expected since it's just copying pixels across buffers... i tried messing around with DDBLTFX struct but doesn't seem to matter >_<

is there any reason to believe using IDirect3DDevice8::Present() will be faster than IDirectDrawSurface7::Blt() ?

Share this post


Link to post
Share on other sites
Yes, because it will render in 3D using 3D Hardware. Let me see if I have this correct: you're using Direct3D to render textured quads to a surface, then using DirectDraw to blit it to the screen? Why not just use Direct3D to render it to the backbuffer?

Share this post


Link to post
Share on other sites
Quote:
Original post by Sc4Freak
Yes, because it will render in 3D using 3D Hardware. Let me see if I have this correct: you're using Direct3D to render textured quads to a surface, then using DirectDraw to blit it to the screen? Why not just use Direct3D to render it to the backbuffer?


i do render the rectangle to the back buffer using direct3D, but i still have to blt it to the primary surface since it's a windowed app. So you guys seem to be suggesting that Blt, even with the right flags set, will use software to render rather than hardware? Doesn't that mean all windowed 3D app before Dx8 used software blitting?? o_O?? just seems so strange...

Share this post


Link to post
Share on other sites
I played with my app some more and was able to reach a frame rate of ~150fps by giving it exclusive access to the screen... but the panning is STILL not smooth!

So this points to a settings problem rather than a blt problem, but i went through all the render states and texture stage states and i just can't get it to pan smoothly >___<

please help~

i have the following set:

m_pd3dDevice->SetRenderState(D3DRENDERSTATE_AMBIENT, 0xffffffff );
m_pd3dDevice->SetRenderState( D3DRENDERSTATE_ANTIALIAS, D3DANTIALIAS_SORTINDEPENDENT );
m_pd3dDevice->SetRenderState(D3DRENDERSTATE_EDGEANTIALIAS , D3DANTIALIAS_SORTINDEPENDENT );
m_pd3dDevice->SetRenderState( D3DRENDERSTATE_TEXTUREPERSPECTIVE, FALSE );

m_pd3dDevice->SetTextureStageState( 0, D3DTSS_COLORARG1, D3DTA_TEXTURE );
m_pd3dDevice->SetTextureStageState( 0, D3DTSS_COLORARG2, D3DTA_DIFFUSE );
m_pd3dDevice->SetTextureStageState( 0, D3DTSS_COLOROP, D3DTOP_MODULATE );
m_pd3dDevice->SetTextureStageState( 0, D3DTSS_MINFILTER, D3DTFN_LINEAR );
m_pd3dDevice->SetTextureStageState( 0, D3DTSS_MAGFILTER, D3DTFG_LINEAR );
m_pd3dDevice->SetTextureStageState( 0, D3DTSS_ADDRESS, D3DTADDRESS_CLAMP);

//i tried the notearing flag for blt and that didn't help either

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