Chris,
Another case of weak documentation, (setMinimumFrameCycleTime) "will
ensure that the time between the start of each successive frame is at
LEAST the specified number of milliseconds" ie this will introduce a
"delay" between displaying frames. Perhaps useful if you are trying to
make a slide show and want each frame to remain on screen for at least
one second (or whatever set time you wish). But for developers trying to
get the fastest frame rate possible it seems to be worthless.
- John Wright
Starfire Research
ChrisThorne wrote:
>
> Thanks John, I will update these.
>
> >
> > Under "Control of Framerate" you can set the MAXIMUM framerate, if your
> > machine can't maintain that level of performance framerate could be
> > lower.
>
> Curiously it sets the minimum frame rate - the delay between frames. Java3D,
> according to the API doc, will ensure at least this rate is maintained. I find this
> a bit strange as on some systems it would not be able to maintain the rate.
> I would have thought a max frame rate API call would make more sense as you
> could use it to free up cycles for other work on fast systems.
>
> Chris
>
> ===========================================================================
> 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".
