1,388
edits
Logbook Add-on: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
|||
| Line 41: | Line 41: | ||
# <code>Date</code> – aircraft take-off date. This is the date taken from your OS, not the date in the simulator. I decided I'd know when I flew in my own time zone, in front of my own computer, rather than what the UTC or local time was in the simulation, which would not be valuable. If you have a different opinion and reasonable arguments, let me know. | # <code>Date</code> – aircraft take-off date. This is the date taken from your OS, not the date in the simulator. I decided I'd know when I flew in my own time zone, in front of my own computer, rather than what the UTC or local time was in the simulation, which would not be valuable. If you have a different opinion and reasonable arguments, let me know. | ||
# <code>Time</code> – aircraft take-off time. As | # <code>Time</code> – aircraft take-off time. As with <code>Date</code> this is the time taken from the OS. | ||
# <code>Aircraft</code> – the code name of the aircraft. | # <code>Aircraft</code> – the code name of the aircraft. | ||
# <code>Variant</code> – the code name of the aircraft as its variant. Some aircraft are available in several variants, such as the default "Cessna 172P", which includes different variants like "Cessna 172P Float". If you select "Cessna 172P," you will see <code>c172p</code> in the <code>Aircraft</code> as well as <code>Variant</code> column. If you select the float variant ("Cessna 172P Float"), you will see <code>c172p</code> in the Aircraft column, but <code>c172p-float</code> in the <code>Variant</code> column. This way you have the main group of aircraft in the <code>Aircraft</code> column, and its variants in the <code>Variant</code> column. This will allow you to extract <code>Totals</code> statistics for a general group of aircraft no matter what variant (filtering by <code>Aircraft</code>), as well as more precisely for a specific variant of a given aircraft (filtering by <code>Variant</code>). | # <code>Variant</code> – the code name of the aircraft as its variant. Some aircraft are available in several variants, such as the default "Cessna 172P", which includes different variants like "Cessna 172P Float". If you select "Cessna 172P," you will see <code>c172p</code> in the <code>Aircraft</code> as well as <code>Variant</code> column. If you select the float variant ("Cessna 172P Float"), you will see <code>c172p</code> in the Aircraft column, but <code>c172p-float</code> in the <code>Variant</code> column. This way you have the main group of aircraft in the <code>Aircraft</code> column, and its variants in the <code>Variant</code> column. This will allow you to extract <code>Totals</code> statistics for a general group of aircraft no matter what variant (filtering by <code>Aircraft</code>), as well as more precisely for a specific variant of a given aircraft (filtering by <code>Variant</code>). | ||
# <code>Type</code> – aircraft type as | # <code>Type</code> – aircraft type as one of following values: | ||
#* "heli" (helicopter), | #* "heli" (helicopter), | ||
#* "balloon" (also airship), | #* "balloon" (also airship), | ||
| Line 80: | Line 80: | ||
# ICAO airport codes include their names in parentheses. | # ICAO airport codes include their names in parentheses. | ||
# With numerical data, | # With numerical data, you are given the units in which these values are presented with conversions to other units. | ||
# At the very bottom | # At the very bottom you have an additional <code>Note</code> field, which is not displayed in the main window, due to the possibility of placing any length of text here. | ||
== Data filtering == | == Data filtering == | ||
| Line 103: | Line 103: | ||
== Recovery mode == | == Recovery mode == | ||
This add-on includes a mechanism to save the current flight status to a separate file recovery.csv every minute. If FlightGear unexpectedly | This add-on includes a mechanism to save the current flight status to a separate file recovery.csv every minute. If FlightGear unexpectedly closes due to an error, this file will be read on reboot and an entry from this file will be moved to the main log file. In this way, no flight, even aborted, should be lost. | ||
= Note = | = Note = | ||
| Line 109: | Line 109: | ||
# If you properly close the simulator during the flight ("File" -> "Exit"), the current flight status will be saved to the logbook (without landing information, of course). | # If you properly close the simulator during the flight ("File" -> "Exit"), the current flight status will be saved to the logbook (without landing information, of course). | ||
# If the simulator will be closed incorrectly during flight, e.g. via the [X] button on the window bar, or a crash occurs, the logbook data should be saved in the <code>recovery.csv</code> file. The data in the <code>recovery.csv</code> file will be automatically transferred to the <code>logbook.csv</code> file when the simulator is restarted. | # If the simulator will be closed incorrectly during flight, e.g. via the [X] button on the window bar, or a crash occurs, the logbook data should be saved in the <code>recovery.csv</code> file. The data in the <code>recovery.csv</code> file will be automatically transferred to the <code>logbook.csv</code> file when the simulator is restarted. | ||
# | # To count as a landing, the aircraft must rest on all wheels and maintain this state for at least 3 seconds. In this way, an ugly bounce off the runway will not be counted as a landing. | ||
# If you start a simulation in the air, the add-on will recognize this and start logging without waiting for take-off. | # If you start a simulation in the air, the add-on will recognize this and start logging without waiting for take-off. | ||
# If you start a simulation in the air, the add-on is unable to recognize the landing gear, so the landing pass will extend to 6 seconds (giving an extra 3 seconds to make sure the aircraft is resting on all wheels). | # If you start a simulation in the air, the add-on is unable to recognize the landing gear, so the landing detection pass will extend to 6 seconds (giving an extra 3 seconds to make sure the aircraft is resting on all wheels). | ||
# Helicopters should also be supported, although I have not tested all of them. | # Helicopters should also be supported, although I have not tested all of them. | ||
# The add-on supports JSBSim-based watercraft, although I have not tested all of them. | # The add-on supports JSBSim-based watercraft, although I have not tested all of them. | ||
| Line 117: | Line 117: | ||
# Flights with UFO will not be logged. | # Flights with UFO will not be logged. | ||
# Pausing the simulation or turning on the replay mode stops the flight statistics from being added to the log. | # Pausing the simulation or turning on the replay mode stops the flight statistics from being added to the log. | ||
# As for fuel burn, the add-on does not take into account | # As for fuel burn, the add-on does not take in-flight refueling into account. If you change the amount of fuel during the flight, the result in the <code>Fuel</code> column will be incorrect. So try to avoid it and refuel the aircraft before the flight. | ||
# Supported FG versions from 2020.1. | # Supported FG versions from 2020.1. | ||
# The minimum resolution for using the GUI is 1366x768. | # The minimum resolution for using the GUI is 1366x768. | ||