Jump to content

Recommended Posts

Posted

Spitfire radio is on, but the comms menu wont open after pressing \. Works fine in all other modules. Is it working for you, as may just be me and not a recent update bug, I'm thinking.

Posted (edited)

There's not enough info in your post to answer your question, but, to cover general DCS comms "peculiarities" you might not be familar with, please keep in mind that:

a) There's easy comms and realistic comms to choose from in DCS. The former doesn't require setting up radio channels, frequencies etc. in mission editor correctly while the latter does. The choice between two is done by ticking the relevant box in gameplay or realism options (I don't remember which one now);

b) It's possible to communicate ONLY with planes, ATC and ground crew of airbase which belongs to the same coalition colour as you (blue on blue, red on red);

c)  "\" key by default (communications command) is supposed to mimic pilot shouting out of the opened cockpit. Thus, if realistic comms is selected, you can use it to "shout" to ground crew or even ATC, but only while you're on the ground, with canopy open. In every other circumstance you're supopsed to bind and use push-to-talk command - "Alt+\" by default, which mimics using the actual radio equipment of your airplane.

d) Various offline or online missions created by someone else can override your own realism & gameplay settings.

So the question are: do you use easy comms and  which mission exactly you're having problem with (is it one of stock ones available in game or a custom one you made for yourself?)

Edited by Art-J
  • Like 2

i7 9700K @ stock speed, single GTX1070, 32 gigs of RAM, TH Warthog, MFG Crosswind, Win10.

Posted (edited)

Thank you for your reply.

The issue is that the Spitfire on my system does not allow me to open the comms menu, after creating my own new mission in the mission editor, the "\" key does not work. This includes where I have spawned into a new mission while either cold and dark or with engines running. However the Comms menu will appear if I use the "\" key on all other modules. Therefore this leads me to believe that either the spit alone is bugged, or I have a mod that is interfering with the process.

 

I have also tried easy comms on and off, to no effect.

Edited by Taildragger
Posted
10 minutes ago, Taildragger said:

The issue is that the Spitfire on my system does not allow me to open the comms menu, after creating my own new mission in the mission editor, the "\" key does not work. This includes where I have spawned into a new mission while either cold and dark or with engines running. However the Comms menu will appear if I use the "\" key on all other modules. Therefore this leads me to believe that either the spit alone is bugged,

 

Just tested, and the \ key works on my Spit, so I doubt that the module is bugged:

 

vFxTaej.jpg

 

Have you tried the PTT binding, instead of the \  ?

 

ZmtEKXd.jpg

 

  • Like 1

 

For work: iMac mid-2010 of 27" - Core i7 870 - 6 GB DDR3 1333 MHz - ATI HD5670 - SSD 256 GB - HDD 2 TB - macOS High Sierra

For Gaming: 34" Monitor - Ryzen 3600 - 32 GB DDR4 2400 - nVidia RTX2080 - SSD 1.25 TB - HDD 10 TB - Win10 Pro - TM HOTAS Cougar

Mobile: iPad Pro 12.9" of 256 GB

Posted

Yes, I have both the comms "\" key and the PPT "RAlt +\" key bound to my Hotas. One interesting thing is when I use the Comms Hotas bound button. it resets my view only...

Fixed!

I re-bound the comms from the settings menu. Now working.

 

Thanks for your support!

 

  • Like 1
  • Recently Browsing   0 members

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