Adobe Director Basics

ADOBE DIRECTOR BASICS
3D: Controlling action
When models are scaled, collisions may be reported incorrectly
Note: There are also other bugs which the Collide.dir movie is not designed to illustrate. These include issues with fastmoving
models, the detection of shallow collisions, and the ability to correctly resolve collisions. In many cases, you will
find that there are better solutions than relying on the collision modifier.
Custom collision detection
In some cases, you can perform collision detection very simply, without the need for any modifiers or xtra extensions.
This article will look at one of these cases. The purpose is to help you to visualize the process of collision detection and
how a collision is resolved.
Collision between two spheres
The simplest case is the detection of a collision between two spheres. Every node has a node.boundingSphere property,
which provides the center and the radius of the smallest sphere that will fit snugly around all the vertices in the node
and in its children. The coordinates and dimensions are given with reference to the world. If a spherical model has no
children, then its boundingSphere gives a perfect description of its own volume.
Here is a handler that will tell whether the boundingSphere of one model intersects that of another.
on SpheresIntersect(aModel1, aModel2)
vSphere1 = aModel1.boundingSphere
vSphere2 = aModel2.boundingSphere
vDistanceBetweenCenters = (vSphere2[1] - vSphere1[1]).magnitude
vMinimumDistance = vSphere1[2] + vSphere2[2]
vIntersection = (vDistanceBetweenCenters