1,089
edits
Line 305: | Line 305: | ||
0=verbose, 5=alerts only | 0=verbose, 5=alerts only | ||
See also [[Commonly used debugging tools#fgfs.log]] | See also [[Commonly used debugging tools#fgfs.log]] | ||
-- | --log-dir=dir | ||
Save the logs in the directory dir. If dir is desktop, | |||
the logs are saved on the Desktop. This option may be | |||
given several times, using a different directory each time. | |||
Inside the specified directory, the log file will be named | |||
FlightGear_YYYY-MM-DD_num.log, where YYYY-MM-DD is the | |||
current date and num is a progressive number starting at 0. | |||
--trace-read=property Trace the reads for a property; | --trace-read=property Trace the reads for a property; | ||
multiple instances can be used | multiple instances can be used | ||
--trace-write=property Trace the writes for a property; | --trace-write=property Trace the writes for a property; | ||
multiple instances can be used | multiple instances can be used | ||
--json-report | |||
Print a report in JSON format on the standard output. | |||
The report will give useful information for debugging | |||
purposes, such as the FlightGear version, | |||
the scenery/aircraft paths in use, the TerraSync and | |||
the data download directories and the paths to | |||
navigation data files. | |||
== Related content == | == Related content == |
edits