Algodoo

WOW! This is pretty cool.

Questions and suggestions:

1. In the preset show, I see colored balls, but after I clear the current show, I no longer see any colored balls (except for one). Where do the colored balls come from that define the firework colors?

2. The balls with text in them need a chart of some sort that explain what those letters mean (F, 5, P, F2, etc).

3. All three firework tubes fire at the same time. It would be an added feature if you could make timing delays between the three tubes. Also be able to adjust time delays between each set of fireworks.

4. In your description you meanioned something about sharing your shows with the world. How does that work?

Again, nice job!

EDIT: I forgot one other thing. When I drag the "angle" balls, they rotate, and then show the wrong angle when I place them in the show controller. Even when I disable rotation in the drag tool, the balls still seem to rotate. Do you see this as a problem?

Thanks

Thanx for the kind words.

1. (and Edit) Cloning. I do all the show editing in create mode as opposed to play mode. Just Ctrl-Drag to clone as many balls as you need. I also use the Move tool as opposed to the finger so there is no rotating. The rotating doesn't really matter though. The only thing that matters is the color of the ball.

2. I actually had planned on doing that originally, but I decided it would be too much in the notes box and that trial and error would allow you to see what each does anyway. What I did was to leave the first time cue open while designing the shows until I was finished. That way, I could use that slot to try things out. Just play until that one fires and then Ctrl-Z. When I got the shot like I wanted, then I would move all the balls over to where I wanted it to happen later in the show.

3. You can do that by staggering time cues firing only one tube per time cue. It's not the best system I am sure, but it works. I originally had 64 cues and intended to run the show faster. However, with 64 cues, I was hitting the Out of Memory warning very quickly. So, I cut it back to 32 cues. Adding a timing variable would require another line of balls for each tube which would cause more memory issues. I seem to be pushing the limits of Algodoo with this one.

4. Look at the author's notes to the left of the scene.

Ok. Just plain awesome.

Great show!
Sripts are good and complex but not optimizet with a lot of unnecessary calc (which is lag). For example why you use eval() for resources? In every postStep! Crazy.