Crystal Space
Welcome, Guest. Please login or register.
September 19, 2014, 05:06:42 am

Login with username, password and session length
Search:     Advanced search
9018 Posts in 2051 Topics by 8481 Members
Latest Member: Cex18145xu
* Home Help Search Login Register
+  Crystal Space
|-+  Crystal Space Development
| |-+  Support
| | |-+  Terrain2 ... some questions
« previous next »
Pages: [1] Print
Author Topic: Terrain2 ... some questions  (Read 1463 times)
maharaja
Jr. Member
**
Posts: 52

t.javed@hotmail.com
View Profile Email
« on: November 28, 2007, 11:10:27 am »

Hi,

I need to render enormous terrains so I decided to start using terrain2 as it seems to provide just what I need (grid etc.)
After reading the complete deails in the manual and looking through the xml in terraini sample, I still have a few questions as follows:

1. Do I understand correctly that the 'gridsize' of each 'cell' would basically always be the same as the x,y size of the height-map? So if your height-map for that cell is 64x64 then the grid-size would also be 64x64 and if height-map is 128x128 then grid would also be 128x128 and so on ?

2. The 'position' of a cell is defined relative to the center of the entire terrain mesh. This is fine for terrains with 2x2 or 4x4 cells. But what if we have a 3x3, meaning a total of 9 cells? There is no 'center' as such unless we count from the 4 corners of the cell that is in the middle. Same would be the case with any odd-number x odd-number grid.

3. <maxloadedcells> defines the maximum cells to pre-load. But if <maxloadedcells> is 20 what does it exectly mean? 20 cells in which direction or what grid format? No grid size would total up to 20 cells.

Well, this is probably all I need to know before jumping off to use terrain2, though I might have more questions later.

Many thanks in advance.

/regards

Logged
Pages: [1] Print 
« previous next »
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.2 | SMF © 2006-2007, Simple Machines LLC Valid XHTML 1.0! Valid CSS!
Page created in 4.355 seconds with 15 queries.