fg-submit:
- takes alternative optional basename (used instead of dirname)
- calls optional user defined fg-upload script at the end (example on top)
- minor fixes, different color for changed binary files
- cleanup, improved documentation
submitting. Detects various kinds of ugliness, but also reports false
positives. (People aren't supposed to compress texture filer so save
40 bytes. ;-)
- bugfix in fg-submit + some more cleanup and cosmetics
"Flightgear.py
- Added the procedures view_next and view_prev
demo.py
- altered the wait five seconds to the new property path and allowed for
the script to be started after five seconds of simulation file
(/sim/time/elapsed-sec).
- the section of code was changed to a pythonism as python does not
support do-while loops, instead you break out of a continuous loop.
- Commented out the fg.wait_for_prop_eq() method as I haven't rewritten
that part of the code yet. Not sure of the best way to do that. Those
lines may not be necessary any more."
mf: removed trailing spaces; I updated the pyc, too, but I really think
it shouldn't be in CVS at all.(?)
There weren't changes to this script in a while -- it almost looks
like dead code, but isn't. I'm using this regularly. valgrind works
better than ever (version 3.0 coming out soon, and the alpha already
very usable). New address: http://www.valgrind.org/
stdin, and outputs the coordinates with FG ground elevation. This requires
a running copy of FlightGear with --fdm=null and the telnet server enabled.
Of course you need to have scenery installed for all areas you are querying.
This is not fast and the scenery load wait time may need to be tuned for
individual systems.
controls in the cockpit vs. which wheels they apply to. FlightGear now
sets /controls/gear/brake-left, /controls/gear/brake-right, and
/controls/gear/brake-parking. It should be up to the FDM to sort out
which wheels under which circumstances are affected by these controls
and ultimately what happens to the physical motion of the aircraft.
builds the ILS database from several sources and uses an external compiled
utility to crunch the math to straighten out the approaches whenever we can
match them to specific runway headings and threshold locations. This should
be *always* but our runway data is horribly outdated so that needs to be
updated soon to get into sync.
to preserve any non-usa approaches that are missing from the FAA data or
the DAFIFT data (these should be checked against current charts to verify
that these still exist and aren't being incorrectly carried along.)
data. The script is growing though to incorportate other data sources
so the name will probably have to change. DAFIFT is missing many
approaches (for instance it only has 6 approaches from the entirety of
Canada.) This is not yet ready for prime time, I'm simply committing it
to the repository so I can check it out and work on it from multiple
locations.
clearly the date of installation at that particular offset. Offsets are
usually not changed because this would imply moving intersection points,
fixes, changing approaches, and all sorts of cascading effects. GEP near
my house hasn't been adjusted since 1965; it is now about 8 degrees off the
real current magvar.
