correct as-is Redundant Radio Commands

[SharpeXB]

The A-10CII has two separate commands for each radio. The trouble is the VOIP command (which I suppose is intended for SRS) doesn't bring up the radio menu and the radio menu commands don't work with SRS. Other modules like the Hornet combine these commands or like the M-2000 have a PTT which calls the radio menu and also works with SRS. Not sure why the A-10 has these redundant commands, but they don't function very well. They should just be combined.

[MAXsenna]

The A-10CII has two separate commands for each radio. The trouble is the VOIP command (which I suppose is intended for SRS) doesn't bring up the radio menu and the radio menu commands don't work with SRS. Other modules like the Hornet combine these commands or like the M-2000 have a PTT which calls the radio menu and also works with SRS. Not sure why the A-10 has these redundant commands, but they don't function very well. They should just be combined.

The VOIP commands are for ED's own VoiP MP integrated system. They are not for SRS. To my knowledge you configure your own settings in SRS outside of DCS. SRS don't know your settings in DCS.

Sent from my SM-A536B using Tapatalk

[SharpeXB]

12 minutes ago, MAXsenna said:

The VOIP commands are for ED's own VoiP MP integrated system.

That’s what I thought they were at first too but that appears to use a separate menu altogether. I haven’t ever used it though.

The other modules have a single command that brings up the radio and works with SRS, they don’t have this VOIP command. 

[MAXsenna]

That’s what I thought they were at first too but that appears to use a separate menu altogether. I haven’t ever used it though.
The other modules have a single command that brings up the radio and works with SRS, they don’t have this VOIP command. 

Yeah, that's why you want to use the non VOIP bindings in any case. I believe some 3rd party modules only have one option where they use short press for the menu, and long press for VOIP. Will check later. Might even be modules that don't really support VOIP in that sense. I've never used it. Only SRS. In a perfect world. Voice Comms/Speech Recognition would be natively supported in DCS, and when enabled. Would suppress the player AI voice, both in SP and MP. So the need for different bindings for VOIP/SRS would absolutely be redundant. Many users use VAICOM, but choose to have different bindings there as well, so they're voice won't be broadcasted, (which sort of defeats the whole purpose if you ask me regarding ATC), because the pilot game voice would be broadcasted as too. And that sounds a little ridiculous I admit. Hopefully there will be a different setup/solution if we ever get an upgraded ATC. You see now why a new better ATC is regarded as a highly anticipated request for many users?

Sent from my SM-A536B using Tapatalk

[Yurgon]

1 hour ago, SharpeXB said:

The trouble is the VOIP command (which I suppose is intended for SRS)

Nope. As MAXsenna already said, this is for ED's own Voice Chat. It's always been ED's stance that DCS doesn't care for non-licensed mods and certainly won't include default bindings for tools like SRS. This stance might change in the future, but currently that's just the way it is.

1 hour ago, SharpeXB said:

The trouble is the VOIP command [...] doesn't bring up the radio menu and the radio menu commands don't work with SRS.

This depends on a bunch of options and settings.

If I understand correctly, SRS will use the DCS "HOTAS Mic Switch Aft/Down/Forward (VOIP)" as PTT when:

• SRS -> Settings -> Controls / Cockpit Integration -> ALWAYS allow SRS Hotkeys if set to OFF
• SRS -> Settings -> Controls / Cockpit Integration -> Allow INCOCKPIT DCS Controlled PTT is set to ON

In this scenario, you will not be able to use the HOTAS Mic Switch for both SRS and the in-game radio menu. Obviously, the same is true when using DCS' own Voice Chat.

You could still use a modifier like any of the Shift or Ctrl keys or define one of your joystick or throttle buttons as a modifier and bind the in-game radio menu accordingly.

The alternative is to ignore DCS' VOIP buttons and define your radio PTT keys within SRS.

SRS will use its own Controls Configuration as PTT when:

• SRS -> Settings -> Controls / Cockpit Integration -> ALWAYS allow SRS Hotkeys if set to ON
• SRS -> Controls -> Radio 1 is set to your HOTAS Mic Switch Forward (or whatever button you intend to use)
• SRS -> Controls -> Radio 2 is set to your HOTAS Mic Switch Down (or whatever button you intend to use)
• SRS -> Controls -> Radio 3 is set to your HOTAS Mic Switch Aft (or whatever button you intend to use)

So in this scenario, SRS doesn't care for whatever VOIP keys are set up within DCS, allowing you to leave the VOIP ones unconfigured and bind the HOTAS Mic Switch Aft/Down/Forward commands (without the VOIP-addendum) to an appropriate switch on your HOTAS.

All that said, I've got the setup from the second scenario, and recently unbound the in-game radio overlay from the PTT-keys, because I find it rather annoying to get the overlay pop up whenever I talk to anyone via SRS (or more precisely, I now use a modifier for the in-game radio overlay with my HOTAS Mic Switch). Muuuuuuch better for my taste.

[SharpeXB]

7 hours ago, Yurgon said:

The alternative is to ignore DCS' VOIP buttons and define your radio PTT keys within SRS.

SRS will use its own Controls Configuration as PTT when:

• SRS -> Settings -> Controls / Cockpit Integration -> ALWAYS allow SRS Hotkeys if set to ON
• SRS -> Controls -> Radio 1 is set to your HOTAS Mic Switch Forward (or whatever button you intend to use)
• SRS -> Controls -> Radio 2 is set to your HOTAS Mic Switch Down (or whatever button you intend to use)
• SRS -> Controls -> Radio 3 is set to your HOTAS Mic Switch Aft (or whatever button you intend to use)

