Sign in to follow this  
PnP Bios

OpenGL Texture Tiling How-to

Recommended Posts

PnP Bios    494
Greetings everybody, I am working on the next version of my graphics library, and I am trying to solve the problem of using an OpenGL texture map for an image surface. Due to the resrictions on size of the texture, I figured I could solve this by breaking up the surface into smaller textures. But that just brings up more problems, such as how to figure out UV coordinates and screen coordinates. This is my blitting function, and where I think the problem is
[source ]void hxSurface::Blit(hxRect sRect, hxRect dRect)
{
	float u1, u2, v1, v2;	//texture coordinates
	float sx, sy, sw, sh;	//screen coordinates
	
	int l, r, t, b;			//four edges of the image

	l = sRect.x / this->chunk_width;
	r = (sRect.x + sRect.w) / this->chunk_width;

	t = sRect.y / this->chunk_height;
	b = (sRect.y + sRect.h) / this->chunk_height;

	//screen coordinate variables
	float x_start = FL(dRect.x);
	float y_start = FL(dRect.y);

	float w_inc = FL(dRect.w)/FL(sRect.w) * FL(this->chunk_width);
	float h_inc = FL(dRect.w)/FL(sRect.w) * FL(this->chunk_height);

	float xOff, yOff;	//offsets for stuff

	sx = x_start;
	sx = y_start;

	xOff = w_inc;
	yOff = h_inc;

	for (int i = t; i <= b; i += 1)
	{
		for(int j = l; j <= r; j += 1)
		{
			u1 = 0.0f;
			v1 = 0.0f;

			u2 = 1.0f;
			v2 = 1.0f;

			
			//do adjustments for UV coordinates
			if(j == l)
				u1 = FL(l % this->chunk_width) / FL(this->chunk_width);

			if(j == r)
				u2 = FL(r % this->chunk_width) / FL(this->chunk_width);

			if(i == t)
				v1 = FL(t % this->chunk_height) / FL(this->chunk_height);

			if(i == b)
				v2 = FL(l % this->chunk_height) / FL(this->chunk_height);
			
			//do adjustments for screen coordinates
			sw = w_inc * (u2 - u1);
			sh = h_inc * (v2 - v1);
			
			//blit object to the screen;
			glBindTexture(GL_TEXTURE_2D, this->texList[(this->y_chunk * i)+j]);

			glBegin(GL_QUADS);

			glTexCoord2f(u1, v1);	glVertex2f(sx, sy);
			glTexCoord2f(u1, v2);	glVertex2f(sx, sy);
			glTexCoord2f(u2, v2);	glVertex2f(sx + sw, sy + sh);
			glTexCoord2f(u2, v1);	glVertex2f(sx + sw, sy);

			glEnd();

			sx += sw;

			//this doesn't look right, does it?
			if(j == r)
			{
				sy += sh;
				sx = x_start;
			}
		}
	}

	return;
}

FL is a macro that casts something as a float. Is there anything blatently obvious that you see with the tiling? Should I be looking at another method instead?

Share this post


Link to post
Share on other sites
JTippetts    12950
Just at first glance, should this line:


if(i == b) v2 = FL(l % this->chunk_height) / FL(this->chunk_height);


be this instead:


if(i == b) v2 = FL(b % this->chunk_height) / FL(this->chunk_height);


You're using l instead of b.

Share this post


Link to post
Share on other sites
PnP Bios    494
I applied that change, and still nothing appeared.
For further refrence, here is some more of the code.

hxSurface constructor
hxSurface::hxSurface(uint w, uint h)
{
//Step 1 break image into the smallest ammount of chunks possible
//Until I write a better routine, 64x64 will have to do...

uint wChunkSize = 64; //64 by 64 is going to be the smallest
uint hChunkSize = 64;
int wct; //number of blocks in each direction
int hct;

if(w > 64) //Determine the width and height of each of the chunks
wChunkSize = 128;
if(w > 128)
wChunkSize = 256;
if(w > 256)
wChunkSize = 512;

if(h > 64)
hChunkSize = 128;
if(h > 128)
hChunkSize = 256;
if(h > 256)
hChunkSize = 512;

wct = w / wChunkSize;
hct = h / hChunkSize;

if(w % wChunkSize) //take care of any overlap
wct += 1;
if(h % hChunkSize)
hct += 1;

//Step 2, allocate some memory for all the mini surfaces
surfaceChunk **list;
uint *textureList;
list = (surfaceChunk **)malloc(sizeof(surfaceChunk)*wct*hct);

//Step 3, create a unique texture ID for each of those surfaces
textureList = (uint *)malloc(sizeof(uint)*wct*hct);
glGenTextures((wct*hct),textureList);

//Step 4, allocate memory for the chunks
for(int i = 0; i < hct; i += 1)
{
for(int j = 0; j < wct; j += 1)
{
list[(i * wct)+ j] = CreateChunk(wChunkSize, hChunkSize, textureList[(i*wct) + j]);
}
}

//Step 5, share the pointers with the rest of the class

this->total_width = w;
this->total_height = h;

this->chunk_width = wChunkSize;
this->chunk_height = hChunkSize;

this->x_chunk = wct;
this->y_chunk = hct;

this->numChunks = wct * hct;
this->chunks = list;
this->texList = textureList;

}




here is the write pixel function:
void hxSurface::WritePixel(int x, int y, hxColor color)
{
surfaceChunk *workChunk; //temporary work chunk container

int blockx; //which block?
int blocky;

int offx; //the actual x,y coordinates of the block
int offy;

blockx = (x / this->chunk_width);
blocky = (y / this->chunk_height);

offx = (x % this->chunk_width);
offy = (y % this->chunk_height);

workChunk = this->chunks[(blocky * this->x_chunk)+blockx];

WritePix(workChunk, offx, offy, color);

return;
}



I just can't seem to narrow down where the problem is. Thanks to anybody who atleast reads this.

edit: here is the refresh surface function
void hxSurface::Update(void)
{
surfaceChunk *work;

for(int i = 0; i < this->numChunks; i += 1)
{
work = this->chunks[i];

glBindTexture(GL_TEXTURE_2D, work->texID);

//setup the texturing parameters
glTexParameteri(GL_TEXTURE_2D,GL_TEXTURE_MIN_FILTER,GL_LINEAR);
glTexParameteri(GL_TEXTURE_2D,GL_TEXTURE_MAG_FILTER,GL_LINEAR);

glTexImage2D(GL_TEXTURE_2D, 0, GL_RGBA, work->w, work->h , 0, GL_RGBA, GL_UNSIGNED_BYTE, work->data);
}

return;
}

Share this post


Link to post
Share on other sites
PnP Bios    494
I'm prety sure that the UV coordinates are done alright, but it seems to be the screen coordinates that I am having problems generating.

Share this post


Link to post
Share on other sites
Megahertz    286
Have you tried stepping through the code and seeing what numbers are comming out right and which ones are not?

Set up some simple test cases and run them through the code and follow along. Veryify all the numbers as you go.

-=[ Megahertz ]=-

Share this post


Link to post
Share on other sites
PnP Bios    494
Quote:
Original post by Megahertz
Have you tried stepping through the code and seeing what numbers are comming out right and which ones are not?

Set up some simple test cases and run them through the code and follow along. Veryify all the numbers as you go.

-=[ Megahertz ]=-


I'm doing this now, and for some reason, it's all comming back as null.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this  

  • Similar Content

    • By povilaslt2
      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).
    • By ZeldaFan555
      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?
    • By Kjell Andersson
      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.
  • Popular Now