> Michael got it right: the 100% CPU utilization happens because Java3D is
> animating the scene with continuous updates. Using a WakeOnElapsedFrame(0)
> makes Java3D continously update, since it expects the scene graph to change
> after each frame, so it wants to display the changes as soon as possible.
Is it possible to stop the updates while making changes to the scene graph?
I takes about 5 seconds on a 300 MHz machine to change a part of the
scene graph in my application (only about a dozen nodes).
(Ultra-10 300 MHz or Intel II 300 MHz)
Would it be faster if I stopped the continuous rendering process?
=====================================================================
To subscribe/unsubscribe, send mail to [EMAIL PROTECTED]
Java 3D Home Page: http://java.sun.com/products/java-media/3D/
