Skip to content

Collect logs for support

Reproduce the problem once, then attach the right log files to your ticket.

Updated View as Markdown
For humans
SupportParallel 42General help

This article covers the following platforms

  • MSFS 2024
  • MSFS 2020
  • ATS
  • FSX
  • Prepar3D

Reproduce the problem once, copy the matching log files, and attach them to your support ticket. Each product stores its logs in a different place, so use the section for the product and simulator version involved in your issue.

Reproduce the issue once

  1. Close Microsoft Flight Simulator and the affected Parallel 42 application.
  2. Start the product normally and reproduce the problem one time.
  3. Note the local time and copy the exact message or error number shown.
  4. Close the simulator and the Parallel 42 application before copying any files.
  5. Do not reopen the application until you have copied the current log. Some logs are replaced when the application starts.

Find your product’s logs

ChasePlane logs

Reproduce the problem once, then attach the ChasePlane logs that match what failed.

Read article →

Flow logs

Attach the Flow Manager log, and check FlowShare when the wheel stops responding.

Read article →

Simstaller logs

Attach the Simstaller log, and export a VFS report for an MSFS 2020 package conflict.

Read article →

Include this context

Along with the files, include:

  • Product name and version
  • Simulator version, plus Steam or Microsoft Store
  • The local time when the issue occurred
  • A short list of steps that reproduces the issue
  • The exact on-screen message or error number
  • A screenshot or short video when the problem is visual
  • Any change immediately before the issue, such as an update, reinstall, or new add-on

Then open a Parallel 42 support ticket and attach the relevant files.

Navigation

Type to search…

↑↓ navigate↵ selectEsc close