Aaaah, that explains some of what I'm seeing. Hum... Using the
TerrianManipulator is different from the trackball manipulator but the idea is
the same: setByMatrix I have been assuming to capture the entire state of the
manipulator and to properly situate my camera exactly where I want and at
Hi Allen,
I have a terrain manipulator I hope to release soon (which is
ill-defined for where I work). For inspiration you can also look at the
earth manipulator in osgEarth.
jp
Allen Saucier wrote:
Aaaah, that explains some of what I'm seeing. Hum... Using the
TerrianManipulator is
Hi Allen,
the problem with setMatrix is that it cannot fully encapsulate the state
of the manipulator. Internally the manipulator (trackball) uses a
distance, rotation and center, but all these variables do not fit into a
matrix. The manipulator can calc a matrix from the internal variables,
Is your viewing camera also using the local coordinate system (i.e
geocentric)?
Guy
--
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=25621#25621
___
osg-users mailing list
Hi,
thanks JP! :) I really appreciate your response. It appears I am fighting
something I didn't expect and something I don't fully understand: the terrain
manipulator.
I understand what you've proposed but when I call the fucntion: setByMatrix()
w/in the terrain manipulator, that function
Hi,
I am having some extreme difficulty in rotating my viewing camera 90 degrees
with respect to a local coordinate system.
Local coordinate system: (in geocentric measure)
mine is at the edge of the earth; i.e. i'm using a spherical earth. here is
how I compute the local axes:
fuctionName (
Hi,
I didn't try to follow your code, but here's and overview of how we do it:
Have a camera/manipulator makeLookAt command that takes eye, center and
up vectors. (These can be converted to the osg manipulators' distance,
rotation, center).
Have a transformation matrix from ECEF coords to
7 matches
Mail list logo