Hi Craig,
[EMAIL PROTECTED] wrote:
>
> Many thanks for your swift reply. I have been through my code and cleaned up
> the few instances without proper masking when calling beginEditCP etc.
>
> Current status, however, remains :
Too bad. I had hoped that would have fixed it. :(
> In all of the above cases, as I have said, if I initialise on the client I
> have no problems because the scenegraph is treated as normal. However, if I
> attempt to simply to distribute the core parameters as part of the node core,
> and then initialise at the server side to reduce transfer of tons of geometry,
> it is inconsistent. I am using "cout <<" statements to confirm initialisation,
> as well as looking for the geometry on screen. One concern is that perhaps the
> geometry is being clipped/optimised or such before it reaches renderEnter for
> that core, is this possible?
Actually that rings a bell. Do you set the bounding box of your derived node
correctly before you send it over the cluster? If that is not set correctly the
node might be culled away before it's rendered. That might explain why it's
only
shown on one server, on the one that shows the origin.
Just try setting the bbox to something big, if you don't know how big it's
going
to be, to make sure it's actually rendered everywhere.
Hope that fixes it
Dirk
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Opensg-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensg-users
