Well if you are doing this from within a behavior then perhaps you are safe
from a collision with a threaded java3d read.
But it makes me very nervous. Can the Sun guys please respond to the
viability of updating by-ref geometries outside the GeometryUpdater? What
is the risk? Why is it so much faster?
Dave Yazel
-----Original Message-----
From: Joachim Diepstraten
[mailto:[EMAIL PROTECTED]]
Sent: Friday, July 06, 2001 10:35 AM
To: [EMAIL PROTECTED]
Subject: Re: [JAVA3D] How to improve performance with GeometryUpdate?
Hi David
I also found the other problem why it stalled without using GeometryUpdate
that was because somewhere inbetween I had a System.gc() call which he
didn't like. But after synchronizing all the methods I don't have any
problems any more and it's going faaaaaaaast. 1000 times faster as with
GeometryUpdate
EOF,
J.D.
--
Jmark2k+1 (http://www.antiflash.net/jmark)
Test the performance of your PC online!
===========================================================================
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".
===========================================================================
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".
