Comm1 channel1 radio frequency at mission start does not match what was set in the ME

[pcoud]

We're a group of friends playing in multiplayer on the stable version and exclusively flying the Hornet. In the Hornet, as soon as you switch the battery switch to "on" (cold start), your comm1 channel1 radio is active. So we've taken this habit, everytime we fly: we jump in our aircraft (cold), we switch battery "on", and immediately perform the radio checks within our own package (we use comm1 / chnl1 as our intra flight frequency), and awaits our leader's orders.

 

But lately we are having issues.

 

In the attached mission are 4 client packages (if you want to quickly find them, check "planes", country: France in the ME's unit list)

-Truman BARCAP (3 aircrafts): within the mission editor, you can see that it's comm1 channel1 frequency is set to be 120Mhz

-FROG SEAD (2 aircrafts): 118 Mhz

-PIKE STRIKE: 123 Mhz

-WALLABY: 119 MhZ

 

But once in the plane, most of these comm1/chnl1 frequencies don't match what was set in the editor. The frequency is not even the same within the same group (ie the leader's frequency and its wingman's are different). It's very reproduceable (at least for me). Open the mission in the ME, check by yourself the assigned frequencies to the 4 client packages, then launch the mission, either from within the ME or not, choose a slot and note what's the comm1/chnl1 frequency (if you have SRS up and running, the test will be very quick: as soon as you switch battery ON you'll see the comm1/chnl1 frequency on the SRS overlay. Ifyou don't have SRS you'll have at least to start the right engine to check the value of comm1/chnl1). Do that for all clients aircrafts and see all inconsistencies.

 

IMPORTANT NOTE: the attached .miz was generated by Liberation, so maybe the issue lies there (I have filed a bug report on the Liberation GitHub), but I am still a bit surprised that what is in the actual plane does not match what was in the ME (?)

 

Also, investigating on the above, I realized I had no clue what the herebelow "RADIO" checkbox was for ? What is the purpose of checking or unchecking this checkbox?

 

 

Thx !

 

radio_test.miz

[Grimes]

It might be both SRS and liberation, but probably more liberation. 

 

What looks like what is happening is that it isn't use the same value for the group wide frequency setting and whatever is the first frequency in each unit's custom frequency list. SRS is likely using one value and switching to the other as the power gets applied. These two values should be the same.

 

["Radio"]=
{
    [1]=
    {
        ["channels"]=
        {
            [1]=123.0,

["frequency"]=119.0,

[pcoud]

Thanks for the answer @Grimes. I hadn't checked the mission file, and  what you are pointing out explains what I'm seeing. But then, the question remains: where does this 123Mhz come from? The mission lines you copied hereabove are from the Wallaby group, but in the mission editor, for both units of the Wallaby group here is what you see:

 

 

Comm 1 channel 1 is 119 Mhz, so how does it become 123Mhz once in the mission file ? (maybe a bug when Liberation generates the file?)

 

Also, I am sorry to ask again, but do you know what checking or unchecking the "RADIO" checkbox in the ME does ? (can't find an answer)

 

 

 

[Grimes]

Within the miz file itself the values don't match. The editor likely is displaying whatever is in the frequency box for channel 1 of the first radio because by its rules if you change one it will change the other. So it is assuming the value in channel 1 is the value in frequency and for whatever reason isn't showing the actual value in the miz. If you re-save it then it'll rewrite the value in channel 1 to actually be 119. It is the file that is generated by Liberation. Don't know if it just creates some default frequency for each group and any custom radio preset separately or what. 

 

The radio checkbox is a group toggle for whether or not that group will broadcast messages over their radio. Set to false you won't hear that group, set to true you will. Just an easy on/off so the user doesn't have to add and set 4 different options for that flight. 

[pcoud]

Many thanks @Grimes

On 9/12/2021 at 1:00 AM, Grimes said:

If you re-save it then it'll rewrite the value in channel 1 to actually be 119

If that works, that'd be an easy countermeasure, I'll test it tonight. In the meantime I'll forward all this to the Liberation GitHub dev team.