• Announcements

    • khawk

      Download the Game Design and Indie Game Marketing Freebook   07/19/17

      GameDev.net and CRC Press have teamed up to bring a free ebook of content curated from top titles published by CRC Press. The freebook, Practices of Game Design & Indie Game Marketing, includes chapters from The Art of Game Design: A Book of Lenses, A Practical Guide to Indie Game Marketing, and An Architectural Approach to Level Design. The GameDev.net FreeBook is relevant to game designers, developers, and those interested in learning more about the challenges in game development. We know game development can be a tough discipline and business, so we picked several chapters from CRC Press titles that we thought would be of interest to you, the GameDev.net audience, in your journey to design, develop, and market your next game. The free ebook is available through CRC Press by clicking here. The Curated Books The Art of Game Design: A Book of Lenses, Second Edition, by Jesse Schell Presents 100+ sets of questions, or different lenses, for viewing a game’s design, encompassing diverse fields such as psychology, architecture, music, film, software engineering, theme park design, mathematics, anthropology, and more. Written by one of the world's top game designers, this book describes the deepest and most fundamental principles of game design, demonstrating how tactics used in board, card, and athletic games also work in video games. It provides practical instruction on creating world-class games that will be played again and again. View it here. A Practical Guide to Indie Game Marketing, by Joel Dreskin Marketing is an essential but too frequently overlooked or minimized component of the release plan for indie games. A Practical Guide to Indie Game Marketing provides you with the tools needed to build visibility and sell your indie games. With special focus on those developers with small budgets and limited staff and resources, this book is packed with tangible recommendations and techniques that you can put to use immediately. As a seasoned professional of the indie game arena, author Joel Dreskin gives you insight into practical, real-world experiences of marketing numerous successful games and also provides stories of the failures. View it here. An Architectural Approach to Level Design This is one of the first books to integrate architectural and spatial design theory with the field of level design. The book presents architectural techniques and theories for level designers to use in their own work. It connects architecture and level design in different ways that address the practical elements of how designers construct space and the experiential elements of how and why humans interact with this space. Throughout the text, readers learn skills for spatial layout, evoking emotion through gamespaces, and creating better levels through architectural theory. View it here. Learn more and download the ebook by clicking here. Did you know? GameDev.net and CRC Press also recently teamed up to bring GDNet+ Members up to a 20% discount on all CRC Press books. Learn more about this and other benefits here.
Sign in to follow this  
Followers 0

INSANE quadtree bugs/artefacts

2 posts in this topic

Hi people

I've been working on a quad tree demo for some time and used this gentleman's code as a study to learn: http://www.youtube.com/watch?v=9N-kgCqy2xs


However my results for the island scene look like this:




I started following the base code loosely, but to try and get the rendering of the quadtree correct I adhered quite closely to the terrain files as I was being driven slowly crazy. Even now when I see very little difference between the sets of code there must be some faults. 


The important code is as follows:


int halfWidth  = m_width/2;
	int halfHeight = m_height/2;

	//init verts
	vec3* vertData = new vec3[m_numVertices];

	for(int z = 0; z < m_height; z++){
		for(int x = 0; x < m_width; x++){

			int index = z * m_width + x;

			int imgIndexZ = z;
			int imgIndexX = x;
			if(z == imgHeight){
			if(x == imgWidth){

			int imgIndex = imgIndexZ * m_width + imgIndexX;

			vertData[index].x = (x - halfWidth) * LANDSCAPE_SCALE;
			vertData[index].y = (float)data[imgIndex] * HEIGHT_SCALE;
			vertData[index].z = (z - halfHeight) * LANDSCAPE_SCALE;


The above is how I init my vertices values, with data being an image file holding the height values. The land mass itself renders fine if I render it as a whole block without a quadtree using an indexed VAO and GL_TRIANGLES.


The indices generating function of the terrain chunks if I go the alternative route, however, is as follows:


int heightmapDataPosX = posX;
int heightmapDataPosY = posY;
unsigned int offset = (unsigned int)pow(2.0f, (float)(lod));
unsigned int div = (unsigned int)pow(2.0f, (float)(depth+lod));
int heightmapDataSizeX = HMsizeX/(div) + 1;
int heightmapDataSizeY = HMsizeY/(div) + 1;

int nHMWidth   = heightmapDataSizeX;
int nHMHeight  = heightmapDataSizeY;
int nHMOffsetX = heightmapDataPosX;
int nHMOffsetY = heightmapDataPosY;

GLuint nHMTotalWidth = HMsizeX;
GLuint nHMTotalHeight = HMsizeY;

m_indOffsetW[lod] = nHMWidth*2;
m_indOffsetH[lod] = nHMHeight-1;
GLuint numIndices = (nHMWidth-3)*(nHMHeight-4)*2;
m_indices[lod] = new GLuint[numIndices]; 
m_numIndices[lod] = numIndices;

int index = 0;

for(GLuint y=1; y< nHMHeight-3; y++)
  for(GLuint x=1; x< nHMWidth-2; x++)
    GLuint id0 = COORD(x*(offset) + nHMOffsetX, y*(offset) + nHMOffsetY);
    GLuint id1 = COORD(x*(offset) + nHMOffsetX, y*(offset) + nHMOffsetY+(offset));
    m_indices[lod][index++] = id0;
    m_indices[lod][index++] = id1;


I have to alter the termination conditions for y and x and the numIndices because for some reason I get a memory access error, even though the numberOfVertices should be ok...


I know its masochistic but if anyone can help me I'd be so grateful! I've been going crazy for days... My github repo is here: https://github.com/LloydGhettoWolf/TitanicTerrain/tree/workingversion


Share this post

Link to post
Share on other sites

Your lack of replies is likely because it is hard to tell which bugs are related to your quadtree (which should be an octree, yes?) and which are related to something else.

For example you have missing triangles.  That would not be related to quadtrees unless you have done something horribly wrong and are in need of a major rewrite.


Besides, you already have  memory-access errors.


Fix everything else so we can see problems that are only related to the quadtree.



L. Spiro


Share this post

Link to post
Share on other sites

I fixed the big issues using a different approach found on the rastertek site, but thankyou for replying. However, now I have bizarre frustum culling issues where nearby quads are being culled. I'll post a separate thread for that.


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  
Followers 0