A300 no longer visible since SU3. Unsolicited installation of the compatible version via iniManager

[AlexEDLE]

We're apparently at a point where the A300 has eliminated itself from the sim.
Since SU3, the iniManager has been behaving strangely, apparently installing the Compatible version in parallel, and the result is that neither the Compatible nor the Premium version are visible in the sim anymore.
I can't say if this is a SU3, iniManager, or A300 issue, but now the thing is completely gone.
If you uninstall the Compatible version, the Premium version also disappears.
Anyone have any ideas?

[Eddie]

Hello,

Can you please doublecheck if the in-sim community folder path is still the same one iniManager uses? You can do that via the Marketplace - My Library then clicking the smaller cogwheel in the top right (next to the search bar). 
Also, for clarity, you mention uninstalling the compatible version makes the premium one disappear but you also say installing compat version in parallel will make both versions not show up. Not sure what to make of that 😅

But as mentioned, doublecheck the file-path and let me know. 
Thank you 🙂

[HHHH]

be sure to "Enable" it in "My Library" at MSFS24 marketplace.

[AlexEDLE]

If i install and enable (enabled by default) these modules (2024 premium variant!) via the inimanager, the a300 is disappearing from the sim:

(Dont understand either why the sim is showing the 2024 premium as 2020)

I double checked the folders, everything is fine. I also noticed that the compatible version is shown in inimanager as installed, though its not.

Switching in inimanager between installed and not installed always shows the compatible version.

The folder structure in the community folder shows that only the premium variant is installed.

Since the new installation of the liveries via the inimanager i also noticed, that the folder-names have been renamed since my previous installation. The structure is now clearer, but it seems there is something not right.

 

Edited Sunday at 06:28 AM by AlexEDLE

[Eddie]

Hello,

We'll most likely need some more information as to why this is happening. Please reach out to direct support and they can help you a little bit closer. 

Apologies for the inconvenience.