Skip to content

Potential conflicts found—what now?

How to read the overrides and potential conflicts in a Simstaller VFS Report and decide whether to ignore them, report them to the developer, or uninstall the add-on.

Updated View as Markdown
For humans
SupportSimstallerHelp and troubleshooting

This article covers the following platforms

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

Not every file override in a Simstaller VFS Report is a problem. As explained in How the MSFS virtual file system works, overrides are the foundation of how MSFS loads add-ons — mods like Flow could not exist without them.

Overrides matter when you notice an issue in your sim: fonts that look wrong, avionics acting up, lighting or other visual effects that seem off. When that happens, the report shows which add-ons to consider disabling while you look for the cause.

Overrides with a warning icon

A warning sign and message mark file overrides that have the potential to affect your entire simulator. These are grouped into common issue categories. You can respond in a few ways:

  1. Ignore it. Some overrides are correct and expected. An add-on may need to override core files to add functionality or change sim behavior. For example, Flow is a menu utility, so it replaces existing menu UI elements — it shows up as a “conflict,” but it is one you expect.
  2. Tell the developer. Create and export a report and send it to them. Developers are often unaware of how their files affect the simulator as a whole, and a report could lead to a fix if there is a real issue.
  3. Uninstall it. If the marked files are causing problems, remove the offending package from your simulator.

Overrides without a warning icon

Some file overrides appear in the Overview section without a warning notice. These are informational, and the package likely isn’t causing issues.

Navigation

Type to search…

↑↓ navigate↵ selectEsc close