2.9 includes fancy new datalink features. FlyingUnit needs to be updated to handle it.
I was hoping some of the information (max number of donors and team members) would be something we could export, but it doesn't look like it. There is a connectDatalinks field of the aircraft Lua that is a list of supported datalinks (using the real names rather than the DCS names, so "IDM" rather than SMDL, "Link16" rather than TNDL, and "SADL" instead of A10CDL), and a datalinks field which maps those to some lua files that define some of the datalink behaviors, but there isn't any defined constant we can pull from those (the F-16 one has a hard coded if donors < 4, so I doubt there is a constant elsewhere that I'm overlooking).
It may be best to not try to limit the number of team members or donors (or whatever limits might exist for IDM and SADL) and leave that up to the application. In Liberation that'll work fine for us since we're used to maintaining non-exported metadata for this kind of thing.
The good news is that pydcs doesn't need this to be compatible with 2.9 (not for serializing missions for 2.9 anyway, I haven't tried deserializing a miz created with DCS 2.9). DCS will automatically configure datalink sensibly if we do nothing, but this is needed for pydcs callers to configure it manually.
datalink.miz.txt (renamed for github's filter) is a mission with several flights set up. Each is a 2-ship, with the group name <callsign> <number>, pilots named <callsign> <number>-<member>, voice callsign label/number set the way Wags said to (first and last letter of the callsign, so "Jedi 1-1" has callsign label "JI" and number 11). The setup is:
Hawg 1:
Hawg 2:
Hawg 3:
Devil 1 (hornets):
Jedi 1 (vipers):
Saber 1 (apaches):
Saber 2 (apaches):
Buff 1 is a flight of B-52s, which do participate in datalink but are AI only. They don't have the donor/team datalink tab but do have callsign labels/numbers/STNs.
2.9 includes fancy new datalink features.
FlyingUnitneeds to be updated to handle it.I was hoping some of the information (max number of donors and team members) would be something we could export, but it doesn't look like it. There is a
connectDatalinksfield of the aircraft Lua that is a list of supported datalinks (using the real names rather than the DCS names, so "IDM" rather than SMDL, "Link16" rather than TNDL, and "SADL" instead of A10CDL), and adatalinksfield which maps those to some lua files that define some of the datalink behaviors, but there isn't any defined constant we can pull from those (the F-16 one has a hard codedif donors < 4, so I doubt there is a constant elsewhere that I'm overlooking).It may be best to not try to limit the number of team members or donors (or whatever limits might exist for IDM and SADL) and leave that up to the application. In Liberation that'll work fine for us since we're used to maintaining non-exported metadata for this kind of thing.
The good news is that pydcs doesn't need this to be compatible with 2.9 (not for serializing missions for 2.9 anyway, I haven't tried deserializing a miz created with DCS 2.9). DCS will automatically configure datalink sensibly if we do nothing, but this is needed for pydcs callers to configure it manually.
datalink.miz.txt (renamed for github's filter) is a mission with several flights set up. Each is a 2-ship, with the group name
<callsign> <number>, pilots named<callsign> <number>-<member>, voice callsign label/number set the way Wags said to (first and last letter of the callsign, so "Jedi 1-1" has callsign label "JI" and number 11). The setup is:Hawg 1:
Hawg 2:
Hawg 3:
Devil 1 (hornets):
Jedi 1 (vipers):
Saber 1 (apaches):
Saber 2 (apaches):
Buff 1 is a flight of B-52s, which do participate in datalink but are AI only. They don't have the donor/team datalink tab but do have callsign labels/numbers/STNs.