FireShow is a 3D fireworks display design and visualization software developed in C++ and OpenGL. Inspired by professional tools like FWsim and Finale 3D, this project allows designers to create, synchronize, and visualize complex pyrotechnic effects in a real-time 3D environment.
Do you have any idea if either FWsim or Finale 3D were implicated in any of the “all at once” firing errors (some may say enhancement?) that affected e.g. San Diego 2012 or Oban 2011 displays ?
Is there any protection against this kind of problem in FireShow ?
Someone I know in that industry described the San Diego event as being the result of playback scrubbing; by either dragging or accidentally clicking somewhere on the timeline. Obviously heard second hand, but its a close community so I generally trust it - Wikipedia says it was a corrupted file
Said Santore the firework producer in delicious bit of Jersey-Italian circumlocution:
> It was a computer error. A set of instructions that were given that we didn’t necessarily create, that was created by the system. [0]
Sounds consistent with a scrubbing error that they’d love to talk about in ways that sounded like it was the computer wot dunnit…
[0] https://www.thrillist.com/entertainment/nation/an-oral-histo...
I spent a couple years doing pyro shows, and found it interesting how the various show leads would plan the timings; proper cadence and shell size choice can really help make a show interesting before the finale