Plugins > LiveTraffic > Aircraft displayed
is on, which is the default.Settings > Input Channels
and enable some, at least OpenSky.Log.txt
.Log.txt
. There should be many lines likeLog.txt
that you just produced.Log.txt
file you keep talking about?X-Plane.exe/.app
.Log.txt
file?Log.txt
in X-Plane's main folder, but containing more detailed information. In Advanced Settings change Log Level to "Debug" if you run into problems and want to ask for help in a forum. From that point on LiveTraffic writes fairly detailed infos into Log.txt
. Recommended to reset to, say, "Warning" after you problem is solved.HTTP response is not OK but 403
and
ADSB Exchange Live Online: Channel invalid and disabled after too many errors
.ADS-B Exchange: API Key missing. Get one at adsbexchange.com and enter it in Basic Settings.
Plugins > LiveTraffic > Aircraft displayed
menu item for an up-to-date number of displayed aircraft.)Log.txt
will tell you, look into it, search for "LiveTraffic"! The following 3 causes are the most often:LiveTraffic
folder with appropriate installation under <X-Plane>/Resources/plugins
(so that it didn't get moved or trashed accidently). Basically go back to installations.LiveTraffic
and nothing else, which is due to X-Plane's logic for searching for plugins: The actual binary to load (LiveTraffic.xpl
) must have the same name as the plugin folder (LiveTraffic
)..../Resources/plugins/LiveTraffic/64/win.xpl : Error Code = 126 : The specified module could not be found.
Download and install vc_redist.x64.exe.LiveTraffic <timestamp> FATAL src\LTVersion.cpp:70/CalcBetaVerTimeLimit: BETA-Version limited to <some date in the past> has EXPIRED -> SHUTTING DOWN!
in your Log.txt
. Go and update to latest version.LiveTraffic 1551304182.7 ERROR src\LTAircraft.cpp:635/ReadFlightModelFile: Config file '.../FlightModels.prf' first line: Unexpected version LiveTraffic 1.0, expected 1.1...trying to continue
Log.txt
and in the message area then you have probably only updated your LiveTraffic executables in the 64
folder, but not the other files. FlightModels.prf
is quite important as it defines parameters of flight modelling. That's why LiveTraffic complains if it expects something newer.Log.txt
includes something like
LiveTraffic/64/mac.xpl: code signature in (.../mac.xpl) not valid for use in process using Library Validation: library load disallowed by system policy
Labels Shown
, which can be bound to a keyboard shortcut or joystick button.A
it is impossible to derive a flight path. I could draw the plane into the sky, but wouldn't know where it is headed for. Keep in mind that LiveTraffic needs to calculate positions for each plane during each drawing cycle, so depending on your frame rates this makes 20-60 position updates per second per plane. And you want to see the plane move swiftly.A
. Heading and speeds (horizontal and vertical) will all change after passing A
. They are not a true and reliable vector to the next location B
, which is 10 to 20 seconds later. And a plane travels far in 10 to 20 seconds (for example, 1.4nm in 20s at 250kt).A
and B
you'll need to know both A
and B
. So a plane can leave A
only once we have also received B
. The buffering time exists and is required to allow for all planes' B
to be known before they reach/leave A
.C
would be necessary to compute at which heading and speed to arrive at B
so we can smoothly without too sharp edges continue to C
...and so on. The smoother the path, the more data is needed in advance. There is hundreds of lines of code about data smoothing in LiveTraffic because the tracking data can be extremely inaccurate and jumpy. And then LiveTraffic even needs to discard unreasonable data items. There's better something in the buffer to keep the plane flying then...A
or B
mentioned above. LiveTraffic receives data points before touch-down and lift off and hopefully also points after that, but not for the precise moment, although this is the moment of a significant change in the flight regime. So where does the plane lift off or touch down? And at which speed? How quickly does the plane accelerate or decelerate? When does it rotate or flare? How steep does it climb after lift-off? You'll need a few points along the take-off path in advance to calculate all that.xsb_aircrafts.txt
in your CSL model folders. Copy them again from BB_IVAO_vert_offsets*.zip
, see step-by-step instructions.model_typecode.txt
. This file has been compiled from information of the OpenSky aircraft database and includes pretty educated guesses about which model text matches which ICAO aircraft type designator.Log.txt
like this of there is no ICAO aircraft type available:Log.txt
(see tips on keeping it open here).xsb_aircraft.txt
file, which defines available CSL models for LiveTraffic.xsb_aircraft.txt
files in your CSL model folders. LiveTraffic reads all of these files into a cache during startup.LiveTraffic/Resources/related.txt
combines all similar looking models into one line, which make up such a group. Each ICAO type is allowed to appear at maximum once in the entire file. The idea is to use a A320 model if a necessary A319 model is not available.Log.txt
like this:Log.txt
: Lower numbers are better matches. For example: The first match (Quality = 56
) is a comparibly bad one...just look at the aircraft class: Wanted is a "L1P" aircraft (one piston engine), the best we found is an L2T (two turbo engines).FlightModel.prf
) then the descend is continued straight ahead with constant sink rate to the ground where the plane flares, touches down, and rolls out to a complete stop, then disappears.
If LiveTraffic finds a suitable runway (+/-10° of current heading, reasonable sink rate) it will guide the plane down there.
This special handling is due to the fact that ADS-B receiver coverage is typically worse the lower planes fly. Missing data during approach is quite common.
LiveTraffic will never simulate taxiing without tracking data.