A question similar to this was posted just 2 days ago. My understanding
is that anytime a BEHAVIOR is added to the scene graph, the view of the
scene could change at any time so J3D goes into a real-time rendering
mode, in other words, drawing the scene as fast as possible, pegging the
CPU. You can set View.setMinimumFrameCycleTime(long framecycletime) to
slow it down from running full hilt.
J. Lee Dixon
Software Engineer
SAIC - Celebration, FL
[EMAIL PROTECTED]
-----Original Message-----
From: Iain Milne [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, August 09, 2000 9:22 AM
To: [EMAIL PROTECTED]
Subject: [JAVA3D] CPU Utilization with KeyNav Behaviors
I've got a simple program that uses the standard KeyNavigatorBehavior
stuff,
but as soon as the code for implementing this is added, cpu usage when
the
program runs jumps to 100% and stays there, whether I'm moving around
the
scene or not.
Is there a way to stop this?
To be honest I don't actually notice a performance hit - the only reason
I
know it's doing it is from a processor monitoring app. I have seen
similar
posts recently regarding cpu usage but I don't know if they're related
to my
problem.
Thanks,
Iain
========================================================================
===
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".
