AW: [Uni-verse] Re: OSGVerse

[Marcus Hoffmann]

Hi Peter,

It will be included until the middle, latest the end of next week. Sorry for
the delay.
We will - in the first version - upload the transformation of the our
avatar-object-node using the common verse commands.
(verse_o_transform_pos_real32, verse_o_transform_rot_real32).
Wouldn't it be a more general way, if you would get the transformations from
that avatar-node in your code (because you have knowledge of our object
node, when we connect)?
Or don't you download the other objectnodes? (i think this wouldn't drop too
much performance on your side, object nodes generally are small verse
objects)

If this would be not possible, we would have to identify your node on the
renderers side (via the tag) and would have to update its coordinates, did I
get that right?

For the orientation:
OpenSG has the possibility to give us the data needed to define the
orientation. We just would have to find a way to transmit that to you.
Following the 2 approaches I described above for the
transformation-information-submission, we could just establish another tag
for that information, in our object node, or if this version is not possible
in your object node....
Then you could get the orientation information everytime you want, because
it's up-to-date.

Best Regards
Marcus

Marcus Hoffmann
Dipl. Ing. für Medientechnologie
Abt. Echtzeitlösungen für Simulation und Visual Analytics
Fraunhofer Institut für Graphische Datenverarbeitung
Phone: +49 (0)6151 155 - 639
Mail: marcus.hoffmann at igd.fraunhofer.de

 

> -----Ursprüngliche Nachricht-----
> Von: uni-verse-bounces at projects.blender.org 
> [mailto:uni-verse-bounces at projects.blender.org] Im Auftrag 
> von Peter Lundén
> Gesendet: Mittwoch, 5. April 2006 15:40
> An: Marcus Hoffmann
> Cc: consortium mailing list
> Betreff: [Uni-verse] Re: OSGVerse
> 
> Hi,
> 
> What is the status of the OSGVerse renderer. Can it handle 
> the navigation now?
> 
> As we talked about, it must also be able to attach the UVAS 
> listener object. As discussed in Stockholm the UVAS listener 
> will be named 'uvas' 
> and will have tag 'listener' in the 'uvas' tag group ( in the 
> future we have to find a better naming scheme that works with 
> more then one listener). You should find that object and 
> update its position and orientation according to the camera 
> in the visual renderer.
> 
> Have you sorted out the problem of how to get the direction? 
> I dont think there is a reference direction specified for 
> Verse but UVAS ceartenly have one, the reference direction 
> vector is (0 0 -1)
> 
> We need to be able to test the whole demo system with all the 
> components before the review and is just a few weeks left.
> 
> Best regards,
> --PLu
> 
>