Forced Auto COMM when COMM I and COMM II were explicitly selected

[Polonsky]

Using COMM I/COMM II with "RAlt+\" or" RCtrl+R" will always ends up in the AUTO COMM option, even if I've deleted the the default "\" key binding for AUTO COMM, as is shown in the "Communication menu" in the screenshot above. This is annoying as the channel were were changed unexpected and user has to scroll all the way back to Chanel 1-2 every time contacting the ATC. Test with the VBIED mission. Check the top right menu in the screenshots below.

 

For comparison, the stock F18C Mission doesn't come with such error as shown in the screenshot below

Edited yesterday at 03:26 AM by Polonsky

[Scotch75]

Using COMM I/COMM II with "RAlt+\" or" RCtrl+R" will always ends up in the AUTO COMM option, even if I've deleted the the default "\" key binding for AUTO COMM, as is shown in the "Communication menu" in the screenshot above. This is annoying as the channel were were changed unexpected and user has to scroll all the way back to Chanel 1-2 every time contacting the ATC. Test with the VBIED mission. Check the top right menu in the screenshots below.

 
For comparison, the stock F18C Mission doesn't come with such error as shown in the screenshot below

I think this occurs when the mission is set with "Easy Communications" on.
Cheers!


Sent from my SM-G998B using Tapatalk

[Polonsky]

4 minutes ago, Scotch75 said:

I think this occurs when the mission is set with "Easy Communications" on.
Cheers!


Sent from my SM-G998B using Tapatalk
 

I’ve disabled Easy Communications in my settings and checked the “ignore mission configuration, use mine” option. This problem  doesn’t occur before September 

[Scotch75]

Hhhmm, ok. Not sure what is happening there then.


Sent from my SM-G998B using Tapatalk

[Looking Glass]

Thanks chaps. No idea what is happening here. Will keep an eye out to resolve this 

 

LG