Assigning FAC Callsigns and Freqs

[Habu_69]

I notice that the FAC ASSIGN GROUP task has boxes for assigning freq and callsign in addition to the PERFORM COMMAND functions of Set Callsign and Set Frequency. Are these 2 redundant procedures to set the same attributes? If so, is one procedure preferred over the other?

[Habu_69]

I guess this question is either too trivial or too hard.

[ENO]

If memory serves there were originally two ways to setup jtac with one being better than the other. I think the assign group with the feature built in was the preferred but its been awhile. That would make the other commands unnecessary.

 

If you just searched for it (setup jtac) either in here or in google (add dcs mission editor) it would have left you with the answer.

[Habu_69]

Well, I did search for this question and got no joy. I understand that the ASSIGN GROUP JTAC protocol produces more consistent in-sim results, but my question remains. I have come across a mission by another author in which he assigned conflicting callsigns and frequencies to the same JTAC unit -- one using PERFORM COMMAND \ SET FREQ and SET CALLSIGN, and a second set using PERFORM TASK \ ASSIGN GROUP freq and callsign menus.

 

I was wondering if anyone else had already investigated this situation to save me the trouble. Apparently not. Maybe I am missing something obvious, but it seems odd that ED would allow this apparent conflict to exist.

[Habu_69]

OK, to close this topic, some brief experimenting led me to the following conclusions:

 

1. If a JTAC unit is assigned conflicting callsigns or freqs, that unit will not respond at all.

 

2. Since freq and callsign must be assigned in the ASSIGN GROUP and the ENGAGE GROUP task menus, the SET FREQ and SET CALLSIGN commands appear to no longer have a useful function and can break the mission, if incorrectly assigned.