@Atlas said in AVCS4 Immersive Voice Control Radios for VoiceAttack:
@SemlerPDX
Hmmm… so I guess I should un-map the VA PTT and just use your program to map it?
If I do, which of the above options is the most appropriate to select?
You can use either system just fine, you just can’t use them both at the same time, if that makes sense.
If you are using my custom “Global Mode”, this is essentially the same is the native PTT Mode in VA anyway, simply without the benefit of my own voice command based set/edit/delete system with its ability to set up to 6 total push-to-talk keys, joystick buttons, and/or mouse buttons.
The reason I designed my own system was two-fold: to allow multiple PTT keys/buttons with a simple and easy voice command & user choice input UI, and an alternate mode that allows only restricting the BMS radio (menu) keypress commands and not ALL commands throughout VoiceAttack. That latter function is an option for those who also use VA for various things, even setting/resetting TrackIR or controlling recording software, etc. during multiplayer flight.
It makes sense in BMS to transmit our actual voice radio request to multiplayers on the same radio channel that we’d be using to send a keypress based macro to issue that corresponding radio command in our radio menu so they don’t merely hear that radio AI just talking out of nowhere, and hear proper and appropriate radio traffic. But we don’t need them to hear us tell TrackIR to Pause or hear us ask our VoiceAttack “What time is it?”, so my “DEFAULT” mode fills this niche.
The native PTT system in VoiceAttack can’t exactly do all this stuff, and that’s why mine exists.
The following video demonstrates my PTT system as I talk about it in greater detail, if it helps: