> > With the sample that was just given regarding sharing the geometry--it > still would result in 50,000 TransformGroup's being created. Not sure > off hand how or if it's possible to avoid that.
In Java 3D 1.3beta1, the memory footprint of TG was half of Java 3D 1.2.1_03. Plus a significant memory deduction in Java 3D internal structures. I was able to render 20,000 spheres without changing the JDK's heap size using Java 3D 1.3 beta1. For 50,000 spheres, I need a heap size of 180m, ie. ~3.6 k of memory/sphere. Part of the challenge in computing is to manage the scare resources we have, and Karsten has memtioned some interesting ideas to address it. Hope this helps. - Chien Yang. Java 3D Team. =========================================================================== 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".
