(single player) COM1 / COM2 not working when TACAN selected as nav source

[gulredrel]

Hello,

did a short cold start mission at Kobuleti. track attached.

- COM1 (UHF radio) manual set to 262 MHz, also Ch8 set in ME to 262 MHz.

- COM2 (U/VHF) set Ch 8 to 133 MHz.

- canopy closed, engine not running, COM1 set and COM selector set to COM1 --> startup request okay

- after INS alignment and system setup requested taxi to RW okay

- reaching end of RW --> no communication

- pressing COM1 or COM2 switch, corresponding light showed up on RDU.

    

Does this work for anybody else? I'm a bit confused. Never had such problems using coms with other modules, once correct radio and frequency was selected.

 

edit: What I didn't try was to push and hold the button!? But that would be weird, cause it isn't implemented in other modules this way.

 

Thanks for the help

Jens

MB-339_radio_test_Kobuleti.trk

Edited February 11, 2023 by gulredrel
edited title after new findings

[MAXsenna]

What coalition is the airbase?
Caucasus cold start. Novorrosjysk (?), blue coalition, radios tunes and working.
Flew to Senaki, neutral coalition. Correctly tuned radios, no respons, but was told to park when I landed, no comms after that. Even parked and shutdown. Flew on to Batumi. Same thing.

Sent from my MAR-LX1A using Tapatalk

[gulredrel]

It's Kobuleti and it's red coalition as well as the flown nation.

Have a similar mission which I use mostly with different aircraft. Almost all airfields are red as well as the nations. Never had such issues in other aircraft. In MB-339 can't get contact even inbound requests or whatever.

Also got the automatic message after landing when slow enough to taxi to parking, but nothing else. Only after complete shutdown I can request rearm / refule as well as startup. But I guess this is due to the engine not running and communication working in a different way.

[LordOrion]

Here are my 2 cents:

I've noticed that both COMM1 and COMM2 PTT keybinds opens the COMM2 menu, which works ok for me.

[gulredrel]

There is something weird. Yesterday it worked for me using COM2. Today I had behavior described above again.

Maybe it's something with the state or initializing of the com panel on the front right?

While in the air, I couldn't contact ATC at Kobuleti, after fiddling around with the COMS panel, pushing / pulling VOR/ILS and TACAN knobs, ILS morse code was playing. Pushing / pulling com1 / com2 knobs, suddenly I was able to communicate with Kobuleti ATC without changing something on the com2 radio itself.

[gulredrel]

Sorry, have no idea, why the video has these flickering. Hope you can see my clicking. Maybe I can redo the video later.

It's indeed something in connection with the audio panel and VOR NAV source selection.

Tuned TACAN and ILS, checked NAV sources, fiddled with audio panel. Couldn't call ATC for takeoff clearance.

After selecting NAV source to VOR/ILS and pulling VOR/ILS audio knob and the morse code could be heared, I was able to call ATC for takeoff clearance.

No track this time, was too fast stopping mission end forgot to save the track.

[scoobie]

I've got problems with calling ATC, too. Typically (or always) the first contact is successful (request start-up), then request taxi and request take-off both fail (silence), then I go fly somewhere and when I get back to the airfiled and contact ATC on approach - this works again. Go figure...

EDIT: Removed some text from this post. I thought I figured out when the radio works (with wrong selection of COMM1/COMM2 selector on ICS panel), but no - today it works all the time, regardless of that. I have no clue what's going on.

Edited November 2, 2022 by scoobie

[gulredrel]

My current workaround is using COM2 radio, manual frequency.

As soon as no ATC communication is possible. Change NAV source selector next to the HSI from TACAN to VOR if a frequency is selected. If that's not enough, I also pull the VOR knob on the audio panel. As soon as the morse code can be heard, ATC communication works again.

Off topic update regarding the video. I've no idea why, but every recording using win + g option will show this black screen flickering. Tried vsync on/off. no difference. Will check nvidia drivers. Didn't have issues in DCS 2.7 with it.

[Jel]

Am 3.11.2022 um 20:38 schrieb gulredrel:

My current workaround is using COM2 radio, manual frequency.

As soon as no ATC communication is possible. Change NAV source selector next to the HSI from TACAN to VOR if a frequency is selected. If that's not enough, I also pull the VOR knob on the audio panel. As soon as the morse code can be heard, ATC communication works again.

 

seems to work ok as workaround. Still a weird bug

[6S.Duke]

Hi!
Is this bug solved?

Inviato dal mio ASUS_I005D utilizzando Tapatalk

[Jel]

Still getting this issue frequently, workaround as mentioned above seems to work.

So: No.

Edited February 8, 2023 by Jel

[gulredrel]

On 2/8/2023 at 8:51 AM, 6S.Duke said:

Hi!
Is this bug solved?

Inviato dal mio ASUS_I005D utilizzando Tapatalk
 

Still an issue. But I guess I narrowed it down.

Communication is no more possible, as soon as TACAN station is tuned and TACAN is selected as navigation source on the NAV panel.

Once you use no nav source or VOR or RNAV, you can talk to and receive ATC information.

Track attached showing Com2 inbound and abort communication with Kobuleti ATC. After selecting TACAN as nav source, the com menu will not open. deselecting TACAN nav source, everything works again.

PS: There's also something with the keybinds and COM1/2 selector. I've mapped com1 PTT and com2 PTT to two buttons, but only the com2 ptt button really works but the com menu only shows COM2 even when talking through com1 radio(?) It's also in the track but that's a bit confusing.

20230211_MB339_no_COM_when_TACAN_nav_selected.trk

Edited February 11, 2023 by gulredrel
Track attached

[gulredrel]

Looks like this is fixed with yesterday's open beta DCS 2.8.5.40170. Having TACAN switched on and selected, I was able to talk to ATC on approach.