Thanks for the response, Doug.
It's good to hear that progress is being made in these areas (rendering
speed and memory footprint). The smaller and faster Java3D is, the better
it will look compared to whatever 3D technology Microsoft is cooking up in
their kitchen-of-horrors :)
>The memory increase comes from Java 3D making a copy of the geometry
>internally. In 1.2, we have included geometry by reference which
>gets rid of this copy.
We were using Java3D 1.2 in our test. Our test case is simply a slightly
modified version of FrameTest. By using the 'Box' utility class, we figured
that Java3D would be able to share geometry across the boxes (as the docs
for Box suggest).
I have attached the source for the test for the entertainment of the public
at large...
FrameBehavior.java
FrameTest.java
