Log.txtare explained. So search for that error text!
Log.txt. The file
Log.txtis created (and overwritten) at every startup of X-Plane in X-Plane's main directory where also
X-Plane.exe/.appresides. 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.
Outputsubdirectory of X-Plane), or sometimes even better:
Log.txtto a safe place and rename it aptly.
Log.txtis overwritten on restart of X-Plane. Let's make it clear: No
Log.txt, no bug analysis. As simple as that.
Log.txt. So even then
Log.txtis of help and needs to be provided. This last line 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
Output/crash_reports. The large
.rptfiles are - in its entirety - only readable by Laminar. A way smaller standard
.dmpfile is readable by any Windows debugger and would help a lot in analysing why the plugin LiveTraffic crashed, if the crash was inside LiveTraffic. If there is no
.dmpfile but only a
.rptfile, then the
.dmpfile can be extracted from the
.rptfile without being asked for it. The small
.dmpfile can be attached to any issue report right away.
Libraryis a hidden folder in your home directory. In a Finder window you can toggle the display of hidden folders/files by pressing [Shift+Cmd+.] The crash reports are named with application and timestamp so you should be able to pick the right one (like
X-Plane_2020-06-04-215443_Charlie.crash). Please attach the
.crashfile to your report.
Report...button. A window with crash details opens (the content of the report written to
DiagnosticsReports). Please include a copy (select text as shown below and copy text to clipboard, no screenshots please) of the header information and the call stack of the first thread into a bug report:
Don't Sendbutton...Apple won't help me