And the last bug - I have found one reason someone who starts FS9 with a 'cold cockpit' type startup is likely to have the Boomerang either fail to load or lock their system...
It seems that a cold cokpit startup that uses the FS2004 master battery variable ALSO sets the Partial Electrical Panel Fail flag. Makes sense - it will automatically switch off any electrical gauges regardless of their internal on/off status.
However my panel actually does something other than just turn off when it fails, and part of my code never expected the panel to fail if it wasn't already ON. So a loop ensues with the Mac toggling rapidly between on and off, and that in turn overloads the sound-playing gauge, and from then I guess it depends how much memory you have ::)
I have worked out a re-write for that gauge that I will email to anyone that needs it. I don't want to paste a whole lot of XML code here - sometime before Xmas I will release a stand-alone panel that will patch all this mess.
So for anyone still getting crashes on loading the Boomerang I would suggest making a startup situation with a 'hot' plane. Unfortunately deleting the Mac*.XML files won't quite work, as some of the laptop gauges are controlled by the Mac logic too. I will have to re-write the panel to fix that. Feel free to edit the XML if you want, the offending variable is (L:Mac_Power, bool), change it to something like (A:Circuit avionics on, bool) and it should work OK.
If it is STILL crashing, my fallback position is the usual RAM, drivers, phase of the moon, viruses, "you have installed games on it" (my favourite from IT support), position of the Planet Coosbane in the constellation of Wombat, evil juju spirits, etc.
Try slaughtering a goat. It probably won't work but you may feel better after,
Cheers,
Adrian Esdaile
by jordonj » Mon Nov 29, 2004 3:17 pm 
