Game Development Community

Terrain guidance needed

by Moogy Monster · in Torque Game Engine · 01/29/2004 (7:55 pm) · 2 replies

I grow tired of this 'repeating terrain' nonsense. :D Thus, I am resolved to write a new TerrainBlock class that behaves in every way the same as the origional, but with only one instance that can be placed anywhere and combined with others, etc.

I am aware of the Terrain Manager patch, but I need to accomplish a similar thing only differently. For now, I just need to strip out the repeating logic, and create a simple terrain block.

In the code I have found the clever little loop for shifting and rendering the block multiple times depending on whats visible, and I imagine there's something similar for the collision logic. Beyond rendering and collisions, is there anything else I need to be mindful of in accomplishing this? What difficulties might I expect?

#1
01/30/2004 (9:32 am)
The terrain rendering code is just really heinous and you may have issues with seams - ie, edges of terrain blocks not lining up nicely.
#2
01/30/2004 (2:09 pm)
I thought that I had the rendering part figured out... could be wrong tho! I know that texturing and light mapping is going to be painful. Right now I'm working on the collision stuff, and on the side I'm wondering about object occlusion. I noticed that when I turn off the terrain rendering, objects behind a now invisible hill disappear. That's pretty darn cool by the way, definately don't want to mess that up. I'm hoping the collision code handles that as well.

Seams and other visual problems do not worry me so much. I'm more worried about the stuff I can't see, like someday falling through a hole in my terrain long after I thought I had it all finished and working.