# OpenGL Texture deformation

## Recommended Posts

mcphist    122
Hi people. Look this two images: The first is my original sphere; the second is how I see with OpenGl. It has a deformation on the left side. I've tried everything: GL_LINEAR, GL_NEAREST, GL_CLAMP, etc. I'm using alpha testing for not drawing pink pixels. I've tried with BLEND, but it doesn't work too. Almost every texture that I have, has a minor deformation when I see with OpenGl. But this seems to happen when the texture is very small. For example, my sphere is 45x43. If I scale the QUAD, the texture automatically scale too, and it looks perfect. Is there a way for see a texture exactly like I made in Paint, for example? Thanks in advance!

##### Share on other sites
swordfish    276
What deformation?
The top image has a circle with the left and top edges slightly trimmed off.
The bottom image has a circle with the bottom and right edges trimmed off.
Conclusion: your texture is flipped across both axes. Invert your UV coordinates and see if that doesn't fix it.

The 'deformation' you are seeing is probably due to the quality of the image you are using for the texture. Can we see the actual image file so that we can be sure?

##### Share on other sites
mcphist    122
Ok, I'll scale the image:

The first is my original image, a 24 bits bitmap. In the second image, the deformation is marked with a blue rectangle. This DOESN'T happen if I scale the QUAD.

Also, note this:

The first is my original image, again a 24 bits bitmap. In the second image, I rotated with glrotatef 90 degrees. Note the little deformation.

All this DOESN'T happen if I scale the QUAD, very strange.

What can I do?

##### Share on other sites
KulSeran    3267
You should consider using an orthographic projection so that screen pixels can directly match up to your texture pixels.
Then you need to draw your textured quad to exactly the same screen size in pixels as your texture you loaded onto it.

Also note that you may need to fix up your UV coords on the texture so that
on a 64x64 image you have UV's of
0 + 1/128
1 - 1/128
(something i read some where about .5 pixel offsets being better than directly on the corners of a pixel)

##### Share on other sites
mcphist    122
Thanks for the answer. I'm using an orthographic projection, and my QUAD is the same size in pixels like my texture. For example, my green sphere is 45x43.

width = 45height = 43p_V = 45/64p_U = 43/64glBegin(GL_QUADS);      glTexCoord2f( 0, p_V );	glVertex2f( 0, 0 ); 		     glTexCoord2f( p_U, p_V );  glVertex2f( width, 0 ); 		     glTexCoord2f( p_U, 0 );  glVertex2f( width, height ); 		     glTexCoord2f( 0, 0 );  glVertex2f( 0, height ); glEnd();

Anyway, I'm sure that the texture's coords and all that is ok, because if I scale the QUAD ( glVertex2f( width = 145, 0) glVertex2f( height = 143, 0) ) the texture is displayed perfectly, without imperfections.

I'm sure that I'm forgetting some texture's parameter, like GL_LINEAR, GL_NEAREST, etc.. but I can't find it.

## Create an account

Register a new account

• ### Similar Content

• Hello. I'm Programmer who is in search of 2D game project who preferably uses OpenGL and C++. You can see my projects in GitHub. Project genre doesn't matter (except MMO's :D).

• Hello, My name is Matt. I am a programmer. I mostly use Java, but can use C++ and various other languages. I'm looking for someone to partner up with for random projects, preferably using OpenGL, though I'd be open to just about anything. If you're interested you can contact me on Skype or on here, thank you!
Skype: Mangodoor408
• By tyhender
Hello, my name is Mark. I'm hobby programmer.
So recently,I thought that it's good idea to find people to create a full 3D engine. I'm looking for people experienced in scripting 3D shaders and implementing physics into engine(game)(we are going to use the React physics engine).
And,ye,no money =D I'm just looking for hobbyists that will be proud of their work. If engine(or game) will have financial succes,well,then maybe =D
Sorry for late replies.
I mostly give more information when people PM me,but this post is REALLY short,even for me =D
So here's few more points:
Engine will use openGL and SDL for graphics. It will use React3D physics library for physics simulation. Engine(most probably,atleast for the first part) won't have graphical fron-end,it will be a framework . I think final engine should be enough to set up an FPS in a couple of minutes. A bit about my self:
I've been programming for 7 years total. I learned very slowly it as "secondary interesting thing" for like 3 years, but then began to script more seriously.  My primary language is C++,which we are going to use for the engine. Yes,I did 3D graphics with physics simulation before. No, my portfolio isn't very impressive. I'm working on that No,I wasn't employed officially. If anybody need to know more PM me.

• By Zaphyk
I am developing my engine using the OpenGL 3.3 compatibility profile. It runs as expected on my NVIDIA card and on my Intel Card however when I tried it on an AMD setup it ran 3 times worse than on the other setups. Could this be a AMD driver thing or is this probably a problem with my OGL code? Could a different code standard create such bad performance?

• I'm trying to get some legacy OpenGL code to run with a shader pipeline,
The legacy code uses glVertexPointer(), glColorPointer(), glNormalPointer() and glTexCoordPointer() to supply the vertex information.
I know that it should be using setVertexAttribPointer() etc to clearly define the layout but that is not an option right now since the legacy code can't be modified to that extent.
I've got a version 330 vertex shader to somewhat work:
#version 330 uniform mat4 osg_ModelViewProjectionMatrix; uniform mat4 osg_ModelViewMatrix; layout(location = 0) in vec4 Vertex; layout(location = 2) in vec4 Normal; // Velocity layout(location = 3) in vec3 TexCoord; // TODO: is this the right layout location? out VertexData { vec4 color; vec3 velocity; float size; } VertexOut; void main(void) { vec4 p0 = Vertex; vec4 p1 = Vertex + vec4(Normal.x, Normal.y, Normal.z, 0.0f); vec3 velocity = (osg_ModelViewProjectionMatrix * p1 - osg_ModelViewProjectionMatrix * p0).xyz; VertexOut.velocity = velocity; VertexOut.size = TexCoord.y; gl_Position = osg_ModelViewMatrix * Vertex; } What works is the Vertex and Normal information that the legacy C++ OpenGL code seem to provide in layout location 0 and 2. This is fine.
What I'm not getting to work is the TexCoord information that is supplied by a glTexCoordPointer() call in C++.
Question:
What layout location is the old standard pipeline using for glTexCoordPointer()? Or is this undefined?

Side note: I'm trying to get an OpenSceneGraph 3.4.0 particle system to use custom vertex, geometry and fragment shaders for rendering the particles.

• 10
• 11
• 25
• 16
• 19