Where does the apache get the member directory from?

[FalcoGer]

In the apache when editing a preset's NET, there is the member directory feature. How does the (real) apache know which other aircraft exist, what their callsign and datalink ID is? Is it just in the data cartridge? How many slots can there possibly be?

[Raptor9]

This information is loaded via a data cartridge. In DCS, this directory is generated from all friendly AH-64D's in the mission file. The description of each entry is derived from the PILOT data field of the unit within the Mission Editor. (Example: adding an AH-64D helicopter into the Mission Editor will automatically default the PILOT name to "Rotary-1-1", which is what will be shown in the directory for that member's description)

[QuiGon]

16 hours ago, Raptor9 said:

This information is loaded via a data cartridge. In DCS, this directory is generated from all friendly AH-64D's in the mission file. The description of each entry is derived from the PILOT data field of the unit within the Mission Editor. (Example: adding an AH-64D helicopter into the Mission Editor will automatically default the PILOT name to "Rotary-1-1", which is what will be shown in the directory for that member's description)

Does it only list aircraft that have spawned in before yourself or will it also list unoccupied aircraft (empty slots in the MP role selection menu)?

[Floyd1212]

2 hours ago, QuiGon said:

Does it only list aircraft that have spawned in before yourself or will it also list unoccupied aircraft (empty slots in the MP role selection menu)?

It will list all aircraft that are in the mission, occupied or unoccupied..

I was flying with a buddy in a large pub server, and it was just the two of us, but the member directory was 12 pages long.  There seems to be a limit at 12 pages (96 aircraft) as there were 112 Apache slots total in the mission.