Hello Support team, @FlyingRaccoon
I’m reaching out regarding an issue I’m facing during the Marketplace ingestion process for my OH6A/500C helicopter addon for MSFS 2024.
The package has been updated to include Career Mode compatibility, and all checks within the Career Compatibility Tool and SDK dev mode panels show green status where required. I’ve validated multiple presets (Flightseeing, Passenger Transport, Cargo Hook Rotorcraft, and Agricultural Spray Rotorcraft), and the tool confirms everything is properly configured.
However, when uploading the package to the Marketplace, the ingestion process flags an “error” on the content browser status, preventing the addon from being validated and taken for further test.
I’ve been in touch with the Marketplace Team (via Steve Schulte, Experis). They confirmed that:
-
The file uploads successfully without visible errors.
-
The issue seems related to internal Career Mode validation, which is currently affecting multiple items.
-
The team has escalated this to Asobo for further review.
At this stage, I’ve been advised to contact Developer Support for assistance and to have someone to examine my upload logs here.
Could someone from the DevSupport team please look into this issue and clarify:
-
What exactly causes the ingestion system to reject an addon marked as “career compatible”?
-
What steps I can take to ensure the package correctly passes ingestion and gets the “Career Compatible” label on the Marketplace?
I’m happy to provide screenshots, tool outputs etc… if needed.
Thank you for your time and help!
Best regards,
Taog
Which build did you use to check that your aircraft was satisfying all career constraints?
Was it SU3 or the latest SU4 beta build?
Best regards,
Eric / Asobo
Hello Eric,
It was the public build SU3 that I used.
Also, I was told by Steve from the MP team, that you would be able to pull some logs from the ingestion platform to see where the issue lies. Is that even a thing ? 
Thank you for your precious help
I have access to logs indeed - I am looking at them right now to first check if the issue comes from the PackageAnalyzer or from the package itself.
To summarise what I see:
- H500C
- Not compatible with TORROT
- Not compatible with COFROT
- Lots of issues reported but I’ll check what the in-sim analyzer says before to getting back to this.
- H500C Cargo
- H500C Floats
- Not compatible with FEFPLN
- Not compatible with TORPLN
- Not compatible with FIFPLN
- Not compatible with SARPLN
- This is to be expected since the PLN activities are for planes, hot helicopters
- H500C Spray
- OH6A
- Not compatible with FEFPLN
- Not compatible with TORPLN
- Not compatible with FIFPLN
- Not compatible with SARPLN
- This is to be expected since the PLN activities are for planes, hot helicopters
- OH6A High Skids
- Not compatible with FEFPLN
- Not compatible with TORPLN
- Not compatible with FIFPLN
- Not compatible with SARPLN
- This is to be expected since the PLN activities are for planes, hot helicopters
I am surprised that the in-sim analyzer did not warn you about these issues - I am launching an SU3 dev build right now to double check why that is.
Best regards,
Eric / Asobo
Ah! that’s what I suspected, so it was because I left the plane activities tags in!
I’ll wait for your input from the dev build, but I guess I know where to look
OK so running the internal PackageAnalyzer (only in dev builds) :
In principle, you should have had the same results with the “Career Compatibility” tab of the SimObjects Editor - isn’t it the case?
NOTE: we have made changes to this UI in SU4 so that it is clearer which activities are targeted and passed/failed.
Best regards,
Eric / Asobo
Hi @EPellissier ,
Wouldn’t be easier if the console could be filtered to show only the things we are tagging? for example, if I want to enable career for VIP and PAX only.. is not use to see all this RED tags not passing, since I am aiming only for 2 careers roles.
Ideally some way to limit this output (a filter of some sort, show only configured activities) this way, it will show only the activities configured and Green / Red if they passed.
I believe most developers having problems during ingestion is because is very hard to understand:
A) What the product has been configured to do.
B) What is the Market Place rejecting.
C) What they have done wrong.
The suggestion above will help with A & C, and help to deduct B, we need some more feedback from the marketplace when it reject to fully understand B.
when we see all these RED in the console, is so daunting we are lost, specially because we might be thinking, well, I only want PAX.. I can ignore all these red stuff.. when in reality we left a tag behind..but we do not know..
Best,
Raul
That’s what I meant in the “NOTE” in my previous post 
. I’ll try to make a screenshot of what it looks like now.
We will work on better feedback from the Marketplace ingestion pipeline for SU5 - however in all cases I have been reported up to now, the in-sim Career Compatibility tab already provided the same information.
That should never be the case if you are targeting a specific activity.
All that being said, we know “easy to read” feedback and missing and are working towards improving this (both in sim and from the ingestion pipeline).
Best regards,
Eric / Asobo
Hey there Eric,
Here is what I see on my side, even with the PLN tags still on (which I will fix now):
For H500C:
For 500C cargo:
For 500C Spray:
So quite different from what you have above…
I will delete the tags now and submit a new version
I’ll let you know when it’s there.
Did you make any change on your end since you last submitted?
If not then there must be an unspotted issue in the analyzer that is integrated in the SimObject Editor - would you mind sharing a stripped down version of your project sources, maybe with only one preset (say H500C since it seems to fail on my end but not on yours)?
Best regards,
Eric / Asobo
This is what the current version of the tool looks like:
When you first run the analysis both “Targeted” and “Non Targeted” lists are collapsed (which I think is wrong, the first one should always be expanded), which allows you to not even see the red lines from non targeted activities.
Best regards,
Eric / Asobo
So the screenshots I shared above are from the version I submitted,
I am now building a new package without the PLN tags and uploading it to the MP portal.
If really this doesn’t go thorugh I think I will definetely share the sources with you so we can have a look
I keep you posted!
Yes this is way better.. will help us a lot, thanks for listening an sharing.
R.
I agree with Raul, this is so much better @EPellissier 
Hello @EPellissier ,
Seems like we’re still at the same page with the ingestion, I get the error symbol :
As I said above, I removed the tags. Also I checked the compatibility before uploading and everything was green where should it should have been.
What would you suggest?
Please let me know,
Cheers
One thing that is flagged by the analyzer in your latest ingestion regarding TORROT and COFROT for the H500C preset:
- Passengers Number does not match requirement : expected >= 1. Got 0. Looking in navigation_graph_passenger.cfg for tags : SIT (0)
- Check this for more information: Commercial Flights And Passengers
For TORROT only:
- RTC_TOUR_EXTERIOR_WAIT_PAX should match SIT tag in navigation_graph_passenger.cfg. Expected 0, got 3
- RTC_TOUR_EXTERIOR_START_PAX should match SIT tag in navigation_graph_passenger.cfg. Expected 0, got 3
- Start node 17 is outside of graph SimObjects\Airplanes\oh6a\presets\taog\500c\navigation_graph\navigation_graph_passenger.cfg
- Start node 18 is outside of graph SimObjects\Airplanes\oh6a\presets\taog\500c\navigation_graph\navigation_graph_passenger.cfg
- Found 0 nodes with name ‘’, cannot resolve graph edge EDGE.6 in SimObjects\Airplanes\oh6a\presets\taog\500c\navigation_graph\navigation_graph_passenger.cfg
- No path defined from RTC_TOUR_EXTERIOR_WAIT_PAX to RTC_TOUR_EXTERIOR_START_PAX for node(s) 3,5 in navigation_graph_passenger.cfg
- Check this for more information: Flightseeing / First Flight
Hopefully fixing this will do the trick, although there are other alerts that I think are false positives - I am double checking them.
Best regards,
Eric / Asobo
Thank you so much Eric, I’ll try all of this!
Is there anything coming out as wrong for spray and cargo?
No issues with Spray and Cargo.
We have understood one of the reasons why you are not seeing issues on your end while the analyzer rejects your package during ingestion: in your “navigation_graph_passenger.cfg” for the 500C preset, you are referring to interactive objects found in the H125 package (SEAT_H125_PAX_1/2/3).
The thing is, the analyzer only mounts base packages in its VFS when proceeding with its analysis, and the H125 package is not one of them - hence it does not find those objects. The real solution would be to declare such dependencies in your package but:
- The interface that allows to do so in the Package Inspector is not available yet (I could explain how to do it in XML though, but it wouldn’t matter much right now, see below)
- The ingestion pipeline needs changes to mount those packages referenced as dependencies - we are discussing internally when that could be done.
What we will do to unblock your ingestion is to mount the H125 package during the analysis, but the real fix will be for us to properly handle such dependencies through the whole pipeline (and for developers to properly declare these dependencies 
). I hope we can do this for SU5.
Important note: because of this dependency, your aircraft won’t work if the player decides to disable the H125 package, which I believe is not a good thing.
Awesome, thank you so much for the explanation Eric,
I actually realized that yesterday, and removed mentions of the H125 in my latest package.
I will re-upload the latest latest version now and let you know if there is any issue again
I see that your latest ingestion failed:
For TORROT:
- Start node 16 is outside of graph SimObjects\Airplanes\oh6a\presets\taog\500c\navigation_graph\navigation_graph_passenger.cfg
- Start node 17 is outside of graph SimObjects\Airplanes\oh6a\presets\taog\500c\navigation_graph\navigation_graph_passenger.cfg
- Start node 18 is outside of graph SimObjects\Airplanes\oh6a\presets\taog\500c\navigation_graph\navigation_graph_passenger.cfg
- No path defined from RTC_TOUR_EXTERIOR_WAIT_PAX to RTC_TOUR_EXTERIOR_START_PAX for node(s) 3,5 in navigation_graph_passenger.cfg
For COFROT:
- No path defined from RTC_ROTORCRAFT_PASSENGER_ENTRANCE to RTC_ROTORCRAFT_PLANE_ENTRANCE for node(s) 12,13,14 in navigation_graph_passenger.cfg
Best regards,
Eric / Asobo
