Hi !
Featured games (85)
games approved by the League of Dukes
Games in Showcase (636)
Games in Android Showcase (178)
games submitted by our members
Games in WIP (688)
games currently in development
News: Read the Java Gaming Resources, or peek at the official Java tutorials
    Home     Help   Search   Login   Register   
Pages: [1]
  ignore  |  Print  
  setSchedulingBounds() question  (Read 1794 times)
0 Members and 1 Guest are viewing this topic.
Offline Yoda

Junior Newbie

« Posted 2004-02-13 11:56:43 »

I'm starting a little project in Java3D and I'm trying to get a better understanding of how setSchedulingBounds() works.

To give a very simple example, consider the following lines from

// a bounding sphere specifies a region a behavior is active
      // create a sphere centered at the origin with radius of 1
      BoundingSphere bounds = new BoundingSphere();

No problem so far.  ColorCube rotates fine.

Now change:
BoundingSphere bounds = new BoundingSphere();

new BoundingSphere(new Point3d(0.0, 0.0, 0.0), 1.0);

Still OK, as I understand things, this is pretty much the same as the empty constructor.  ColorCube still rotates fine.

Now, if I comment out the following line, the ColorCube won't rotate.  Also as expected.

Here's my problem/question:
If I change the default position of the bounding sphere or give it a really small radius, the ColorCube still rotates fine.  Should the bounding sphere intersect the ColorCube at any (however small) position or at all positions?  I'm failing to see a tight correlation between the location/size of the bounding sphere and the rotation.

For a ColorCube constructed with a scale of 0.4, the rotation will work for the first bounding sphere below, but not for the second.

This works:
BoundingSphere bounds = new BoundingSphere(new Point3d(30.0, 30.0, 30.0), 0.0001);

This doesn't:
BoundingSphere bounds = new BoundingSphere(new Point3d(40.0, 40.0, 40.0), 0.0001);

Thanks for your help!
Offline Yoda

Junior Newbie

« Reply #1 - Posted 2004-02-13 20:10:09 »

Think I found my answer in Selman's book (pg. 165).  "When the Bounds for a Behavior and the ViewPlatform's activation radius intersect, the Behavior is scheduled for processing."

My understanding (now) is that the Bounds for a Behavior don't have to be anywhere near the actual object(s) that the Behavior is performed upon.  If I place a ColorCube out of site, but my rotator Behavior bounds intersect the ViewPlatform's activation radius, the ColorCube will spin out of sight.  Likewise, if I place my ColorCube in view, but add rotator Bounds outside of the ViewPlatform's activation radius, the ColorCube will be visible, but won't rotate.

Hopefully a moment of clarity.
Pages: [1]
  ignore  |  Print  
You cannot reply to this message, because it is very, very old.

Dwinin (75 views)
2015-11-07 13:29:08

Rems19 (81 views)
2015-10-31 01:36:56

Rems19 (79 views)
2015-10-31 01:32:37

williamwoles (107 views)
2015-10-23 10:42:59

williamwoles (93 views)
2015-10-23 10:42:45

Jervac_ (112 views)
2015-10-18 23:29:12

DarkCart (137 views)
2015-10-16 00:58:11

KaiHH (118 views)
2015-10-11 14:10:14

KaiHH (158 views)
2015-10-11 13:26:18

BurntPizza (173 views)
2015-10-08 03:11:46
Rendering resources
by Roquen
2015-11-13 14:37:59

Rendering resources
by Roquen
2015-11-13 14:36:58

Math: Resources
by Roquen
2015-10-22 07:46:10

Networking Resources
by Roquen
2015-10-16 07:12:30

Rendering resources
by Roquen
2015-10-15 07:40:48

Math: Inequality properties
by Roquen
2015-10-01 13:30:46

Math: Inequality properties
by Roquen
2015-09-30 16:06:05

HotSpot Options
by Roquen
2015-08-29 11:33:11 is not responsible for the content posted by its members, including references to external websites, and other references that may or may not have a relation with our primarily gaming and game production oriented community. inquiries and complaints can be sent via email to the info‑account of the company managing the website of java‑
Powered by MySQL Powered by PHP Powered by SMF 1.1.18 | SMF © 2013, Simple Machines | Managed by Enhanced Four Valid XHTML 1.0! Valid CSS!