not a bug DL Setup in Mission Editor not fully transfered to cockpit?

[Flagrum]

If you set up a flight in the ME, the primary comms freq. is synchronized with the pre-configured frequencies of the radios (and with the default comms freq. of the whole flight). In case of our AH-64 this is channel 1 of the ARC-164. If you change the freq. in the upper portion, it also automatically changes radio channel #1 and vice versa.

The datalink presets corresponds to those pre-configured radio frequencies. So by default, PRESET1 corresponds to radio channel #1, PRESET2 to radio channel #2 and so on. Thus, using PRESET1 (= ARC-164 chan.# 1 = AI flight primary comms. freq.) should and does work.

The issue is now, that PRESET1 is not assigned to the radio when entering the cockpit. Instead, the ARC-164 is set to MAN and the primary comms. frequency, while all other radios get their appropriate DL preset correctly assigned to it. You have to manually assign PRESET1 to the radio - then also the DL functions work.

I assume, this is due to the way the radios are initialized at mission start:

1. assign DL presets
2. assign primary comms. frequency to the whole flight and thus, overriding the DL preset

Did I miss here something, or is this really a bug/quirk? Or how could I get the correct DL preset assigned to the ARC-164 automatically?

Edited November 5, 2023 by Flagrum

[flanker0ne]

Very saddly, at this time there is no tool to automatically spread the DL settings among the flight members

Be ready to spend hours of monkey-job

Edited November 5, 2023 by flanker0ne

[Flagrum]

1 hour ago, flanker0ne said:

Very saddly, at this time there is no tool to automatically spread the DL settings among the flight members

Be ready to spend hours of monkey-job

 

You have to redo the DL preset settings for the other members of your flight, yes. But you can't even adjust the radio channel frequencies for your AI flight members. I am not sure, if those are inherited from the flight lead or if you are stuck with the default frequencies in this case in order to get it to work. Until now, AI flight members simply had no use of any other radio other than the one for the primary flight comms freq., aka ARC-164 ch. #1. So why would they inherit the other radio settings anyways?

But in my test, I just kept everything at the defaults - except the primary comms. frequency / channel #1 of the ARC-164. This allowed me to a) talk to my wingman just fine and also b) use DL functions over that radio/frequency. The other radios / frequencies I did not investigate (yet).

But anyways, while there are still other open questions, my main concern right here is just why the DL Preset setting for exactly the radio / channel, which is used as the primary comms. frequency, is not transferred into the cockpit, while for all other radios it does work.

Note: I am only talking about Single Player with AI flight members!

 

[Flagrum]

Hi ED Team

Is this a known issue and/or already reported as a bug? Then please move this thread to the Bug section then, if appropriate.

Or did I just miss something else here?

Thanks!

[Flagrum]

If you set up a flight in the ME, the primary comms freq. is synchronized with the pre-configured frequencies of the radios (and with the default comms freq. of the whole flight). In case of our AH-64 this is channel 1 of the ARC-164. If you change the freq. in the upper portion, it also automatically changes radio channel #1 and vice versa.

The datalink presets corresponds to those pre-configured radio frequencies. So by default, PRESET1 corresponds to radio channel #1, PRESET2 to radio channel #2 and so on. Thus, using PRESET1 (= ARC-164 chan.# 1 = AI flight primary comms. freq.) should and does work.

The issue is now, that PRESET1 is not assigned to the radio when entering the cockpit. Instead, the ARC-164 is set to MAN and the primary comms. frequency, while all other radios get their appropriate DL preset correctly assigned to it. You have to manually assign PRESET1 to the radio - then also the DL functions work.

I assume, this is due to the way the radios are initialized at mission start:

1. assign DL presets
2. assign primary comms. frequency to the whole flight and thus, overriding the DL preset

Did I miss here something, or is this really a bug/quirk? Or how could I get the correct DL preset assigned to the ARC-164 automatically?

  

On 11/5/2023 at 8:05 AM, flanker0ne said:

Very saddly, at this time there is no tool to automatically spread the DL settings among the flight members

Be ready to spend hours of monkey-job

 

You have to redo the DL preset settings for the other members of your flight, yes. But you can't even adjust the radio channel frequencies for your AI flight members. I am not sure, if those are inherited from the flight lead or if you are stuck with the default frequencies in this case in order to get it to work. Until now, AI flight members simply had no use of any other radio other than the one for the primary flight comms freq., aka ARC-164 ch. #1. So why would they inherit the other radio settings anyways?

But in my test, I just kept everything at the defaults - except the primary comms. frequency / channel #1 of the ARC-164. This allowed me to a) talk to my wingman just fine and also b) use DL functions over that radio/frequency. The other radios / frequencies I did not investigate (yet).

But anyways, while there are still other open questions, my main concern right here is just why the DL Preset setting for exactly the radio / channel, which is used as the primary comms. frequency, is not transferred into the cockpit, while for all other radios it does work.

Note: I am only talking about Single Player with AI flight members!

 

___

(This is a repost of

 of the main forum as it is not being moved here)

Edited April 5, 2024 by Flagrum

[Lord Vader]

Hey @Flagrum

Considering how our Mission Editor works at this moment, it is indeed required to manually insert the frequencies.

You can do it in the Com page as part of the cockpit preparation. This is not a bug but a compromise. In the future it's possible we may revisit this item.