Hi,

> Well I didn't do the kinematics or the animation (though I've got a
> rollercoaster coming up next), though I would probably have an activation
> frame (if statement) for each domino and any frames greater than the
> activation frame rotate (using difference) it to a set value that can't be
> exceeded. a power statement may be required to accurately control the
> dominos rotation.

absolutely right. I played around with mechsim too, but it was way too slow 
for even a small number of dominos. So that was definitely not the way to do 
1700 dominos as I used in this first experiment.

Next I coded a macro for each domino and each domino got an explicit number, 
i. e. when it has to fall. The falling takes five successive images and 

mathematics by hand and even if you look very closely to a fallen domino row 
it looks okay.

Currently I'm working on a much bigger domino field with many areas. The 
hardest job is a good camera movement next to the falling dominos. And of 
course to get even better ideas for the arrangement of each area.

If I'm through with that I'll do the rest like floor texture, domino 
textures, normals and finish and the lighting. I'm quit sure that slows down 
rendering dramatically. The current Domino.mpg took 3h12 for 140 pictures.

Ralf

Post a reply to this message