> If you've done it some different way, I'd be curious to hear how. :)

Nope, looks like I'm doing it much the same way, though I store all three
axis' and the position of the ball in an external file. I could use that
technique you mentioned with using just two axis and generating the third to
save some filespace, but then again, it just is convenient to have it
accessible right away. The file also stores the radius of the sphere.

My macro also requires an "up"-vector to generate the axis around which the
matrix will be rotated, as I want to allow balls to roll up and down hills
etc. I'm planning on some macros that'll take, for example, an array of new
positions with up-vectors and apply these in succession, so that I can have
a more detailed "simulation" from frame to frame.

I'm not yet sure how to pull it off, but I also want to script some
functionality to have balls stay in a relative global position of the
original rolling sphere (like always on top), but roll as if moved by the
parent. One idea I had for a robot-like character was to have the main
sphere's upper hemisphere covered with some metallic surface, and in these I
set several such smaller spheres that are supposedly electromotors or such
to move the big sphere. Just neat little stuff that can animate by itself
and make the character look more alive and interesting. :-)

Regards,
Tim

-- 
"Tim Nikias v2.0"
Homepage: <http://www.nolights.de>

Post a reply to this message