- Timestamp:
- 10/24/05 16:37:50 (19 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/VUT/work/TestCullingTerrain/TestCullingTerrainApplication.cpp
r346 r347 309 309 generateScene(200, 2); 310 310 } 311 312 // no limitations on height => it is possible for the user to put single313 // objects on peaks of the terrain (only few, not relevant for occlusion)314 mTerrainContentGenerator->SetMaxPos(mTerrainMaxPos);315 311 } 316 312 //----------------------------------------------------------------------- … … 319 315 float val = TerrainFrameListener::msObjectScales[objectType]; 320 316 Vector3 scale(val, val, val); 321 const float maxHeight = 100;317 const float maxHeight = 75; 322 318 // to provide much occlusion, 323 // height is restricted to 50=> no objects are created on peaks319 // height is restricted to maxHeight => no objects are created on peaks 324 320 mTerrainContentGenerator->SetMinPos(Vector3(mTerrainMinPos)); 325 321 mTerrainContentGenerator->SetMaxPos(Vector3(mTerrainMaxPos.x, maxHeight, mTerrainMaxPos.z)); … … 342 338 } 343 339 344 // no limitations anymore=> it is possible for the user to put single345 // objects on peaks of the terrain ( only few, not relevant for occlusion)340 // release limitations on height => it is possible for the user to put single 341 // objects on peaks of the terrain (will be only few, not relevant for occlusion) 346 342 mTerrainContentGenerator->SetMaxPos(mTerrainMaxPos); 347 343 }
Note: See TracChangeset
for help on using the changeset viewer.