• Advertisement
Sign in to follow this  

OpenGL Texture detail changing by itself [solved]

This topic is 3023 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 everybody! This is my first opengl experiment and I'm trying to make a simple 2D game. The problem is: The "floor" texture is getting very ugly. In other words, it's getting from this: http://i38.tinypic.com/2chp4p3.jpg to this: http://i33.tinypic.com/35bccbt.jpg . It becomes like that when the floor moves very fast (so when it's freezed it gets like the last picture), but when it moves not so fast it stays ok. One more thing, the floor moves through the texture matrix (glTranslatef). Thankyou in advance! [Edited by - pescador on November 10, 2009 9:59:46 AM]

Share this post


Link to post
Share on other sites
Advertisement
This is common problem - try to look at fast rotating wheel (I think it is called The Rotating Wheel Phenomenon).

E.g. you have to do some kind of per pixel motion blurring to make illusion of motion and to keep high level image quality ... look at http://http.developer.nvidia.com/GPUGems3/gpugems3_ch27.html - you might get right idea there ;)

Share this post


Link to post
Share on other sites
Vilem Otte,

Thankyou for posting that link, but I guess you didn't understand what I said. The floor texture gets ugly like that after moving at fast velocity, I mean, after the "motion" (when it's freezed again) it gets ugly.

See the program flow:

-> Floor is freezed (texture is ok);
-> Floor is moving (texture is bad, as it suposed to be);
-> Floor is freezed again (texture is still bad, why?);
-> Floor is moving very fast (texture is much bad);
-> Floor is freezed again (texture is still much bad);

Sorry for my english.

Share this post


Link to post
Share on other sites
To me it looks like loss of precision in texture coordinates. Are you using full float all the way through?

Share this post


Link to post
Share on other sites
RDragon1,

Yes. Btw the problem is gone when I take off this line (GL_TEXTURE matrix mode):

glTranslatef((GLfloat) cos(rot), (GLfloat) sin(rot), 0);

So maybe it is a "loss of precision in texture coordinates". But now I can't make my car get velocity... Any idea?

Share this post


Link to post
Share on other sites
You are doing something very wrong. You should not be using GL_TEXTURE_MATRIX.

You should be using GL_MODELVIEW_MATRIX. In other words if you have a terrain, when running on it, does the grass move across the terrain, or does the terrain move as a whole?

Share this post


Link to post
Share on other sites
Quote:
Original post by dpadam450
You are doing something very wrong. You should not be using GL_TEXTURE_MATRIX.

You should be using GL_MODELVIEW_MATRIX. In other words if you have a terrain, when running on it, does the grass move across the terrain, or does the terrain move as a whole?


Computer graphics isn't about conceptually simulating the real world if there are better ways to achieve the same result. In this case however I remember it is generally advices not to use the texture matrix for performance reasons (probably optimized away if identity). Instead of a screen-sized quad and a moving texture you need to move the quad (or car and "camera", which has the same end result).

It also means more trouble doing an "infinite" world (texture wrapping does that automatically) and always checking the bounds.

The texture matrix is easier and more convenient, but the result looks like either filtering and zooming a low res texture, not clearing the color/depth buffer before each frame or some weird scaling going on. For debugging, read back the texture matrix and make sure it is orthonormal.

Share this post


Link to post
Share on other sites
So it's not convenient to use TEXTURE matrix mode to make the world (floor) move. But why? So the texture matrix mode is less eficient than the others matrix? If yes, how to make an infinite world moving using not infinite quads? Maybe creating an giant quad (size of the game world) using GL_REPEAT wrap mode for the rendering texture and moving it in MODELVIEW matrix mode... Well, In my opinion this is a great loss of performance. What you think?

Thankyou for helping me!

Share this post


Link to post
Share on other sites
Well, I tested it.

1- Move the floor by rendering a textured screen size quad through texture matrix translation;
2- Move the floor by rendering a giant quad (game world size) textured with GL_REPEAT wrap mode, with modelview translation;

Conclusion: the frame rate is the same.
The difference is: in the first option the texture looks, after some time, ugly.

Maybe someone can make a deeper test. Thanks!

Share this post


Link to post
Share on other sites
I use the texture moving technique (to simulate the track of a tank), and I didn't notice this phenomenon.
Anyway you can use the following with modelview transformation:
Make a quad and repeat the texture 2 times (-1 to 1 texture coordinate range).
The size of the quad is to times bigger, than the size of the screen.

if you translate the map and rotate the car (like in GTA 1):

Let x, y be the coordinates of the quad center in screen coordinates.

if( x > screen_width )
x -= screen_width;
else if( x < screen_width )
x += screen_width;

if( y > screen_height )
y -= screen_height;
else if( y < screen_height )
y += screen_height;

I hope that made sense.

Share this post


Link to post
Share on other sites
The code has no secrets, it's just like this:


glMatrixMode(GL_TEXTURE);
glTranslatef(floor.xpos, floor.ypos, 0);
//render the floor with display list or vertex array (I got the same frame rate).
glLoadIdentity();
//render the car. Want it to stay centered.
glMatrixMode(GL_MODELVIEW);
glPushMatrix();
//render some objects.
glPopMatrix();

Share this post


Link to post
Share on other sites
What values do floor.xpos, floor.ypos have?

Do you convert it to texture space, or you have say x = 42345312454744?

Maybe it's simply a floating point precision problem.

Maybe the car only seems to have proper speed because of this:
You except to translate it with 0.1, instead it translates with 321321321.1.
So it displays just like it was 0.1 (because the repeat warping), but you loose precision.

EDITED it heavily.

Share this post


Link to post
Share on other sites
Well, actually xpos and ypos are defined as GLfloat. And they are "zero initialized". The increment function: obj.xpos += 0.001; I really don't know what to do. Maybe my graphic card (Btw Sis Mirage 3, onboard) is the trouble.

Share this post


Link to post
Share on other sites
So, I would like to say this problem is partially solved. I just change the floor move type, from texture matrix mode to modelview matrix mode. The texture didn't currupt its appearence anymore.

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