A spelling error, mis-placed semi-colon, any one of a number of typo errors can upset things in those files. You also have to have the "B" nodes, or "R" nodes, or whatever equipment you are attempting to mount, has to have that mount point on the platform itself. For the Loadouts themselves, you "Name" and outline a load-out in the cfg file, and you define it in the eqp file. Kind of like programming and sub-routine procedures. btw - The "DummyBomb" in your example is there as a "fake" so that the plane will come down and at least strafe you. So the cfg file names the load-outs, but each plane's eqp file should start with a "default" load-out, so make certain that set of nodes is at the top of the file. Most of the eqp files we've dealt with will call it "Basic", such as:
; Basic Loadout definition
[Equipment 1]
NodeName=B01
LinkName=Bomb250Kg
StartDate=19380101
EndDate=19431101
Five lines for each entry when including the dates. Notice the Start and End Date lines generally only have to be there for at least the first item of a loadout definition, and that everything about the plane is listed in ALL of the loadouts that are outlined (cfg) and defined (eqp). If there are five "B" nodes on a given plane that you wish to use in a load-out, the empty slots need a NULL listing in the other definitions. When you get to building the "named" loadouts, then you add another line to the equipment listing:
;3x250Kg Bomb Loadout definition
[Equipment 10]
NodeName=B01
LinkName=Bomb250Kg
Loadout=3x250Kg Bomb
StartDate=19431102
EndDate=19451231
There would now be six lines for each entry (including dates), adding the "Loadout=" line. Also, be certain that the headers are listed in proper numerical order. Blank lines are not necessary, and the ";3x250Kg Bomb Loadout definition" line isn't necessary either. Those are there for the human. The game uses the "Loadout=" lines for that. It is good practice (possibly necessary for the game) to keep all Load-outs with the same sequence of "[Equipment XX]" sections, and as mentioned, if not used in a given load-out, use "NULL". Also, don't overlap dates if the loadouts are for spawned assets... This particular plane above is set to "automatically" change its loadout by date. All items in a given loadout definition need to have the same dates, if listed. You can have overlapping dates if the mission builder chooses the loadouts when placing the asset in a mis file and chooses a particular loadout, such as one plane for ASW, another for divebombing, etc...
However, again, you are illustrating the Hurricane, but describing the Martlet and Avenger as avoiding you. Of course, each of those generally only has one bomb slot, so if they used it elsewhere, they won't tangle with you - unless they have a "loaded" "DummyBomb" still on a "B" node... Thanks to Hebe and Jeff-Groves for helping us to further understand loadouts - IF I did this correctly, that is...
