PTT buttons using Exposed Variables?

[Jorik]

Hi guys,

 

I'm fairly new to VAICOM but I'm loving every bit of it.

Now do I fly mostly F-14, F-18, Harrier and A-10C and this while using the TM Warthog. But all of these birds have different HOTAS Comm setups. Is there a way to have VAICOM recognize witch module you are flying and set the correct button PTT settings accordingly?

I have noticed in the manual something like Exposed Variables but I have no clue how to tackle the PTT settings the best way.

 

Did anybody succeed in this?

[hornblower793]

I use exposed variables but you do not need to do this for what you want (assuming you are using the same PTT button(s) for each module)

 

Are you flying with easy comms on or off?

 

Sent from my SM-T835 using Tapatalk

[streakeagle]

I don't map in-game radio ptt buttons per the VAICOM instructions.

But I prefer mapping ptt buttons to custom buttons per aircraft, so I have gone against the instructions in having a separate Voice Attack profile for each aircraft and customizing the TX button maps as I see fit. Many aircraft only use one or two of the TX buttons, which can be seen on the VAICOM tab while flying that aircraft in a mission. So, I duplicate either the base DCS profile or one that I have already made for an aircraft that has a similar mapping, fly a mission with the desired aircraft, identify the active TX buttons for that aircraft, then customize the TX button maps to suit my preferences. I try to make my PTT buttons match both their location and switch type as close as possible.

 

One problem I have is that some aircraft have PTT buttons on their stick grips and I change stick grips all the time whereas I always use the same Warthog throttle. So, I have to decide: always make sure to install the grip that my profile uses, customize the profile per grip, map multiple grips, or map the button to the throttle so that it doesn't matter which grip I use. There is a limit to the number of controllers you can map and each VKB grip type counts as a separate controller, so mapping multiple grips only helps for the grips I commonly use.

 

The other problem with my approach is that I have to change profiles every time I change aircraft. With VR, that means briefly peeking out of the headset while alt-tabbing into Voice Attack to select the desired profile. Changing profiles while in-game seems to increase the odds of Voice Attack crashing. But if it crashes, I restart it and it works fine after that.

 

The end result of my approach is that I typically decide what type of aircraft I am going to fly for that session, install the desired grip, start Voice Attack, select that aircraft type's profile, then start DCS World. But I am trying to get into multi-player and I am likely to frequently switch aircraft. The grip problem is solved by generally flying with the MCG Pro, which has so many control options that I can emulate any other grip in the game. But I still have to change VAICOM profiles per aircraft. Interestingly enough, SRS has an option to automatically change profiles per aircraft being flown. It would really be nice if VAICOM had this same capability.