Hi all,
Dirk, thanks for your replies on this subject. But it is still not clear how
to use this decorator. I'll explain my questions:
We found some docs telling that both user node and screen corners are
defined within tracker space, which makes sense for me ;). I've analysed
ProjectionCameraDecorator source code, and, in fact, planes are stored in
tracker space. (::updateData()). But ::getViewing() method uses the user
node to place the camera (user->getToWorld()). So, the user node must be a
child of camera beacon, otherwise camera transform will not be taken into
account in order to calculate
view matrix... ;-/ . That means that user position will change camera
position... I can't understand that..
Why should user alter camera view matrix?
We have a dynamic camera, that moves around the world, so it does have a
changing world position. If user node is equivalent to the tracker device
pose (which means, of course, that user is in tracker space),
and it must be child of camera's beacon, it means that tracker must to be in
the same metric system of my world... In fact it means that user is placed
in world position relative to camera world position. Why can't user be in
tracker space only (if user does not uses camera position it will always
implicit be related to the camera current position, i.e moves with the
camera implicitly).
Thanks in advance and sorry for any missing concept of my part! ;)
Pablo
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Opensg-users mailing list
Opensg-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensg-users
