Sorry your browser is not supported!

Hey all,

It has probably been asked before but i couldnt find it, so here goes (again maybe ?)

I am in the process of creating a game (like most of you are, I am aware of that) and I currently finished the design on paper.
Now to go from that paper design to real software, I ran into a problem (Well, i don't have problems actually, just challenges) :

I need to have a large terrain, preferrably around 30k units HxL, and it has to be able to show quite some detail as well, so the 70x70 max on a matrix won't cut it.

Now there seem to be 2 main choices I have here :
1: Stick with matrixes and simply create a 4x4 matrix area (or more)
2: Go for plain objects that I can possibly create in milkshape or something.

Now from what I read about both, they both have their pro's and cons. (like always) But these aren't really clear to me alas.

Can someone help me in this area and point me in the right direction ? I really need a reasonably detailed (big) terrain and I don't know which way to go with this.

Cheers.

Richard.

I wouldn't have that large an area unless it's actually vitally necessary for your game design - you'd be better off just switching from one area to another instead of having the entire world loaded all the time.

Use Kelebrindae's memblock matrices. You can find them in the codebase or on his website. They offer alot more flexibility than a regular matrix and your map can exceed 70x70. Although as Demon's Breath said, it's better to use smaller maps and just hide the sections you dont need because a 70x70 matrix is 9800 polygons and that'll kill your framerate.

You can also use a small matrix and have huge arrays containing all the texture and height data.

As you move around by scrolling the matrix under the player, you can update the edges of the matrix (which will always be in the distance and therefore unseen) from the arrays.

The attached demo zip file uses a similar method.

TDK_Man