firework show glitch
#2
Posted 05 July 2012 - 09:18 PM
Edited by phildunford, 05 July 2012 - 09:18 PM.
thegreenman
#3
Posted 09 July 2012 - 07:12 PM
They wouldn’t reveal any specific details as they areobviously attempting to protect their customer, but I guess someone obviously over lookedsomething very obvious when constructing the final fire file that was used byall the barges. The problem with a showof this scale is that things can go wrong and so it is very convenient to justblame the firing system even when it isn’t at fault……..
#4
Posted 09 July 2012 - 08:47 PM
#5
Posted 09 July 2012 - 09:01 PM
#6
Posted 10 July 2012 - 01:51 AM
Click here for Cooperman435, THE online shop for chemicals, materials and tooling
Click here to email me Personally,
Click here to email Optimum Fireworks, West Yorkshire's premium Display Company
#7
Posted 10 July 2012 - 07:09 AM
#8
Posted 10 July 2012 - 10:22 AM
FBW comes up with "show errors" where it lists errors you have made with timings etc, you can reduce the error checking to low and it will only come up with those DEFINATELY going to screw up or set it to HIGH and it comes up with everything that has a chance of piddling about on the day. I had it set to HIGH for the recent show we did at Giggleswick and the list was LONG but with ten minutes of fiddling they were all gone and we had a 100% fire rate, not bad for 1255 cues? the only item not to go up was a 3" shell at the end of a timed string (which was ANNOYING to say the least!)
not bad for my first fully automated pyromusical to a live orchestra!?
Click here for Cooperman435, THE online shop for chemicals, materials and tooling
Click here to email me Personally,
Click here to email Optimum Fireworks, West Yorkshire's premium Display Company
#9 Guest_PyroPDC_*
Posted 10 July 2012 - 10:42 AM
#10
Posted 10 July 2012 - 07:36 PM
I think at peak times shows will be planned in the office, then the firing data transferred to a laptop. I certainly have oddities when transferring things from a W2K pc to an XPpro based one and there are further complications with W7. Maybe transfer to a MAC would mean different issues.
Maybe things should be tested before firing?
Keep mannequins and watermelons away from fireworks..they always get hurt..
#11
Posted 10 July 2012 - 10:01 PM
I don't see this as a bug in the FireOne software though, it is only doing as its told after all, and there are ways and means of playing back your firefile before you let it loose on a show. The columns are clearly marked.
Surely with a $400,000 budget someone would have checked for this though?!
#12 Guest_PyroPDC_*
Posted 10 July 2012 - 10:11 PM
the owner of the display company say they think it was a virus, he say it was not human error, not a firing system error but a virus.
very strange
#13
Posted 11 July 2012 - 11:44 AM
#14
Posted 11 July 2012 - 07:04 PM
One wonders what scripting software was used and or method of conversion.
Just waiting on the official statement now. They certainly need it to protect future business.
On a side note, is anyone willing to PM what caused the short display at Oban last year and what system was used?
#15
Posted 11 July 2012 - 07:53 PM
Keep mannequins and watermelons away from fireworks..they always get hurt..
2 user(s) are reading this topic
0 members, 2 guests, 0 anonymous users