Sign in to follow this  

OpenGL why is my polygons "tearing"?

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

hey. im a java developer but i just started using opengl via the jogl wrapper, after reading the first 10 lessons of the nehe tutorials i decided that the time is right to start coding my own engine with my own file format for storing my models and textures. ok ok ok bad idea i know but after strugling for some time i managed to create a basic engine that loads model files from one directory and JPEG's from another. the model files contains sets of coordinates for each polygon and RGB values for each point and a optional texture name for the entire polygon, it can also store more than one set of RGB and texture values for each polygon so my program can later decide what "skin" to use. i made a ModelHandler class that manages all my models and contains methods to make models from the base models that i loaded from my model files. these models references a base model and contains a xyz coordinate, a xyz angle (direction its facing) and a scale which determines how big it is in relation to the base model. so far my engine can rotate these models around there origin and translate them. my engine translates and rotates the camera with input from the keybord ok.. so thats a roughe summary of what i did so far.. the things i did might be very wrong and unoptimized. but im happy that its working so far but theres just one thing thats REALY bothering me and thats the fact that when my camera gets up close to any of my models and i move around some more i get these nasty horizontal lines "tearing" through my polygons. wheather the polygon is filled with a plain color or with a texture doesnt matter. i dont know if its maybe because of some fundemental mistake im making or just some minor detail im missing. id realy apreaciate help on this matter. anyway here's some screenshots of my engine so far maybe it can help, http://img134.imageshack.us/img134/7578/73651535ut9.jpg http://img134.imageshack.us/img134/8827/33368515de1.jpg http://img412.imageshack.us/img412/47/59183502po0.jpg http://img218.imageshack.us/img218/4564/26405620rd0.jpg so far i've made a Square model that contains 1 "skin" (red and white ying-yang), a cube model that contains 5 different "skins" and a wall model that contains 2 different "skins" (the one with the stone tile texture all over and the one with the asian like decorations) i apologize for any bad terminology used.

Share this post


Link to post
Share on other sites
I don't see any evidence of what's commonly known as tearing in your images, however, what you describe does seem to fit the bill as tearing. Basically, tearing results from not syncing to the display on the vertical retrace period. Not syncing basically means that, during the period that the screen is being drawn, several back-buffers complete rendering and are flipped to the screen. This means that the upper part of the screen is displaying frame n, and the lower part is displaying frame n+1. If the camera or objects move between frames, the frames are different and introduce a visual incongruity; this is tearing.

To fix it, enable vertical syncing. I don't know specifically how to do it in your API, but search the docs for vertical syncing for relevant details. That should fix the problem.

Share this post


Link to post
Share on other sites
unfortenetly the screenshots i took doesnt seem to show the problem. but im 90% sure that what u just explained is relevent to my project so i should to able to sort this by googling up the term

thnx

Share this post


Link to post
Share on other sites
Quote:
Original post by EternityZA
unfortenetly the screenshots i took doesnt seem to show the problem. but im 90% sure that what u just explained is relevent to my project so i should to able to sort this by googling up the term
thnx

That simply confirms the problem. It is the lack of vertical sync. Reason it's not showing up in screenshots is because your screenshot comes from memory, where the entire frame is drawn. It's just that the screen is still displaying a portion of the last frame on it.

You can usually force it on in your video card drivers, or better yet, programmatically turn on like V-man suggested using the WGL_EXT_swap_control extension.

