I’ve changed my gamertag in the past, but most normal names are already taken and I don’t want to be called NickJ(random set of numbers) in career.
Since it has been said the Career mode will be heavily “moderated” as to what 3rd party planes and airports will be available in it, my guess is only from the Market place, has it been said anywhere how it will work? Will only the Marketplace bought addons be allowed or does it “just” need to be on marketplace and it will recognize them even if they were bought from the publisher directly? If so, the entire mode is useless for me, shame. I’m not buying any addon on marketplace any time soon, if it takes MS/Asobo several weeks to implement updates sent to them by developers…
I have plenty I’ve already bought so I’m going on hiatus from 3rd party new purchases for a while, but it makes another argument for PD as surely some of those aircraft CAN be integrated into career mode. Almost every all new PD aircraft looks like it has a specific job it’s capable of doing. 747 tanker and transport, heavy rescue heli, CH47, business class, saab, the 787… I have the Miltech CH47 but who knows if that will ever be integrated into a career. And who knows long term if those native aircraft can be both in a career and modded accordingly. Big gamble to pass on them.
This subject was discussed extensively above. In the SDK Q&A, it was said it will be Marketplace only, but then they discussed they’re going to look at allowing planes that are on sale in the Marketplace might be capable of being used if they’re in the Community directory, but they’ll need some method of verifying that all the required files and information is in place. Or perhaps some other method, i.e. maybe they own the required files and if it finds the same GUID, it’ll use those for that plane, something along those lines (this detail is conjecture on my part on how to solve the problem).
The 2024 SDK shows what is required to ensure that aircraft and airports work correctly with the various careers that are available. See here.
IMPORTANT! The document is still a work-in-progress and as such may not contain all the information about the SDK contents or how to use tools described.
I hope the absence of helicopters for aerial firefighting is only a temporary thing and they get added later. They play such an important role in real life, it seems a strange choice to not include them, especially now underslung loads are properly modelled.
I wonder if the aircrane has some functionality. They are modeling slung heli loads and ag spraying with the smaller helis so it may be there just not shown?
The aircrane and CH47 are definitely capable of it.
Most likely that’s the case. As aircraft are modular and as the Skycrane features firefighting equipment I think it’s mainly (if at all) bambi buckets missing.
(MSFS24 promo screenshot)
Maybe there also is currently some trouble with turbulence from fires in combination with helicopters - at least that would be a show stopper in that particular case.
The SDK documentation currently shows no career path configuration for aerial fire fighting with rotorcraft, only two for fixed wing aircraft.
However, maybe it’s also just a configuration thing and aerial firefighting missions are handled as “cargo” missions as these don’t require an individual cabin or different equipment - it’s just another type of sling load in the end which requires different skills.
What I don’t quite understand currently is the design choice for helicopters on career mode to require a copilot and to exclude helicopters with floats from being able to transport cargo.
That means especially the Kaman K-Max is excluded from cargo ops but also stuff like that won’t be a thing:
“The Rotorcraft cannot be flagged as Military”
Hmm, this seems rather strict and unnecessary. Though I imagine a workaround is having separate models for flagging for various careers, similar to how, for instance, the L-19 has Civilian, Float, and Tundra models in the same package. Each could have their own definitions.
It seems like excluding vehicles flagged as “Military” from use is a little pedantic, however, since the military very often assists with civilian issues, such as flooding and disaster relief.
And, yeah, the copilot thing is interesting… What if I want to do the copilot duties? Or do copilot duties have to be AI only?
Lot’s of reading to do tonight ![]()
I will call mine El Fungote
“military” in general is not excluded - for remote cargo operation type missions it’s required instead
might be they plan to have specific military rotorcraft missions in mind at a later point as the general helicopter cargo missions also only cover sling load cargo, not internal cargo (looking at the CH-47D there might be a candidate to transport equipment or goods also internally
)
Yeah, but, why exclude a tag like “Military” from from a “Fire Fighting” career/mission? That doesn’t make any sense to me in this type of case if you know what I mean. Sure, exclude “fixed wing” aircraft from “rotorcraft” missions, but “military” doesn’t mean anything in most situations. For instance, an L-19 might be a “Military” tagged plane, but that shouldn’t exclude it from “Bush Plane” missions.
I know what you mean but on other hand that’s something you could work around by adding a simple variant which has no military tag ![]()
The other things like the must have copilot or that a helicopter must not have floats cannot be worked around - the floats are defined in the flight model as one of the contact point types, so changing these will draw the floats inop.
The copilot is defined by a model node on the left seat, so to cheat that check you’d have still to put the copilot somewhere to spooky clip through the fuselage in worst case… that’s also not an option I’m afraid ![]()
I see what you’re saying. But I also disagree to an extent. Military should be military aircraft. Be it an f18, c17 or ah64. I don’t want to see a General Av aircraft or 737 incorrectly tagged.
And Search and Rescue, lots of military air forces perform civilian SAR. It seems like someone didn’t do their research properly!
Coming back to this - while there is currently no specific aerial firefighting career path for rotorcraft I stumbled over this section in the SDK which specifically mentions there is a preset for “Bambi Bucket” in place for the career:
Also notice the other things like the fuel tester ![]()
Well there you go, they just didn’t show firefighting with a heli yet. There is a lot to cover…
Guess they’re taking a page from the Comanche walkaround.
At least way more features are planned - it might be these presets are in place but still the models and some core functionalities are not finished or not even started.
Prime example for this is one of the interactive points on the Boeing 747-8i which actually was intended to be an ASU (Air Start Unit) connection. Just like the emergency exit doors that however was not actively used on MSFS2020 ![]()
And there’s a fuel connection point in many 2020 aircraft… did that ever work with the ground vehicles that a hose would hook to the fuel connection point in 2020? I thought I once saw a video somebody did showing it working, but, I never spent the time to figure out how…



