Hm, may a SUN guy should comment on the topic? SharedGroups are a powerful concept - if they work!
? Is it a bug, then will it be fixed? ? Is it a misunderstanding, then how should they be used? ? If non of the former, it should be documented that Links/SharedGroups should be avoided bc. they don't work and replaced by cloneTree() whereever possible? There are some constructs that are hard to do w/o SharedGroup, e.g. if you wanted to spin all trees on a terrain synchronously by just updating a single TG. Currently this can be done for a tree typically is a trivial sub-scenegraph. But dare the tree is a fractally computed one, that consists of many Nodes itself! See the effect from my sample.... - J ----- Original Message ----- From: "Lan Wu-Cavener" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, July 05, 2002 9:05 PM Subject: Re: [JAVA3D] Trouble with Link/SharedGroup - is it a Java3D bug?? > Yes, memory usage is huge, performance is poor compared to what I am using > (Geometry By-Reference) now. I only turned the visibility on or off to > avoid detaching the BranchGroup( another performance drop). But has never > had geometry being altered or mix up. I don't use beta version either. > > > At 01:54 PM 7/5/2002 -0500, you wrote: > > >Increased memory usage, poorer than expected performance, renderbin > >crashes (stopped when sharedgroups/links were removed), and geometry > >seemingly getting altered and mixed up (a leg on one of my characters > >suddenly replaced by a tree). That sort of thing. That was with 1.2 > >though... haven't tried with the most recent beta. > > =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff JAVA3D-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
