Attempting to re compile our MSFS 2020 Products to allow them to be easier to make compatible later …
(This is simply some minor file renaming to prevent duplicates etc )
The details of this are irrelevant because they no longer show in Sim ( 2020) regardless of alleged “Successful compile” of previously Perfect XML Projects
Can there be some cross talk between 2020 and 2024 SDK Compilers being installed at the same time ( In different locations) ???
To Clarify . . . NO Work is being done under 2024 SDK but when correctly compiling via MSFS 2020 SDK & Tools they no longer display In MSFS 2020 Sim
@FlyingRaccoon Any feedback on this ?
Can you confirm or deny as it is frustrating any further development
Sometimes the compiler (at least in 2020) skips files with minor changes
If you happen to still have the packages and PackageInt folders, remove them and compile again, so you are sure you have a fresh compile
Nahh pretty certain its not that … we are very experience in this and always make sure it skips nothing by doing a clean build …
ALL previous files are deleted as well as the _PackageInt folder…
and NO errors are reported on the compile beit within the project editor or via the supplied fspackagetool.exe
There is no such thing as an “SDK compiler”. The Package Builder is integrated into the sim itself and not in the SDK - but some support files can be provided through the SDK in 2024 (ModelBehaviorDefs, LOD processing presets…). However there’s no “cross-talk” between the two pipelines (unless there is a bug somewhere).
What kind of files renaming are we talking about?
Did you try to compare a working version of your package with a non-working one with tools such as WinMerge?
Maybe the package compiles successfully but has issues at runtime - does the console tell you anything about this?
Please provide a working and a non-working built package if you want us to help.
@EPellissier
Thanks Eric … I am aware how the compiler works thanks … Been using it since day 1
THIS is exactly what I am suggesting …
A Pre compiled project or one that is already in the Marketplace appears in the Sim just fine …
However a project compiled “Today” Using the EXACT SAME file set fails to appear in Sim … There are NO Console errors during the build and this problem occurs with Any Previously working project . Even the content manager shows them as INSTALLED and Yet there are No aircraft in the hangar…
(Note). this is definitely NOT due to any changes made as we have tried with several UNCHANGED Projects with the same result…
I am suggesting that the latest MSFS2024_SDK_Core_Installer_0.11.0 is somehow cross talking with the MSFS2020 SDK in some way preventing the successful compilation of MSFS Product Previously built and distributed without error…
Just to clarify the “renaming files” issue … It is actually irrelevant if files are renamed as the recompiling of the projects is what brought this Bug to Light… It still exists with a completely unchanged and vanilla file set.
There are no errors in project editor or the console and the projects appear as INSTALLED in content manager… they do Not however appear in the hangar or aircraft selector
I understood what you were suggesting but, in principle, the two SDKs and EXEs are totally separate - without more information from you there’s not much we can do to help.
If your aircraft is not seen in-game while the package is mounted you should see errors in the console (when the aircraft is loaded, NOT at build time) - don’t you see anything in the console?
Did you try uninstalling both SDKs then reinstall only the 2020 SDK?
If your assumptions are correct then your package should work again?
Correct … as I have already said there are NO ERRORS in The console …
and please explain How we are supposed to load an aircraft that does not appear in the hangar ???
No we have not tried this yet as we are at a critical stage of development converting our FS2020 Products to comply with 2024 …
Uninstalling these SDK’s would not only be vastly Inconvenient, But would only go to prove our initial suspicions that there is some for of Interference between the two …
hi @EPellissier Antony From BBS here ,
I can confirm 100% that there are no errors logged whatsoever
the only entry regarding this package is to state the package contents have been mounted at load time.
The aircraft do not appear in the hangar or dev tools aircraft selection at all
However using internal tools we have developed using simconnect i can inject all these aircraft into the sim and they render perfectly.
There are zero differences in aircraft configs or any xml files anywhere when compared to a working set from our website installers
Does your aircraft appear in the DevMode Aircraft Selector? If it does, then it may just be grouped in a way you didn’t anticipate in the sim’s aircraft selector/configurator.
What are the values for “icao_model” and “ui_createdby”?
Can you send us the built package for review so that we can help?
Looks like I didn’t read your post carefully enough - you said the aircraft is not visible in the DevMode Aircraft Selector and since the issue is within 2020 it has nothing to do with the 2024 aircraft selector/configurator.
If in 2020 you can see your aircraft neither in the sim’s selector nor in the devmode’s selector, BUT you can spawn it using SimConnect, then it means that the sim considers it is not “UserSelectable” (what we call passive or AI aircraft). Again, seeing the built package would help us checking the issue.
A few more questions:
If you rebuild your package without changing anything in the package sources, does the aircraft appear in-sim?
Do you still have “working” versions of the built package?
If that’s the case, can you send us a working and a non-working version of the package?
1 - with zero changes to package sources from published version
NO - The aircraft Fails to appear in Sim or Dev Selection window
However it DOES Appear in content manager as “not installed”
2 - yes of course… I will ask @SteamedPhoenix4 to send a copy of working / non working projects
Meanwhile is it possible you can attempt a compile of ASOBO “Simple Aircraft” Sample (or similar) and check your own results ?
When comparing the two packages I can see that you removed the “panel” folders of “blackbox-aircraft-BN-Islander-PAX” in the new version.
Unfortunately a user-selectable aircraft needs to have such a folder with a panel.cfg file, otherwise it is ignored by the sim. Since other variants reference the same folders, they are ignored too.
I don’t think this is related to 2024 though, unless I am missing something?
The conclusion of this topic was the biggest plot twist I’ve seen so far
I say this because I’m facing the same problem reported in the initial message, but in reverse and I expected a solution for this in the final messages:
When opening an MSFS 2020 project (previously copied as a backup but with a different name than the original) in the MSFS 2024 SDK, following the steps to update the project package or not, the compilation is never successful, resulting in a fatal crash on the computer.
I would like to better understand the reason for this, because since I can’t work on my projects in the 2024 SDK, I’m still using the 2020 SDK to make my products compatible with MSFS 2024 instead of working on the projects entirely from scratch from the 2024 SDK
