Support

Discord community

All MFSAppsControl support happens on Discord, in the dedicated #mfsappscontrol channel (remember to pick up the role when you arrive).

That channel has a ready-to-use template for reporting a bug or suggesting a feature.

Join the Discord

Reporting a problem

So that a problem can be diagnosed, please include:

• your Windows and MFSAppsControl versions (shown in Options → About);
• the simulator version (2024 or 2020);
• the steps to reproduce the problem;
• the expected behavior and the observed behavior.

Attaching a diagnostic report

Logs save an enormous amount of analysis time.

The procedure to follow:

1. In Options → Debugging, set the Log level to Debug (or Trace if support asks you to).
2. Reproduce the problem — repeat exactly the steps that go wrong.
3. Still in Debugging, click Export logs and save the .zip file it offers.
4. Attach that .zip to your message on Discord.
5. Once you are done, set the level back to Error.

What is in the export?

The .zip bundles the generated logs and your configuration file.
Nothing else is collected, and nothing is sent automatically: you alone decide to share it.

Suggesting a feature

Suggestions are welcome on Discord.
Describe the need by following the template (what you are trying to do before or during a flight) rather than the technical solution. I can't promise every idea will be implemented, but they will all be read and considered.