I’m getting an error when sending my Garmin G5 & Aera pack; the error seems to be in the a320neo (v2) aircraft.cfg file inside the presets folder. I’ve tried reconfiguring it in every way possible, but I’m still getting the error. Rial from Teams advised me to post here to ask for help. If I upload the file without the aircraft.cfg, no error appears, but the pack needs the aircraft.cfg to work.
Hello @RMS
During ingestion process, only the base sim content is mounted by default so it will fail because of unresolved dependencies.
We need to add the A320 neo V2 to handled dependencies on our side.
I’ll escalate the issue and will let you know when you can try ingestion again.
Regards,
Sylvain
2 Likes
Hi
I’m having the same problem with the 737 MAX 8 as well; I tested it today and got an error on the MCP again
Hello @RMS
Can you then list all the dependencies you have?
Ideally, that’s something you want to indicate in the package metadata, through the package xml file Dependencies section. Package Tool XML Properties
Regards,
Sylvain
Hello FlyingRaccoon
Can I only add one dependency per project? I tried adding the 737 and A320 dependencies to my MOD, but it only generates one of the two in the manifest file. Even so, I tested it to see if the error in the MCP would persist, and now the project is loading indefinitely.
Regards,
Renan
Hello FlyingRaccoon
After a few attempts, it seems to have worked on the PC, but on the Xbox it’s stuck in an infinite loop on the MCP
1 Like
Hello @RMS
Is it okay now?
Both Xbox and PC versions have the “Success” status for me now.
You should be able to define multiple. I will double check that.
Regards,
Sylvain
I couldn’t replicate the issue
<Dependencies>
<Dependency Version="0.1.0">
<Name>toto</Name>
</Dependency>
<Dependency Version="0.1.0">
<Name>tata</Name>
</Dependency>
</Dependencies>
gave me this in the manifest:
"dependencies": [
{
"name": "toto",
"package_version": "0.1.0"
},
{
"name": "tata",
"package_version": "0.1.0"
}
],
Maybe you provided multiple names in a single Dependency element?
Regards,
Sylvain
1 Like
Hello FlyingRaccoon
It worked only for the A320, but it still showing an error in the MCP for other aircraft’s, as shown in the photo. Below are the dependencies I compiled that appeared in the manifest.json file
{
"dependencies": [
{
"name": "asobo-aircraft-c152",
"package_version": "0.1.0"
},
{
"name": "asobo-aircraft-c152-aerobat",
"package_version": "0.1.0"
},
{
"name": "asobo-aircraft-c172sp-classic",
"package_version": "0.1.0"
},
{
"name": "asobo-aircraft-da40-tdi",
"package_version": "0.1.0"
},
{
"name": "asobo-aircraft-dr400",
"package_version": "0.1.0"
},
{
"name": "asobo-aircraft-dv20",
"package_version": "0.1.0"
},
{
"name": "asobo-aircraft-l39-reno",
"package_version": "0.1.0"
},
{
"name": "asobo-aircraft-savage-cub",
"package_version": "0.1.0"
},
{
"name": "microsoft-aircraft-cap4",
"package_version": "0.1.0"
},
{
"name": "microsoft-aircraft-c185f-skywagon",
"package_version": "0.1.0"
},
{
"name": "microsoft-aircraft-pa28-236-dakota",
"package_version": "0.1.0"
},
{
"name": "microsoft-aircraft-r66",
"package_version": "0.1.0"
},
{
"name": "microsoft-aircraft-a321",
"package_version": "0.1.0"
},
{
"name": "tata",
"package_version": "0.1.0"
},
{
"name": "microsoft-aircraft-a330",
"package_version": "0.1.0"
},
{
"name": "microsoft-aircraft-bell407",
"package_version": "0.1.0"
},
{
"name": "microsoft-aircraft-a320neo",
"package_version": "0.1.0"
},
{
"name": "asobo-aircraft-b737max",
"package_version": "0.1.0"
},
{
"name": "microsoft-aircraft-a310-300",
"package_version": "0.1.0"
}
],
Regards,
Renan
Dependencies in the manifest.json are not yet used to mount appropriate content at ingestion.
Hopefully this will be the case soon, but for now this is a manual process.
I’ll forward the full list to our Marketplace team so they can make the required changes and will let you know when the package can be reingested again.
Regards,
Sylvain
Hello @RMS
FYI, you left the “tata” package from my example in your dependency list. 
Regards,
Sylvain
Oh, my mistake. Thank you so much for letting me know. I fixed the manifest.json file, but I’m still getting an error in MCP because of the aircraft.cfg files. However, when I uploaded it with just the A320, it worked fine. I think it’s because of the dependency you added to MCP for a320.
As I said, the dependencies need to be manually added by our Marketplace team for now so I’m waiting for their confirmation it’s done and I’ll tell you when to reingest.
Regards,
Sylvain
1 Like
The necessary changes were made on our side, please try reingesting your package and let us know if it went as expected.
Regards,
Sylvain
hello @FlyingRaccoon Unfortunately, I’m still getting an error in MCP :(. Could you share the log with me so I can fix whatever’s wrong with the pack?
Hello @RMS
The logs are not designed to be read by the end user for now.
Even for me, they’re a bit cryptic.
We plan to expose public logs in MCP for SU5 so that should improve the situation.
In the meantime, I’m reviewing with the team what went wrong in your latest ingestion.
Regards,
Sylvain
2 Likes
After SU5, I’m still getting an error when uploading the MOD. From what I’ve tested, the error keeps occurring with the a320neo aircraft.cfg. I sent the pack with all the other presets and it worked, but when I send it with the A320neo, the error keeps occurring. For this last upload, I sent it with only the A320neo to see if the MCP would indicate the error, but when I click, nothing appears.
Hello @RMS
We have the same issue as described here: MCP error uploading project Microsoft Team doesn't have answers
We are having issues with the ingestion process handling of dependencies at the moment.
The ingestion pipeline is being worked on as we speak to resolve those issues.
No ETA for a fix but I am tracking the problem so as soon as the necessary modifications are made on our side, I will let you know.
Regards,
Sylvain
2 Likes
Do you have any news about the modifications on MCP?
Hello @RMS
The dependencies that are filled in your package manifest.json were manually added to our ingestion pipeline.
Can you please to try to reingest your package and let us know if it succeeded?
Regards,
Sylvain