I am having some problems in MSFS2024 with our Eurofighter Typhoon, and I am a little lost.
The retail package seems now “disabled” by default on MSFS2024 (both SU5.1 and SU6 Beta).
The retail package is an MSFS2020 package built with the latest MSFS2020 SDK.
All of our planes are made in this way - but all others do not haver this problem.
I can enable it in the library, and the package works fine… but next time I start the sim is disabled again.
Moreover, I have been working on a new update… and putting the package in the Community folder like we always did does not work, and the package does not show.
This makes me think that the Typhoon package is - for some reason - flagged as “bad” package by MSFS2024, and disabled by default (or ignored in the Community folder) - but I see no errors at all.
Help?
Hello @Scimmia1974
What repository are you selecting when booting the sim? Your draft repository?
Can you please take a screenshot of the Packages DevMode tool showing the line about your package?
Regards,
Sylvain
Hello @FlyingRaccoon - thanks for getting back to me so quickly.
As for the repository, I had it set to Draft, but I also tried the other options (retail and pre-release) and it does not seem to make any difference: the stream version is always disables (and if I enable it, it works… but next time I start the sim is back to disabled), and the version in the community folder is ignored by the sim.
I have also tried both SU5.1 and SU6 Beta - no difference.
For example, in this moment I have the following packages in the Community folder of MSFS2024.
F-16 (new product in development)
TA-4J (new product in development)
EFA (Typhoon update)
All of them are 2020 packages.
The F-16 and the TA-4J show and are available for selection.
The Eurofighter Typhoon is not there.
These are the messages I get from the console, which I think mean the streamed and the local copy are both registered.
Ok, I think I have found the problem - the Typhoon was disabled inside the “Community Content” group - I did not remember it existed (and frankly I do not recollect I have never disabled it), but it seems to work now.
Apologies for the inconvenience, but I panicked as we have a new update almost ready.
I was referring to this tool: The Packages Window
It might help you the next time you face a similar problem.
Regards,
Sylvain
