sthompson

To perhaps state the obvious, ARIO has nothing to do with ATC communications or the Supercarrier, or the Hornet. Seems unlikely that your problems are related to ARIO.

You realize you can do that already and have been able to do so for a long time. it's in the settings. Right?

You only need TX1 if the only radio you want to use in the module is on TX1. But that isn't always the case. My recollection is that in some modules (e.g. The A-10C) you have a choice of AM and FM radios and need separate TX for each. In the Mirage 2000 there are separate UHF and VHF radios and for at least some campaign missions you really want to have them tuned differently so that you can monitor and reply on more than one frequency.

You probably have a registry entry for the stable version. You might get some insights by turning on debugging and checking the log after a restart.

If you are flying Openbeta 2.8 but the VAICOM sliders are set to the release version then VAICOM probably is not updating your lua files properly, and that is the source of the trouble. In general the slider needs to be on the openbeta setting if you are flying openbeta. I suggest you post your "CONFIG" page settings and also tell us the path to where your DCS openbeta version is installed.

The part I highlighted in red is not accurate. With instant select VAICOM will first select Batumi as the intended ATC recipient even if you have not given an explicit SELECT command. However the transmission will go out on whatever frequency the radio is currently tuned to. It is NOT automatically sent on the Batumi tower frequency (unless you are using easy comms). You need to tune the radio first, either using cockpit controls or by using "select tunes radio" and giving an explicit select command.

@Japo32. I am unable to reproduce the problem. Can you confirm that you ran your tests using DCS 2.8 Open Beta version?

That behavior is consistent with what I wrote, so I believe you. However the example you posted did not include a visible "Select" command. In fact it did not show that you gave any commands at all. And so it is impossible to use it to see what might be going wrong now. So turn on debugging, fire up a mission, give that Select command, then report back with the log.

It's several years past time for that!

This example does not show that VoiceAttack actually heard a command. Where are the commands that aren't working? Tip: Turn on debugging in VAICOM options before testing. Also, you complain that the radio is not tuned automatically to Kobuleti. To understand why this might be so, note that in your first screen shot it shows that you have both "Select Tunes Radio" and "Instant Select" both checked. However "Select Tunes Radio" only works with an explicit "Select" command. Simply naming the recipient (e.g. using "Kobuleti, Inbound") will select the recipient (because you have "Instant Select" turned on) but it will not tune the radio. It's always been like that. If you want the radio to tune automatically either use Easy Comms or an explicit Select command. Once things settle down on the community release I hope we can start a wish list for improvements, and it would be nice if "Instant Select" also tuned the radio when "Select Tunes Radio" is on.

In case anyone following this thread has missed the news. VAICOM lives again. Hollywood has released the source code and volunteers have already patched it for DCS 2.8. Head over to the VAICOM forum and/or discord for more info. (Of course VAICOM could be so much better with an exposed API for AI communications.)

Does the VA log show that the select command was recognized and acted upon by VAICOM? If so then the problem will be with the underlying lua code. Probably something changed with DCS 2.8 that requires something new in the VAICOM lua code. If so the fix will require updating the underlying code. I haven't had time to check out the discord or github for the community project yet, but I'm wondering if they have set up a formal bug reporting system yet.

Rather than use custom path, just check the "manage DCS-side files manually" box. Then shut everything down and redo the patch. the only point of changing the "custom path" was to keep VAICOM from updating the real one. The "manual" checkbox does exactly that.

@BIGNEWY Please pin this important news

If you read other threads you will see that (1) VAICOM is one guy. There is no "department." We hope he is OK but he hasn't showed up on the forums for a long time. And (2), for unknown reasons the supposedly most current version on the website isn't actually the most current version. I suggest you turn off the automatic checking for updates to get rid of the annoying messages.

It always says that when you are not in a mission. Try checking from within a mission that has easy comms off. If you need further conversation I suggest starting a new thread since this is a completely different topic.

I've never heard of anyone successfully restoring the original Jester wheel while otherwise still running ARIO. The early versions of ARIO did not provide an alternative Jester wheel, but still removed the default one. The explanation at the time was that ARIO is not compatible with the default wheel, and apparently this was not just a graphics issue. If you want to disable ARIO altogether the easiest way is to delete or move the DLL.

You don't need a script for that. Just turn on the invulnerable mode! You can bounce off the ground of fly into a hail of SAMs without consequences. But why would you want to do that? LShift-R is plenty fast for me.

That's all correct. But if you leave the F10 Menu Import option turned on the list will grow each time you fly a mission with a new F10 menu. Eventually this is going to slow down VAICOM processing of keywords even if you have not done the "Finish" step. You can delete all of these keywords by resetting your keyword database. (That will delete any customized keywords you have added, however.) I do not recall whether they can be deleted individually.

You have it backward. The command is "Batumi, Select" with a short pause at the comma. But VAICOM will usually accept it the other way as long as you keep the TX key pressed until it has recognized the entire command.

You can also try the "Instant Select" option described in the manual.

I understand the logic of the "rectangle" argument. But consider that if that were all there was to it we would have a very detailed Crimea on our Caucuses map already. As a former Flanker 1 pilot, I really wish we did!

Although the maps are rectangular the detailed areas are not. Have you tried flying over Crimea on the Caucuses map? There isn't anything there.

Turn the Mode switch from NORML to MULTI and they all will be available.

First, the manual suggests that TX6 is intended for future unspecified functionality. But since Hollywood is AWOL it's hard to know what that might mean or if we will ever see the additional functionality. Currently it does open the microphone so that you can give commands to VA or VAICOM without them going over a radio channel. I haven't used it for a while but my recollection is that you can also use it to talk to ground crew. However be warned that TX6 is not enabled in VAICOM's NORML mode for some modules. It isn't clear why not. To make sure you have access you need to switch VAICOM to MULTI mode. Second, the key binding issue is a VA issue, not a VAICOM issue. I can't tell why your joystick is not showing up as bindable. Maybe you can provide more information or take this up on the VoiceAttack forums.