Vasilios,
Although I cannot speak for the J3D collision detection code, 100% processor
utilization is not necessarily a problem. Any thread that is running. E.g.
while( true )
{
// do nothing... or even yield (but to what!)
}
Will consume 100% of the processor IF the processor has nothing else to do! What you
should be concerned about is how readily the thread yields to other threads in your
application or the OS. The thread priority etc.
This is managed by the OS thread scheduler, and needs to be addressed in the context
of how the threads in your application need to coexist with the OSes threads.
All the best,
Daniel Selman
[EMAIL PROTECTED]
http://www.tornadolabs.com
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Vasilios
> Darlagiannis
> Sent: Monday, June 07, 1999 11:47 AM
> To: [EMAIL PROTECTED]
> Subject: [java3d] Processor utilization
>
>
> Hi everyone,
> I have tried all the examples about collision detection
> that have been send in the mailing list, but all of them have
> the same problem. They are making 100% utilization of the
> processor and in some more abvance cases this becomes
> a problem. Is it natural that the utilization is 100%? Or
> those examples are missing something?
> I tried to solve the problem by setEnable(b) where b is
> true when the mouseBehavior detects a motion and false
> otherwise, but it didn't work. Does anybody have another idea?
>
> Cheers,
>
> Vasilis
>
>
> =====================================================================
> To subscribe/unsubscribe, send mail to [EMAIL PROTECTED]
> Java 3D Home Page: http://java.sun.com/products/java-media/3D/
>
=====================================================================
To subscribe/unsubscribe, send mail to [EMAIL PROTECTED]
Java 3D Home Page: http://java.sun.com/products/java-media/3D/
