* Chris Metzler -- Wednesday 15 December 2004 19:15:
> - the "inner marker" sound immediately upon startup, while sitting on the
> runway, that can only be stopped by starting your takeoff roll and getting
> far enough along into it.

fgfs rightfully beeps. It found that it's in the range of an inner marker
that it hasn't indicated yet. I was never annoyed by this beeping. To ban
it, one just had to pretend that fgfs has already seen this marker. Shouldn't
have negative side effects anywhere else. Of course, fgfs would still beep
if it were started in the range of a middle or outer marker. But as inner
markers are the most likely ones, we might want to have this patch applied:


RCS file: 
/var/cvs/FlightGear-0.9/FlightGear/src/Instrumentation/marker_beacon.cxx,v
retrieving revision 1.2
diff -u -p -u -0 -r1.2 marker_beacon.cxx
--- marker_beacon.cxx   5 Dec 2004 01:04:33 -0000       1.2
+++ marker_beacon.cxx   15 Dec 2004 18:53:35 -0000
@@ -249 +249 @@ void FGMarkerBeacon::search()
-    static fgMkrBeacType last_beacon = NOBEACON;
+    static fgMkrBeacType last_beacon = INNER;

m.

_______________________________________________
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

Reply via email to