Okay-- I did not read ALL the messages in detail (and who would).But it
seems to me that next to none of the Java3D users botherwith those nasty
'stopovers', which an animated scene has to doin order to let the
GARBAGE collector do it's job !
Or has everyone Xeon systems with perfect OpenGL accelleration ?
My 333Mhz + TNT just doesn't make these stops go away, visually that
is...So, if there is no 'official clean' way to get rid of the garbage
collector while rendering (other than some JIT-JVMPI-who-knows
-what-native-call-scheme), I simply can't accept Java 3D 1.1 as a 3D API
for professional real-time 3D applications !
I guess, one has to wait for the GigaHz CPU, a change in the GC scheme or
get visually annoyed while watching the flickering 3D-scenes.
I also wonder if similar stops are also visible in the Java 2D API(when
animating of course) !?
"java -Xnoclassgc [Class]" won't help either.
If there IS a way to get around the GC, please call me stupid and post
that information to the interest group (and the GC-off-switch too).
jwin
=====================================================================
To subscribe/unsubscribe, send mail to [EMAIL PROTECTED]
Java 3D Home Page: http://java.sun.com/products/java-media/3D/
