Jump to content

Recommended Posts

Posted

Hello,

 

 

For unknow reason, after take off, the communication menu doesn't work. Nothing is shown when I press the default's key "/". but when landed, all works again.

 

 

Do you know what I doing wrong ?

 

 

Thanks

Specs: Win10 64bits Pro, Intel i9-9900K | 32Go | RTX 2080 Ti | M.2 SSD 850go x2

Hardware: HTC Vive Pro + X56

Maps : Normandy + Assets | Gulf | Nevada

DCS Modules: FC3 | UH-1H | Mi-8MTV2 | A-10C | F/A-18C | Ka-50 | SuperCarrier | F-14A/B | F-5E | F-86F Sabre | MiG-15bis | Mig-19 | MiG-21bis | AV-8B | Fw 190 D-9 | SA342 | P-51D | Bf 109 K-4 | Spitfire LF Mk. IX | M-2000C | F-16C

 

Posted
Hello,

 

 

For unknow reason, after take off, the communication menu doesn't work. Nothing is shown when I press the default's key "/". but when landed, all works again.

 

 

Do you know what I doing wrong ?

 

 

Thanks

You may have to try using your binding for communication on your hotas. Just check your comms key bind in control menu.

Windows 10 Pro 64bit|Ryzen 5600 @3.8Ghz|EVGA RTX 3070 XC3 Ultra|Corair vengence 32G DDR4 @3200mhz|MSI B550|Thrustmaster Flightstick| Virpil CM3 Throttle| Thrustmaster TFRP Rudder Pedal /Samsung Odyssey Plus Headset

Posted

As others said, check in your Controls settingss under the two follwings names:

 

 

 

COMM Switch - Comm 1 (Ralt+\) Make sure it's backslash and not Slash

 

COMM Switch - Comm 2 (RCtrl+\) Make sure it's backslash and not Slash

Posted

Actually, in my case it even is #. Depends on keyboard layout. / was just a wild guess plus the OP said it was the default key for general comms, but I think that would be - in my case (next to , and .).

dcsdashie-hb-ed.jpg

 

Posted

Thanks, I'll try that: What is strange, is that it work while on ground.

Specs: Win10 64bits Pro, Intel i9-9900K | 32Go | RTX 2080 Ti | M.2 SSD 850go x2

Hardware: HTC Vive Pro + X56

Maps : Normandy + Assets | Gulf | Nevada

DCS Modules: FC3 | UH-1H | Mi-8MTV2 | A-10C | F/A-18C | Ka-50 | SuperCarrier | F-14A/B | F-5E | F-86F Sabre | MiG-15bis | Mig-19 | MiG-21bis | AV-8B | Fw 190 D-9 | SA342 | P-51D | Bf 109 K-4 | Spitfire LF Mk. IX | M-2000C | F-16C

 

Posted
Thanks, I'll try that: What is strange, is that it work while on ground.

 

 

 

 

On ground might be for normal communcation menu, such as ground crew.

Posted
Actually, in my case it even is #. Depends on keyboard layout. / was just a wild guess plus the OP said it was the default key for general comms, but I think that would be - in my case (next to , and .).

 

 

 

 

Yep, that's why i directly pointed him how it's named, because i was so looking for it at first.

Posted

/ works for general comms on the ground. Once you are airborne you have to use the radio ptt buttons (whatever they are mapped too) for comm 1 and comm 2.

Posted

Ok that's it ! usually I used "/" key for other modules !

 

 

Thanks!

Specs: Win10 64bits Pro, Intel i9-9900K | 32Go | RTX 2080 Ti | M.2 SSD 850go x2

Hardware: HTC Vive Pro + X56

Maps : Normandy + Assets | Gulf | Nevada

DCS Modules: FC3 | UH-1H | Mi-8MTV2 | A-10C | F/A-18C | Ka-50 | SuperCarrier | F-14A/B | F-5E | F-86F Sabre | MiG-15bis | Mig-19 | MiG-21bis | AV-8B | Fw 190 D-9 | SA342 | P-51D | Bf 109 K-4 | Spitfire LF Mk. IX | M-2000C | F-16C

 

  • Recently Browsing   0 members

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