✈️
LiveTraffic
DownloadSupport
  • LiveTraffic
  • Introduction
    • Features
      • Flight Data Channels
      • Display of Aircraft
      • Snapping to Taxiways
      • TCAS
      • Accessing LiveTraffic's Aircraft Data
      • Feeding Data to LiveTraffic
    • Requirements
    • Limitations
  • Setup
    • Installation
      • Step-by-Step
      • adsb.fi
      • OpenSky Network
      • Open Glider Network
      • ADSBHub
      • ADS-B Exchange
      • RealTraffic
      • FSCharter
      • SayIntentions
      • ForeFlight
      • XPMP2 Remote Client
    • First Steps
    • LiveTraffic and other multiplayer Clients in parallel
    • Configuration
      • Settings - Basics
      • Settings - Weather
      • Settings - A/C Labels
      • Settings - Advanced
      • Settings - CSL
      • Settings - Debug
  • Using LT
    • Message Area
    • Menu Items
      • Keyboard and Button Commands
    • Status Information Window
      • Aircraft List
      • Messages
      • Status / About
      • UI Settings
    • Aircraft Information Window
      • External Camera View
      • Hide and Impersonate Aircraft
  • Reference
    • Help, Support, Bugs, Issue
    • FAQ
    • Change Log
    • Known Issues
    • Video & Screenshots
    • Privacy
Powered by GitBook
On this page
  • Help and Support
  • Bugs, Defects, Problems, Issues, Suggestions
  • What to do immediately
  • X-Plane quit unexpectedly
  1. Reference

Help, Support, Bugs, Issue

What you can do yourself in case of problems and how to get further support

PreviousHide and Impersonate AircraftNextFAQ

Last updated 5 months ago

Help and Support

Your best bets for getting clarification on your question or problem are:

  1. LiveTraffic has a and it has [?] buttons in all windows. Use and click them! They bring you here, to the right page.

  2. Search this documentation

    1. There is a search box in the top right corner. Just enter a few words. This documentation is very comprehensive, hoping to cover all usual aspects of operating LiveTaffic. Every question I have answered once is reflected in this documentation. Even a number of typical messages from the or your Log.txt are explained. So search for that error text!

    2. Check . You question might be frequently asked...and answered.

    3. Check the . There is stuff I know about.

  3. Check your Log.txt. The file Log.txt is created (and overwritten) at every startup of X-Plane in X-Plane's main directory where also X-Plane.exe/.app resides. It contains diagnostic information of X-Plane itself and all plugins. It is just a plain text file. Double click it...it will open in your standard text editor. You don't need to understand every line of it. If we talk about LiveTraffic then just search for lines starting with "LiveTraffic" (usually [Ctrl+F] starts a search). Chances are you find "ERROR" or even "FATAL" lines written by LiveTraffic. They will point you into the right direction. Every plugin author as well as Laminar will request this file when asked for help. So do I. To make it very clear-cut: No Log.txt, no help. I must have this file to be able to help you.

  4. Ask for more help in the if none of the above helps. Please follow the guidance for support requests given in . Attach your complete Log.txt file to a new post.

Bugs, Defects, Problems, Issues, Suggestions

...are all welcome, provided, they come in a structured and informative way.

I will not follow up on issues like "I once saw an aircraft that...".

If you find a pattern, though, like "Using channel Abc, many planes around KXYZ, especially in the evening, tend to blablabla", then you would have time to switch , maybe even activate network raw data logging () and shoot some meaningful screenshot including an . And then I might be able to follow up.

What to do immediately

When you find a problem there are a few things you do right away:

  • [Shift-Space] takes a screenshot (which lands in the Output/screenshots subdirectory of X-Plane), or sometimes even better:

  • [Ctrl-Space] takes a video.

  • Copy away Log.txt to a safe place and rename it aptly. Log.txt is overwritten on restart of X-Plane. Let's make it clear: No Log.txt, no bug analysis. As simple as that.

X-Plane quit unexpectedly

Even if X-Plane quits unexpectedly ("Crash to Desktop" or CTD) it usually writes some last lines into Log.txt. So even then Log.txt is of help and needs to be provided. This last line may or may not indicates which plugin was the culprit...or if it was at the core of X-Plane. There are several pieces of software that provide your simulator experience. All could fail.

If Log.txt ends with something like this:

LiveTraffic crashed in thread LT_RT_Direct by signal 11, please upload this Log.txt and the following dump file to the LiveTraffic Support Forum:
Output/crash_reports/LiveTraffic_2024-12-05_22-55-26.dmp
--=={UUID: 2f460e17-d708-4203-bfc4-e5d84614b34a}==--

then chances are good that it really was LiveTraffic. Please then do as asked:

LiveTraffic writes a dump file of the following naming convention under your main X-Plane folder:

Output/crash_reports/LiveTraffic_yyyy-mm-dd_hh-mm-ss.dmp

If situation allows, and display the a/c in question (the AUTO feature might come in handy), then do another screenshot with that information.

Take both files, Log.txtand LiveTraffic_*.dmp, zip them together, head to the , open a post there, describe what happened, and attach the zip archive.

open an A/C Info Wnd
Support Forum
message area
FAQ
Known Issues
LiveTraffic Support Forum
this introductory post
Debug settings
a/c info window
help menu
log level to Debug