Couldn't load loadouts

[shdwp]

I've tried loading loadouts using both:

group.load_task_default_loadout(dcs.task.CAS.name)

and

group.load_loadout("the name as it is in mission editor loadouts page")

but when I load the mission aircraft is there but with nothing under its wings.

The group itself is generated by Mission.flight_group like this:

return self.m.flight_group( country=side, name=name, aircraft_type=unit, airport=airport, position=at, altitude=WARM_START_ALTITUDE, speed=WARM_START_AIRSPEED, maintask=None, start_type=starttype, group_size=count)

group.task is set later along the callstack.

Could you share an example that works? Or is this a bug?

[rp-]

That might be a bug, do you have installed DCS in the default location?
C:\Program Files\Eagle Dynamics\DCS World

or on another drive or folder?

[rp-]

or what unit type is it?

[shdwp]

I have both SA at standard and steam in PFx86/Steam.

For the type I've tried A10C with CAS and F15C with FighterSweep.

I think I'll debug this later this evening after I come back home and provide a little more information (I've thought it's a simple wrong usage issue).

[shdwp]

Wait, does it require dcs to be installed? I'm using a separate computer to generate the missions (without DCS), so that would explain it all. How does it account for non-standard path installations then?

[rp-]

I don't think it is your fault, but it should have worked for the A10C.

The code for loading the unit payload is a bit static, if you look at unittype.py:58 these are the folders that are currently looked for unit payload definitions.

The code should get the DCS install folder from the registry or some other reliable way and it should also load all CoreMods/aircraft folders.

I just tested it with SU-25 and AH-64A and it worked.

apache = m.flight_group_from_airport(usa, "AirCav", dcs.helicopters.AH_64A, kobuleti, group_size=2)
apache.load_loadout("8xAGM-114, 38xHYDRA-70")
apache.add_runway_waypoint(kobuleti)

[rp-]

Wait, does it require dcs to be installed? I'm using a separate computer to generate the missions (without DCS), so that would explain it all. How does it account for non-standard path installations then?

yes for payloads to work it needs a DCS install, or you copy all the payload definitions in a directory and add them to the load path in unittype.py.

[shdwp]

Yeah, I've tested that on the machine with DCS installed and it works just fine. Thanks a bunch.