Mission Editor ----- Loadout Editor weirdness - please explain?

[SDsc0rch]

i organize the missions i build in to folders

 

my custom loadouts don't always appear

 

sometimes i see all of my custom loadouts...

 

 

 

 

but sometimes i see this...

 

 

 

 

as you can imagine this can be frustrating to me

 

can someone explain this to me?

 

where should my "loadout files" be stored? (are they even a thing? how can i find them??)

 

or should i use a better directory structure? (parent-child?)

 

just help me work "with" the system - help me understand

 

thx

Edited March 27, 2017 by SDsc0rch

[feefifofum]

I can't see what airframe you're using because the pictures won't show up, but:

 

If it happens to be one of the newer, oft updated airframes I've found that prepatch custom loadouts tend to break. The M-2000C has been the main culprit on my end but I would expect to see the same from the F5, Viggen, etc.

 

Any time there is a patch that affects the ordnance of these aircraft it's a good idea to rebuild any custom loadouts you use to jive with the new weapon tables. This is especially prevalent in missions with limited ordnance...anything that's been updated will appear as a blank space in the list and will not be accessible in the resource editor.

[Rudel_chw]

i organize the missions i build in to folders

my custom loadouts don't always appear

sometimes i see all of my custom loadouts...

 

...

 

but sometimes i see this...

 

...

 

as you can imagine this can be frustrating to me

 

can someone explain this to me?

 

Hello,

 

What happens is that the loadouts are classified in DCS by "role" ... so if for example you create a custom loadout for an A-10C that is set to a Role of "CAS", it will be saved for that Role only.

 

Thus, if you then have a second A-10C unit but on the mission you set its role to "Ground Attack", the custom loadout that you created will not show on the list.

 

where should my "loadout files" be stored? (are they even a thing? how can i find them??)

 

The loadouts are stored in two places:

 

1) Within the program files, on the path \DCS World\MissionEditor\data\scripts\UnitPayloads ... there is a .lua file for each aircraft, that contains its default loadouts.

 

2) Within your Saved games, on the path \Saved Games\DCS World\MissionEditor\UnitPayloads ... there is a .lua file for every aircraft that you have created custom payloads for.

 

What you see on the mission editor is the combination of these two files, but classified by the Role of the specific aircraft.

 

or should i use a better directory structure? (parent-child?)

 

How you store your missions have nothing to do with the loadouts at all.

 

just help me work "with" the system - help me understand

 

This is an old post, so the file paths are no longer valid, but it correctly describes how the payloads are stored on the lua files ... its a bit complicated but interesting reading nonetheless:

 

https://forums.eagle.ru/showthread.php?t=79499

 

Best regards.

[SDsc0rch]

ohhhhhhh man

 

i'm reading that other thread - thank you for pointing me in the right direction

 

this kinda sucks - i don't think of loadouts as belonging to a task or mission area, i think of loadouts assigned to AIRCRAFT (sigh)

 

nevertheless - thank you

[Rudel_chw]

this kinda sucks - i don't think of loadouts as belonging to a task or mission area, i think of loadouts assigned to AIRCRAFT (sigh)

 

 

However, you can assign to your aircraft the Task "Nothing", and this will put together all the loadouts available on one large list.

 

 

I actually find this useful, since it simplifies the listing ... if I select the Task "antishipping" it will only shows those loadouts that make sense for the role, a much shorter list.

 

 

Regards.