1,388
edits
No edit summary |
|||
| Line 43: | Line 43: | ||
# <code>Time</code> – aircraft take-off time. As for <code>Date</code> this is the time taken from the OS. | # <code>Time</code> – aircraft take-off time. As for <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 more than one variant, for example, we have an aircraft called "Cessna 182S" which also includes a variant called "Cessna 182T." If you select "Cessna 182S," you will see <code>c182s</code> in the <code>Aircraft</code> as well as <code>Variant</code> column. If you select "Cessna 182T", you will see <code>c182s</code> in the <code>Aircraft</code> column, but <code>c182t</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. You should know that this is not a rule, and some aircraft do not distinguish between variants, such as the Cessna 172P. Then you will always see a variant of the aircraft in both columns, e.g. <code>c172p-amphibious</code>. If you want, you can manually correct the <code>Aircraft</code> column with a generic aircraft name, e.g. <code>c172p</code>, and leave <code>c172p-amphibious</code> 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 a one of following value: | # <code>Type</code> – aircraft type as a one of following value: | ||
#* "heli" (helicopter), | #* "heli" (helicopter), | ||
| Line 64: | Line 65: | ||
# <code>Night</code> – number of hours spent flying during the night. | # <code>Night</code> – number of hours spent flying during the night. | ||
# <code>Instrument</code> – the number of hours flown during the IMC (Instrument Meteorological Conditions). | # <code>Instrument</code> – the number of hours flown during the IMC (Instrument Meteorological Conditions). | ||
# <code>Duration</code> – total duration of the flight in hours, as the sum of <code>Day</code> and <code>Night</code>. The instrument is not added up here, as it is simply counted separately, regardless of whether it was day or night. | # <code>Duration</code> – total duration of the flight in hours, as the sum of <code>Day</code> and <code>Night</code>. The instrument is not added up here, as it is simply counted separately, regardless of whether it was day or night. **Duration** is calculated in real time, so if you speed up or slow down the simulation time, it will not be affected. | ||
# <code>Distance</code> – total distance flown from take-off to landing, in nautical miles. | # <code>Distance</code> – total distance flown from take-off to landing, in nautical miles. | ||
# <code>Fuel</code> – total fuel burned, in US gallons. | # <code>Fuel</code> – total fuel burned, in US gallons. | ||
| Line 84: | Line 85: | ||
== Data filtering == | == Data filtering == | ||
The add-on allows you to filter some columns in the main log window. At the moment you can filter by the "Date" (as a year), "Aircraft", "Type", "Callsign", "From", "To", "Landings" and "Crash" columns. To use filtering, hover the mouse cursor over a column name (it will be highlighted) and click it. A new window will appear with a choice of values. For filtering on the "Aircraft" column, these will be the IDs of aircraft you have flown before. For filtering by the "Type" column, these will be the names of aircraft types, etc. Each window with filters also has the "Default All" position, which means that the filter will be turned off and all items will be shown. When the filter is enabled, a <code>(!)</code> sign will be shown next to the filtered column to warn that the filter has been used. | The add-on allows you to filter some columns in the main log window. At the moment you can filter by the "Date" (as a year), "Aircraft", "Variant", "Type", "Callsign", "From", "To", "Landings" and "Crash" columns. To use filtering, hover the mouse cursor over a column name (it will be highlighted) and click it. A new window will appear with a choice of values. For filtering on the "Aircraft" column, these will be the IDs of aircraft you have flown before. For filtering by the "Type" column, these will be the names of aircraft types, etc. Each window with filters also has the "Default All" position, which means that the filter will be turned off and all items will be shown. When the filter is enabled, a <code>(!)</code> sign will be shown next to the filtered column to warn that the filter has been used. | ||
After using the filter, the "Totals" row will also be updated with the filtered data. In this way, you can see statistics for a specific aircraft or types of aircraft. | After using the filter, the "Totals" row will also be updated with the filtered data. In this way, you can see statistics for a specific aircraft or types of aircraft. | ||
| Line 103: | Line 104: | ||
# 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 | # 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. | ||
# For the add-on 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. | # For the add-on 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. | ||
| Line 113: | Line 114: | ||
# 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 the change in the amount of fuel during the flight. When 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. | # As for fuel burn, the add-on does not take into account the change in the amount of fuel during the flight. When 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. | |||
edits