I’ve run into an issue during Marketplace ingestion that is stopping a package from being uploaded. I know this isn’t the SDK teams field, but the Marketplace team suggested I disable career mode to avoid the checks associated with it. Looking through the SDK I can’t seem to find any one option that would disable career mode checks during ingestion.
Is there a way to do this?
Hello @kcgb
Can you tell us which aircraft we are talking about here?
So it’s not supposed to be career compatible and you haven’t made any changes that would be career related?
Based on these instructions, do you have any of your aircraft.cfg [FLTSIM] section specifying a targeted_specializations parameter?
Regards,
Sylvain
It’s actually just an aircraft mod like the DA62 mod sample, adding attachments and a new preset, but for the FA18.
The preset aircraft.cfg only contains
[fltsim.0]
title = "FA-18E Payloads" ; Variation name
ui_manufacturer = "@asobo-aircraft-fa18e,TT:AIRCRAFT.UI_MANUFACTURER"
ui_type = "@asobo-aircraft-fa18e,TT:AIRCRAFT.UI_MODEL"
ui_variation = "Payloads"
isUserSelectable = 1
capacity = 1
This does not look like a career compatibility issue.
The ingestion fail is more likely caused by the package being considered incomplete.
Can you try editing your package xml file in PackageDefinitions and add a Dependencies section with the format described here: Package Tool XML Properties
<Dependencies>
<Dependency Version "0.1.0">
<Name>asobo-aircraft-fa18e</Name>
</Dependency>
</Dependencies>
This is not editable through the Project Editor yet, the xml has to be edited manually.
Rebuild and export your package with that modification, submit it again for ingestion, and let us know if this solves your issue.
Regards,
Sylvain
There is a small issue with the documentation there. You and the SDK are missing an = sign
<Dependencies>
<Dependency Version="0.1.0">
<Name>asobo-aircraft-fa18e</Name>
</Dependency>
</Dependencies>
That did add
"dependencies": [
{
"name": "asobo-aircraft-fa18e",
"package_version": "0.1.0"
}
],
to the manifest.json. But it seems not to have fixed the ingestion issue.
Ok, we’ll keep investigating and will let you know when we have new guidelines.
Our apologies for the inconvenience, and thank you for the feedback.
Regards,
Sylvain
Hello @kcgb
Quick update on this: this is a dependency issue but ingesting your package requires some modifications on our side first. This is ongoing.
I’ll update this topic when the tools are ready for your package to be ingested again.
Regards,
Sylvain
Hello @kcgb
The issue is resolved on our side, please try a new ingestion and let us know if the issue is still present or not.
Regards,
Sylvain
Fantastic, Ingestion completed and I can see it in the content browser, It’s also says its mounted, but it isn’t in the menu. There are also no errors in the console.
Thanks for the quick work.
@FlyingRaccoon I see this got changed to fixed, ingestion happened did but it’s still not actually showing up. there should be a new preset but it isn’t appearing with the streamed version
Hello @kcgb
There is another issue, this time on the way protected cfg files are merged.
This will also require a fix on the sim exe. It’s being worked on, and we will let you know when this is available in SU4 beta.
Regards,
Sylvain
Thanks for the update, guess I’ve been a guinea pig for this kind of mod 
. Good to hear it is being sorted out. I’m assuming it’s to do with the merging of Non-protected files like the stock FA18 ones and the protected ones in the mod.
Yes exactly, and you seem to be the first one to rely on this feature. 
Hello @kcgb,
We made a fix in the latest SU4 flighting 1.6.22.0 that should fix the issue.
Can you test and confirm ?
Regards,
Boris
Tested on PC and Xbox, both are working now. Thanks!
