Hi Andrew,
The current KeyNavigator implementation is similar to Billboard
and DistanceLOD in that it uses WakeupOnElapsedFrames(0). This
means that it will trigger, even though it should be idle. This
is most likey why your CPU usage is so high. The only workaround
would be to copy the KeyNavigator code into your application and
modify it to be more passive.
Doug Twilleager
Java 3D Team
> MIME-Version: 1.0
> X-Priority: 3
> X-MSMail-Priority: Normal
> X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
> Subject: Re: [JAVA3D] KeyNavigatorBehavior and thrashing
> Comments: To: [EMAIL PROTECTED]
> To: [EMAIL PROTECTED]
>
>
> Thanks for the response!
> By thrashing, I mean the application is using near 100% of CPU time, only when
KeyNavigator is used. I have 128M physical RAM, and am running Java with -mx64m.
The scenes I'm testing with have only several thousand geometric primitives
distributed across several Shape3Ds.
>
> -----Original Message-----
> From: Daniel Selman <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
> Date: Saturday, October 16, 1999 12:43 AM
> Subject: Re: [JAVA3D] KeyNavigatorBehavior and thrashing
>
>
> Andrew,
>
> I've not had any problems using KeyNavigator (other than the documented
ones). I can't think why you would be "thrashing". I take it you mean the HD is
thrashing. How much physical RAM have you got? 64 MB is a practical minimum for
Java 3D. What kind of scene are you manipulating?
>
> Sorry I can't be of more help,
>
> Daniel Selman
> [EMAIL PROTECTED]
> http://www.tornadolabs.com
>
>
>
===========================================================================
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".
