> Date: Wed, 26 Feb 2003 11:33:35 -0500 > From: RWGRAY <[EMAIL PROTECTED]> > > Doesn't this assume you are not interested in *any* kind of transparency or > rendering order?
Yes, this has been missing from the discussion so far. There's always a tradeoff. By decreasing the granularity of the scene graph structure, you inhibit the effectiveness of transparency sorting. The granularity is not great to begin with -- transparency sorting is done on a per-Geometry basis -- but if you combine Geometry you'll get more errors. Combining geometry also makes view frustum culling less effective. Picking granularity is also decreased, which makes for more work for the app. On balance, though, reducing the number of TransformGroups in the scene graph is an effective optimization for most apps. Reducing the memory footprint of TransformGroup and Transform3D was a significant effort for the Java 3D 1.3 release -- they're less than half the size from 1.2. They're pretty much bare bones right now for the functionality they need to support. -- Mark Hood =========================================================================== 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".
