Primary vs. Secondary Comm Issue

[Chappy500]

Hey all, didn't want to post this under bugs until seeing if maybe I am just doing something incorrectly.  Based on several Youtube videos, you should be able to set up your primary and secondary comms so that you can use the swap button for anticipated changes.  I am having an issue where I input the Primary at Kobuleti (133.000), press swap to bring up the Secondary, and enter the ATIS channel I set up using Funkyfranky's work (126.800 in this case).  Once I press enter, it switches the Secondary back to a default 127.500.  

Is this normal behavior?  I know I could go in with the mission editor and setup all the comms channels that way, but that defeats the purpose of entering in game on the fly.  Curious if anyone else has had this issue or if I am doing something wrong.  I made a generic new mission with nothing else in it and no ATIS scripting, and it still does it, see attached track.

AH64 Comm Issue.trk

Edited December 23, 2022 by Chappy500
Adding track

[Cato]

I've had the same issue. Input one frequency into the active and one in the standby and when I swap, it goes back to the old frequency I replaced. Don't know if it is a bug or not cause we do use an ATIS script on our server. Looking forward to presets

[Swift.]

The way those secondary comms work is its the last entered comm.

PRI=B SEC=A
I enter C via the Man or via a preset.
PRI=C SEC=B
I enter D via the Man or via a preset
PRI=D SEC=C

 

As for it defaulting to 127.5 I've heard that mentioned before, but never experienced it myself. Maybe try out what I said above and see if it still presents that failure mode. If it stops that'll be an interesting thing to report. Maybe there is some hidden pri/sec thing going, worth a go I think.