Share this post


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

  • Similar Content

    • By _OskaR
      Hi,
      I have an OpenGL application but without possibility to wite own shaders.
      I need to perform small VS modification - is possible to do it in an alternative way? Do we have apps or driver modifictions which will catch the shader sent to GPU and override it?
    • By xhcao
      Does sync be needed to read texture content after access texture image in compute shader?
      My simple code is as below,
      glUseProgram(program.get());
      glBindImageTexture(0, texture[0], 0, GL_FALSE, 3, GL_READ_ONLY, GL_R32UI);
      glBindImageTexture(1, texture[1], 0, GL_FALSE, 4, GL_WRITE_ONLY, GL_R32UI);
      glDispatchCompute(1, 1, 1);
      // Does sync be needed here?
      glUseProgram(0);
      glBindFramebuffer(GL_READ_FRAMEBUFFER, framebuffer);
      glFramebufferTexture2D(GL_READ_FRAMEBUFFER, GL_COLOR_ATTACHMENT0,
                                     GL_TEXTURE_CUBE_MAP_POSITIVE_X + face, texture[1], 0);
      glReadPixels(0, 0, kWidth, kHeight, GL_RED_INTEGER, GL_UNSIGNED_INT, outputValues);
       
      Compute shader is very simple, imageLoad content from texture[0], and imageStore content to texture[1]. Does need to sync after dispatchCompute?
    • By Jonathan2006
      My question: is it possible to transform multiple angular velocities so that they can be reinserted as one? My research is below:
      // This works quat quaternion1 = GEQuaternionFromAngleRadians(angleRadiansVector1); quat quaternion2 = GEMultiplyQuaternions(quaternion1, GEQuaternionFromAngleRadians(angleRadiansVector2)); quat quaternion3 = GEMultiplyQuaternions(quaternion2, GEQuaternionFromAngleRadians(angleRadiansVector3)); glMultMatrixf(GEMat4FromQuaternion(quaternion3).array); // The first two work fine but not the third. Why? quat quaternion1 = GEQuaternionFromAngleRadians(angleRadiansVector1); vec3 vector1 = GETransformQuaternionAndVector(quaternion1, angularVelocity1); quat quaternion2 = GEQuaternionFromAngleRadians(angleRadiansVector2); vec3 vector2 = GETransformQuaternionAndVector(quaternion2, angularVelocity2); // This doesn't work //quat quaternion3 = GEQuaternionFromAngleRadians(angleRadiansVector3); //vec3 vector3 = GETransformQuaternionAndVector(quaternion3, angularVelocity3); vec3 angleVelocity = GEAddVectors(vector1, vector2); // Does not work: vec3 angleVelocity = GEAddVectors(vector1, GEAddVectors(vector2, vector3)); static vec3 angleRadiansVector; vec3 angularAcceleration = GESetVector(0.0, 0.0, 0.0); // Sending it through one angular velocity later in my motion engine angleVelocity = GEAddVectors(angleVelocity, GEMultiplyVectorAndScalar(angularAcceleration, timeStep)); angleRadiansVector = GEAddVectors(angleRadiansVector, GEMultiplyVectorAndScalar(angleVelocity, timeStep)); glMultMatrixf(GEMat4FromEulerAngle(angleRadiansVector).array); Also how do I combine multiple angularAcceleration variables? Is there an easier way to transform the angular values?
    • By dpadam450
      I have this code below in both my vertex and fragment shader, however when I request glGetUniformLocation("Lights[0].diffuse") or "Lights[0].attenuation", it returns -1. It will only give me a valid uniform location if I actually use the diffuse/attenuation variables in the VERTEX shader. Because I use position in the vertex shader, it always returns a valid uniform location. I've read that I can share uniforms across both vertex and fragment, but I'm confused what this is even compiling to if this is the case.
       
      #define NUM_LIGHTS 2
      struct Light
      {
          vec3 position;
          vec3 diffuse;
          float attenuation;
      };
      uniform Light Lights[NUM_LIGHTS];
       
       
    • By pr033r
      Hello,
      I have a Bachelor project on topic "Implenet 3D Boid's algorithm in OpenGL". All OpenGL issues works fine for me, all rendering etc. But when I started implement the boid's algorithm it was getting worse and worse. I read article (http://natureofcode.com/book/chapter-6-autonomous-agents/) inspirate from another code (here: https://github.com/jyanar/Boids/tree/master/src) but it still doesn't work like in tutorials and videos. For example the main problem: when I apply Cohesion (one of three main laws of boids) it makes some "cycling knot". Second, when some flock touch to another it scary change the coordination or respawn in origin (x: 0, y:0. z:0). Just some streng things. 
      I followed many tutorials, change a try everything but it isn't so smooth, without lags like in another videos. I really need your help. 
      My code (optimalizing branch): https://github.com/pr033r/BachelorProject/tree/Optimalizing
      Exe file (if you want to look) and models folder (for those who will download the sources):
      http://leteckaposta.cz/367190436
      Thanks for any help...

  • Popular Now