So in this scenario, SRS doesn't care for whatever VOIP keys are set up within DCS, allowing you to leave the VOIP ones unconfigured and bind the HOTAS Mic Switch Aft/Down/Forward commands (without the VOIP-addendum) to an appropriate switch on your HOTAS.

That’s the solution I was looking for, thanks

PS this is confusing because other aircraft like the Hornet don’t need this workaround. But it looks like an SRS issue not a DCS one. 

Edited October 29, 2024 by SharpeXB

[Yurgon]

2 hours ago, SharpeXB said:

PS this is confusing because other aircraft like the Hornet don’t need this workaround. But it looks like an SRS issue not a DCS one. 

It's a bit of a historic mess. ED have learned a lot about keybinds and our needs, demands and requirements, from the casual gamer who will remember a couple of keyboard combos to cockpit builders who need clearly defined commands for each switch position (and not just "increment" and "decrement" keybinds, for example). ED have tried to make modules and switch behavior consistent, but are of course also trying not to implement breaking changes that would require us to do the whole controller setup all over again.

Long story short, not all modules use the same keybinds and not all modules are consistent. Some, especially those in Early Access, may still change, and relatively new features like ED's own VOIP may also see changes and updates as player feedback makes its way back to ED. With a bit of finesse and sometimes lua-file hacking, it's usually possible to achieve what we need, and reasonable requests may also warrant a wishlist-thread to let ED know what we'd like to see implemented in the future.

[SharpeXB]

13 minutes ago, Yurgon said:

It's a bit of a historic mess. ED have learned a lot about keybinds and our needs, demands and requirements, from the casual gamer who will remember a couple of keyboard combos to cockpit builders who need clearly defined commands for each switch position (and not just "increment" and "decrement" keybinds, for example). ED have tried to make modules and switch behavior consistent, but are of course also trying not to implement breaking changes that would require us to do the whole controller setup all over again.

Long story short, not all modules use the same keybinds and not all modules are consistent. Some, especially those in Early Access, may still change, and relatively new features like ED's own VOIP may also see changes and updates as player feedback makes its way back to ED. With a bit of finesse and sometimes lua-file hacking, it's usually possible to achieve what we need, and reasonable requests may also warrant a wishlist-thread to let ED know what we'd like to see implemented in the future.

It’s a different topic but they should make it possible to bind the Radio Menu and VOIP to the same button. Long and short presses would be a good idea. That’s a big obstacle to using the in-game feature and SRS lets you do that. 
Already a wish

 

[Loadie]

On 10/28/2024 at 9:56 PM, Yurgon said:

Nope. As MAXsenna already said, this is for ED's own Voice Chat. It's always been ED's stance that DCS doesn't care for non-licensed mods and certainly won't include default bindings for tools like SRS. This stance might change in the future, but currently that's just the way it is.

This depends on a bunch of options and settings.

If I understand correctly, SRS will use the DCS "HOTAS Mic Switch Aft/Down/Forward (VOIP)" as PTT when:

• SRS -> Settings -> Controls / Cockpit Integration -> ALWAYS allow SRS Hotkeys if set to OFF
• SRS -> Settings -> Controls / Cockpit Integration -> Allow INCOCKPIT DCS Controlled PTT is set to ON

In this scenario, you will not be able to use the HOTAS Mic Switch for both SRS and the in-game radio menu. Obviously, the same is true when using DCS' own Voice Chat.

You could still use a modifier like any of the Shift or Ctrl keys or define one of your joystick or throttle buttons as a modifier and bind the in-game radio menu accordingly.

The alternative is to ignore DCS' VOIP buttons and define your radio PTT keys within SRS.

SRS will use its own Controls Configuration as PTT when:

• SRS -> Settings -> Controls / Cockpit Integration -> ALWAYS allow SRS Hotkeys if set to ON
• SRS -> Controls -> Radio 1 is set to your HOTAS Mic Switch Forward (or whatever button you intend to use)
• SRS -> Controls -> Radio 2 is set to your HOTAS Mic Switch Down (or whatever button you intend to use)
• SRS -> Controls -> Radio 3 is set to your HOTAS Mic Switch Aft (or whatever button you intend to use)

So in this scenario, SRS doesn't care for whatever VOIP keys are set up within DCS, allowing you to leave the VOIP ones unconfigured and bind the HOTAS Mic Switch Aft/Down/Forward commands (without the VOIP-addendum) to an appropriate switch on your HOTAS.

All that said, I've got the setup from the second scenario, and recently unbound the in-game radio overlay from the PTT-keys, because I find it rather annoying to get the overlay pop up whenever I talk to anyone via SRS (or more precisely, I now use a modifier for the in-game radio overlay with my HOTAS Mic Switch). Muuuuuuch better for my taste.

Have you considered making a video on how to do this? I just started using the A-10Cii after a while and can’t for the life of me get SRS to work anymore. I had it working last year without issue. Now, I’m pulling whatever hair I have left out.

[Yurgon]

On 11/22/2024 at 3:50 AM, Loadie said:

Have you considered making a video on how to do this? I just started using the A-10Cii after a while and can’t for the life of me get SRS to work anymore. I had it working last year without issue. Now, I’m pulling whatever hair I have left out.

Sorry for taking so long to respond!

A few days ago I went through all SRS settings with a new DCS player. We got it to work, but it took a bit of back and forth and I realize there's a lot of settings I'd have to test out in order to make a definitive statement. Long story short, no video planned here, and if I were to do any DCS tutorial videos, there's a ton of stuff I'd probably do before making my way to SRS.

But if you have any concrete questions or issues, be sure to ask around, for instance in the SRS thread, or join Ciribob's SRS Discord, he usually asks users to find help there and the people there are usually very savvy and friendly.

[Loadie]

Thanks for responding! I’ve got it sorted out. Just need to get it working through oculus virtual desktop now…….