Jump to content

Additional comms menu not opening unless wheels on ground


Recommended Posts

I have what appears to be an odd bug: Over the last few missions...I am currently on mission 13 I believe...when asked to use F10 on comms menu to speak to those lovely people in control of the mission for either confirmation to engage or for the next action to be triggered, I cannot do so unless my wheels are on the ground. I know this as I waited in one mission as I knew there would be a message that needed a response, so I remained on the ground and it worked. I therefore employed the next comms (in the nest mission) by landing. Again, this worked (but would not open when in flight). On the current mission (the one after the convoy) which involves escorting Mi 24's to engage dangerous sheds in the mountains...I have the same issue. I decided to literally touch back wheels whilst flying low to the ground...which again worked (but no comms menu in flight). I have checked the comms channels (several times) but this is always on the correct channel... If this is correct...acrobatics every time comms is needed seems excessive...

 

Question...anyone else with this issue...and I doing something wrong...if not...any ideas?? Thanks

Link to comment
Share on other sites

On 4/19/2021 at 9:26 PM, Scorpion_knight said:

I have what appears to be an odd bug: Over the last few missions...I am currently on mission 13 I believe...when asked to use F10 on comms menu to speak to those lovely people in control of the mission for either confirmation to engage or for the next action to be triggered, I cannot do so unless my wheels are on the ground. I know this as I waited in one mission as I knew there would be a message that needed a response, so I remained on the ground and it worked. I therefore employed the next comms (in the nest mission) by landing. Again, this worked (but would not open when in flight). On the current mission (the one after the convoy) which involves escorting Mi 24's to engage dangerous sheds in the mountains...I have the same issue. I decided to literally touch back wheels whilst flying low to the ground...which again worked (but no comms menu in flight). I have checked the comms channels (several times) but this is always on the correct channel... If this is correct...acrobatics every time comms is needed seems excessive...

 

Question...anyone else with this issue...and I doing something wrong...if not...any ideas?? Thanks

+1 to what ftmch said. You need to be on the correct channel/frequency and have line of sight to be able to use the radio. If there is a mountain blocking line of sight between you and the "target" of radio call you need to climb/wait for call until you crossed the mountain ridge.

 

comms.jpg

Modules: KA-50, A-10C, FC3, UH-1H, MI-8MTV2, CA, MIG-21bis, FW-190D9, Bf-109K4, F-86F, MIG-15bis, M-2000C, SA342 Gazelle, AJS-37 Viggen, F/A-18C, F-14, C-101, FW-190A8, F-16C, F-5E, JF-17, SC, Mi-24P Hind, AH-64D Apache, Mirage F1, F-4E Phantom II

System: Win 11 Pro 64bit, Ryzen 3800X, 32gb RAM DDR4-3200, PowerColor Radeon RX 6900XT Red Devil ,1 x Samsung SSD 970 EVO Plus 2TB NVMe, 2 x Samsung SSD 2TB + 1TB SATA, MFG Crosswind Rudder Pedals - VIRPIL T-50CM and VIRPIL MongoosT-50 Throttle - HP Reverg G2, using only the latest Open Beta, DCS settings

 

Link to comment
Share on other sites

Ok...I will certainly give that a go, I check my key binding, I will let you know if it works...it's odd that I can use the comms when I land in situ though...so I'll be in the correct trigger area but in the air it doesn't bring up the comms menu to select F10, but if I land at that location or even just touch the ground with my wheels ( whilst still moving) that allows me to open the menu too. I am on the correct radio channel by the way. Thanks for the reply, I will re visit it tonight 😀

Link to comment
Share on other sites

Thats because the comms menu binding doesn't use your radio equipment, it's more a talking to someone via intercom*/open canopy....not your radio. That's why it works on the ground but not in the air, it's the same behaviour in every other module.

 

* despite the fact that there are seperate intercom bindings for several modules

Modules: KA-50, A-10C, FC3, UH-1H, MI-8MTV2, CA, MIG-21bis, FW-190D9, Bf-109K4, F-86F, MIG-15bis, M-2000C, SA342 Gazelle, AJS-37 Viggen, F/A-18C, F-14, C-101, FW-190A8, F-16C, F-5E, JF-17, SC, Mi-24P Hind, AH-64D Apache, Mirage F1, F-4E Phantom II

System: Win 11 Pro 64bit, Ryzen 3800X, 32gb RAM DDR4-3200, PowerColor Radeon RX 6900XT Red Devil ,1 x Samsung SSD 970 EVO Plus 2TB NVMe, 2 x Samsung SSD 2TB + 1TB SATA, MFG Crosswind Rudder Pedals - VIRPIL T-50CM and VIRPIL MongoosT-50 Throttle - HP Reverg G2, using only the latest Open Beta, DCS settings

 

Link to comment
Share on other sites

Yes, well...this has resolved my issue, thanks again for responding. I obviously knew this at some point as I have a key binding for it AND a separate button on a tablet button box specifically for the Radio trigger (in bright green no less)...which to be frank is very obvious so I can only think I have suffered some brain shrinkage over the last few months and forgotten this was a thing.

 

At least I can now do some rather impressive aerobatic manoeuvres in the Mi8 🤨

 

Relieved...SK

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...