Hello Michael,
Michael Babcock wrote:
> Thanks Carsten. Indeed I am only rendering on the servers. I added a
> root->updateVolume call before the window->render on the client, and
> that causes adjustVolume to be called on the client.
ok, that is probably the easiest solution and unless you need to free
your client from the load of updating volumes not so bad either.
> It is still not
> called on the servers, but the client volume seems to be propagated to
> the servers because they seem to be doing frustum culling correctly now.
if the servers receive an up-to-date volume from the client it is
intended that they do not recalculate it. However, if the servers get an
invalid volume they should notice that and perform the update themselves.
> So while it may be nice to fix the underlying issue, this workaround is
> good for me.
Yes, I'm still curious why the servers believe their bounding volumes
are accurate if they in fact are not. If you feel like investigating
this a little further: After the server receives a sync can you check if
the volume of the root node is marked valid and also the status of a
node a bit down the hierarchy. I'm wondering if the nodes that come over
the network are in fact marked invalid, but if the root is a node that
only exists locally on the server that information might not be
propagated to it after the sync.
Cheers,
Carsten
------------------------------------------------------------------------------
SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
http://p.sf.net/sfu/solaris-dev2dev
_______________________________________________
Opensg-users mailing list
Opensg-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensg-users
