Support, Bugs, Suggestions

are all welcome; if they come with some crucial infos everything goes faster

Support and Suggestions

• Customer Portal

  • "Technical Support"

  • "Suggest a New Feature"

• Discord

Bugs

When you think something is wrong, then please go to the Customer Portal and click on "Report a bug". This gives us the chance to handle all reports in an organised way.

Please include the following information in any bug report:

• File Log.txt, which you find in your main X-Plane folder, where also X-Plane.exe sits. This is X-Plane's standard log file any developer will request. Also the FSC plugin writes into it. This file is overwritten on startup of X-Plane, so make sure to secure the version of the flight in which you experienced the bug!

• File FSCRawNetw.log This file contains all network requests and responses between the plugin and the server. It is only written if Log raw network data is selected in the Settings. For beta versions, this is on by default. This file is handled similar to Log.txt: It sits in the same folder and is also overwritten upon restart.

• Brief, but meaningful description:

  • Location, Phase: Where are you right now in your simulator (airport, in flight between...)? What flight phase is on?

  • Intention: What did you want to achieve?

  • Steps: What did you do to try getting there, at least up to the step that failed?

  • Expected Result: What had you expected to happen at the failed step?

  • Actual Result: What did instead happen?

• Additional uploads, e.g.

  • Screenshots of windows or messages in X-Plane, [Shift-Space] produces screenshots written into the <X-Plane>/Output folder.

  • Crash dumps in case of CtD events

    • Windows writes them to Output/crash_reports in form of .rpt or .dmp files. These files are not overwritten, so they are available historically.

    • Mac: When X-Plane crashes on a Mac then Mac OS pops up a question saying "X-Plane ... quit unexpectedly" offering three buttons. Please click the Report... button. A window with crash details opens. 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: