::> Don't forget to setSchedulingBounds(bounds) for your
::Behaviour object.
::> Every time an active ViewPlatform enters the region AND after the
::> number of elapsed frames, your behaviour will wakeup.
::
::My understanding of ViewPlatformEntry is that it works around
::view in all directions, not just in view frustrum... But if
::I'm wrong then it is exactly what I wanted.
Mmh, perhaps YOU are right. I can not figure out the difference between:
WakeupOnActivation / WakeupOnDeactivation
and
WakeupOnViewPlatformEntry / WakeupOnViewPlatformExit
But stop. I read in the Spec (10.4 How Java 3D Performs Execution
Culling):
<schnipp>
In essence, the Java 3D scheduler performs the following checks:
* Find all Behavior objects with scheduling regions that intersect
the active ViewPlatform object's activation volume.
* For each Behavior object within the ViewPlatform's activation
volume, if that behavior's WakeupCondition is true, schedule that
Behavior object for execution.
</schnapp>
So the engine seems to determine the intersection between ViewPlatform's
activation volume
and scheduling regions by default before checking conditions.
But for what do we need
WakeupOnActivation,WakeupOnDeactivation,WakeupOnViewPlatformEntry and
WakeupOnViewPlatformExit ???
::
::Artur
::
::==============================================================
::=============
::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".
