Carsten Neumann ha scritto:
...
> I still don't quite understand why you want to handle the animation on
> the server side instead of doing it on the client and distribute its
> _result_ over the cluster. The main problem I see with your approach is
> that you can not just stop receiving data from the client after the
> initial scene is transmitted. For example you still want updated camera
> and light beacons.
> This means you'd have to merge some changes from the client back into
> your "pristine" state, which seems rather difficult. Since you said you
> want to keep it simple, I guess my question is: why do you believe that
> your approach is the most simple one, that gives you what you want ?
>
Well, actually my first idea _was_ to handle the animation on the client,
but since I decided it had to use a custom RenderAction method to change
the Transform nodes' Cores I came up with the described solution...
My initial idea was a client application able to:
- Load a scene from a file
- Register a custom callback via RenderAction::registerEnterFunction()
in order to be able to process the nodes thus setting up the
transformation matrices
- Transmit the result to the server
This didn't work as expected because my callback was never executed by the
client, since all the rendering stuff was done by the server and I didn't
want to call the traverse() method on the client every frame.
So, to answer your final question: I don't believe at all that my approach
is the simplest, but it was the first one that came to my mind ! ;-)
Regards,
Carlo
-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services
for just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
Opensg-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensg-users
