feat: add simulator property to addons#56
Merged
FoxtrotSierra6829 merged 5 commits intostagingfrom Nov 15, 2025
Merged
Conversation
6 tasks
flogross89
approved these changes
Oct 12, 2025
FoxtrotSierra6829
added a commit
that referenced
this pull request
Nov 15, 2025
* feat: add simulator property to addon * feat: add A32NX to msfs 2024 addons * feat: add A380X and Simbridge to MSFS2024 * revert: msfs 2024 test addons
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary of Changes
Additional context
I initially intended addons to be able to support multiple simulators without needing two entries. This turned out to only be possible with a translation layer due to the need for individual addon keys for installer state handling, as well as the facilitation of the installer chosing which set of paths to use. As in the long term, the configuration of an addon between the two MSFS simulators will diverge either way, I have opted for not creating this translation layer to ease the maintainability of the installer code.
Old versions of the installer (pre flybywiresim/installer#512) are unable to filter by simulator. Having an MSFS 2020 and MSFS 2024 version of an addon will therefore lead to having both versions shown and detected as installed. The new installer version will filter out any addons without the simulator property. A potential course of action to mitigate this issue is to initially release the new config alongside the new installer version without MSFS 2024 addons to allow for a transition.
Discord username (if different from GitHub):
foxtrotsierra