OpenGL Texture Tiling How-to

Recommended Posts

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

Share on other sites
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

Share on other sites
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

Share on other sites
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

Share on other sites
Anybody anybody at all?

Share this post

Share on other sites
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

Share on other sites
Quote:
 Original post by MegahertzHave 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

Share on other sites
"it's all comming back as null."

That's not very descriptive =P

-=[ Megahertz ]=-

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

• Partner Spotlight

• Forum Statistics

• Total Topics
627657
• Total Posts
2978472
• Similar Content

• Both functions are available since 3.0, and I'm currently using glMapBuffer(), which works fine.
But, I was wondering if anyone has experienced advantage in using glMapBufferRange(), which allows to specify the range of the mapped buffer. Could this be only a safety measure or does it improve performance?
Note: I'm not asking about glBufferSubData()/glBufferData. Those two are irrelevant in this case.
• By xhcao
Before using void glBindImageTexture(    GLuint unit, GLuint texture, GLint level, GLboolean layered, GLint layer, GLenum access, GLenum format), does need to make sure that texture is completeness.
• By cebugdev
hi guys,
are there any books, link online or any other resources that discusses on how to build special effects such as magic, lightning, etc. in OpenGL? i mean, yeah most of them are using particles but im looking for resources specifically on how to manipulate the particles to look like an effect that can be use for games,. i did fire particle before, and I want to learn how to do the other 'magic' as well.
Like are there one book or link(cant find in google) that atleast featured how to make different particle effects in OpenGL (or DirectX)? If there is no one stop shop for it, maybe ill just look for some tips on how to make a particle engine that is flexible enough to enable me to design different effects/magic
let me know if you guys have recommendations.
Thank you in advance!
• By dud3
How do we rotate the camera around x axis 360 degrees, without having the strange effect as in my video below?
Mine behaves exactly the same way spherical coordinates would, I'm using euler angles.
Tried googling, but couldn't find a proper answer, guessing I don't know what exactly to google for, googled 'rotate 360 around x axis', got no proper answers.

References:
Code: https://pastebin.com/Hcshj3FQ
The video shows the difference between blender and my rotation:

• By Defend
I've had a Google around for this but haven't yet found some solid advice. There is a lot of "it depends", but I'm not sure on what.
My question is what's a good rule of thumb to follow when it comes to creating/using VBOs & VAOs? As in, when should I use multiple or when should I not? My understanding so far is that if I need a new VBO, then I need a new VAO. So when it comes to rendering multiple objects I can either:
* make lots of VAO/VBO pairs and flip through them to render different objects, or
* make one big VBO and jump around its memory to render different objects.
I also understand that if I need to render objects with different vertex attributes, then a new VAO is necessary in this case.
If that "it depends" really is quite variable, what's best for a beginner with OpenGL, assuming that better approaches can be learnt later with better understanding?

• 10
• 12
• 22
• 13
• 33