Filter for...hex code
Filter all flight data for one specific aircraft. Good for code debugging purposes.
The same search options as in an A/C Info Window apply: Transponder Hex Code, Registration, Call Sign, Flight Number, SquawkCode, Index.
Log.txt: Set Log Level = "Debug"
Has the same effect as setting Log Level = "Debug" in the Advanced Settings. When deactivating here, Log Level is reset to Warning.
Provided as a courtesy, in case users search here when asked to set Log Level to Debug.
Log.txt: Log a/c positions
If Logging Level is Debug and an aircraft is selected, enabling this setting produces detailed output into
An aircraft is selected if it is filtered (see previous option) or if it is selected in an A/C Info Window.
Log.txt: Log model matching
This places some lines of debugging information into
LTRawFD.log: Log raw network flight data
With this option a separate output file named
Note 1: Unlike
Note 2: This option is not written to the config file but returns to disabled with restart.
These are options for CSL model builders to test their models with LiveTraffic. Each of the 3 fields overrides the otherwise variable strings that LiveTraffic hands over to the multiplayer library to feed into the model matching algorithms.
Or in other words: You can force LiveTraffic to pick a specific model regardless of the actual aircraft as per tracking data. You can read about the details of the matching process here.
These settings affect which model is picked for all newly created aircraft. So you'll have to wait for the next new aircraft to be created to see an effect.
Changes to the settings are announced in the message area. If you fill all three fields for an exact model/livery match make sure to also tab out of the last field to make LiveTraffic accept the value.
There are no validations on data input. This is meant for debugging purposes: You can test whatever you like.
Only filled values are overwritten; clear values will be filled with real information as per received tracking data. To return to standard processing clear all three values.
These settings are not written into the config file, hence latest on startup LiveTraffic is back to standard processing, i.e. without forced values.
You definitely want to have Log model matching enabled and watch
Log.txt live while testing (see Tips on Testing for how to open a terminal window and keep watching).
ICAO a/c type
The ICAO aircraft type as per ICAO Doc8643.
The operator, usually the airline, as an ICAO airline code.
Matches against the
A text specifically identifying an individual livery. LiveTraffic fills the registration (tail number). So it is theoretically possible to define up to one CSL model per airframe for most realism.
Matches against the