Hi Asobo,
I have a project that for almost a month has given us issues uploading onto the FS2024 marketplace draft. We were able to upload and test it on Xbox/PC via stream for several months since late 2025, but we are unsure what happened after March 11 of this year, as our package at the MCP keeps returning an error.
The product is now ready for launch, but this block is on the way.
The Microsoft team couldn’t find the cause of the error, and they have told me to seek help from you guys.
I would like to share this information via a private route. I don’t wish to disclose the project.
Looking forward for your assistance.
You can send private content as described here:
See section 3) Provide Private Content.
1 Like
There’s not much we can do to help if we don’t even know the name of the package.
Best regards,
Eric / Asobo
Hi @EPellissier
Sorry about it. Here’s the information.
The name of our package is called “bravoairspace-bravo-traffic-wh”.
Hello @playboy
This is the same issue as discussed here:
Error in MCP after sending a file containing aircraft.cfg - [MSFS 2024] Bug Reports / Aircraft - MSFS DevSupport
You have unresolved dependencies in your package, typically attached_objects.cfg with references to asobo content.
Can you please explicit your dependencies by adding them to your package xml file?
Package Tool XML Properties
and provide the list here so that I can review what needs to be changed on our side.
Regards,
Sylvain
Hi Sylvain,
Will this also be required when we attach the chocks? for example? as per SDK instructions? and the way the DA62 did it?
R.
No the issue only occurs with non mandatory content. Standard attachments are in packages flagged as mandatory that will always be mounted during ingestion.
The problem rather occurs when you start creating a preset for other aircraft, or that you use attachments from other aircraft in your own…
Regards,
Sylvain
1 Like
@FlyingRaccoon
Hi,
I uploaded the package again and it went through successfully. I removed all aircraft.cfg and anything .cfg calling for Asobo default elements. At the moment it’s not very important but its needed for updates after its released. Our focus was to force aircraft types to park at cargo spots versus seeing them at jetways. Some variants do not work as passenger jets anymore and wouldn’t mind seeing the few ones parked at hangars, etc.
We are going to constantly update this add-on.
I will update the package xml and get back to you for your help in order to make those changes in the game.
But to be sincere the dependency isn’t in any of our files and I need to learn what to do.
We don’t have any of these structures
toto
tata
We do appreciate your immediate assistance.
These were just examples of how to add dependencies in the xml package file.
You will need to add a <Dependency> entry for each package you depend on.
Regards,
Sylvain
@FlyingRaccoon From what I’ve been streaming, it appears I will need to do this asap.
