Thanks for the tips. On Friday 16 April 2004 23:58, Andy Ross wrote: > If it is aircraft-specific, then the mechanism of putting it into the > -sound.xml file is probably exactly what you want.
I would say that it's more instrument-specific than aircraft-specific. > Things like > playing sounds from the UI are more problematic from the current > interface. > > I'd start with a single beep.wav with an XML definition like: > > <sim> > ... > <fx> > ... > <beep> > <name>engstart</name> > <path>Sounds/beep.wav</path> > <property>/tmp/somewhere/beep</property> > </beep> > > Now you can trigger the beep by toggling the property from false to > true. With a little work with settimer(), you can get it to beep with > different patterns and frequencies, etc... Let me know if you need > more help. > > Hopefully I haven't misunderstood the sound configuration files. This > isn't exactly one of my areas of expertise. :) I'm not either, but I don't think it's possible to put sound configurations into the instrument configuration XML files, or is it? Note that I'm not under the impression that that's what you suggested, or was it? :-} I'm confusing myself. Anyway maybe the ideal solution would be if there were a fgcommand to play sounds. That would then be trivial to call from Nasal, right? -- Roy Vegard Ovesen _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
