RB
20-03-2006 09:50:16
Hi,
Currently I am working on the submersible simulation project which is using PLSM for ocean bottom surface modeling.
Coordinate system of our specific terrain should be translated along y axis ( this is a marine convention).
I think it would be nice if we can place terrain in positions different from (0,0,0).
So i added new option to the PagingLandScapeOptions class and call it "position", i also add 3 new parameters to the .cfg parser -
"PositionX, PositionY, PositionZ", which working much like "ScaleX, ScaleY, ScaleZ" options. Also i slightly changed PagingLandScapePage::init (..) PagingLandScapeRenderable::getRawVertexData(..) functions which now consider terrain translation, i.e physics engines should not notice any change.
I'll post the patch as soon as cvs.sourceforge.net wake alive
Currently I am working on the submersible simulation project which is using PLSM for ocean bottom surface modeling.
Coordinate system of our specific terrain should be translated along y axis ( this is a marine convention).
I think it would be nice if we can place terrain in positions different from (0,0,0).
So i added new option to the PagingLandScapeOptions class and call it "position", i also add 3 new parameters to the .cfg parser -
"PositionX, PositionY, PositionZ", which working much like "ScaleX, ScaleY, ScaleZ" options. Also i slightly changed PagingLandScapePage::init (..) PagingLandScapeRenderable::getRawVertexData(..) functions which now consider terrain translation, i.e physics engines should not notice any change.
I'll post the patch as soon as cvs.sourceforge.net wake alive