sthompson

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.

This is marked "solved" but the doc folder still does not exist after several DCS updates.

If Salute is the problem then could this be a Tomcat issue? My recollection is that the Tomcat "Salute" command is not the same as the Hornet one in the DCS internal system, and that VAICOM implements the Hornet (Supercarrier) version. So the VAICOM voice command Salute does not work for me in the Tomcat but does work in the Hornet. But I haven't tested this recently and so could be wrong.

Try checking "Disable Automatic Updates" from the VAICOMPRO Config tab to suppress the offers to update.

I checked and am getting the same thing. The weird thing is that Hollywood released a new version 2.5.27.3 when the Apache came out and my installation autoupdated to that version. As an experiment I backed up that installation and reverted to an older version and then asked it to autoupdate, and the resulting file was version 2.5.26 and VAICOMPRO reported that this was up to date. I've backed up my DLL since it seems like it might be hard to restore it in the future should I need to. FWIW, I think the update was quite minor, unless you were an Apache pilot.

Thanks for the tips. I had registered previously for the Discord server. I can see the other channels (e.g. server new, bug reports) but not the one for mission descriptions. It used to be visible but not lately.

Two things. First, I'm trying to figure out how to join the server. I often am online late evenings North America East Coast time, and typically see no one else on the server. I figured that gives me a good chance of figuring things out without bothering anyone. When I tried last night to join the Two Towns mission, I was still waiting for my A-10A to spawn 15 minutes after pushing "FLY" from the briefing. Is that normal? While waiting a message from the server appeared that it would roll over in two hours, so apparently things were not entirely frozen. Eventually I gave up and rebooted DCS to try something else. My ping was reasonable at about 100. Second, in response to a recent inquiry I was told to look at the Discord to find info about the missions. That channel seems to have disappeared from the Discord site, however, and I'm having trouble finding mission info in this thread. A search for "Two Towns" turns up lots of references to the mission, but I didn't find a mission description.

I believe that the tab was created by Hollywood, not ED. My understanding is that any mod can introduce it's own tab and options in the Misc page. SRS, Tacview, and various community modules being other leading examples.

I'd like to try this server. The number one post has a list of missions, but no info about most of them. I recall looking at the top of the thread at one time in the past and finding descriptions of the missions. But now I can't find that. Is there a central place to get info about the missions and other server info. (In addition to the main post at the start of this thread, of course.)

Is it recognizing your module on the PTT page? Have you tried different modules? I do not recall the specific thread that @MAXsennamentioned. Unfortunately it's difficult to debug without source code, and only @Hollywood_315has access to that. Too bad he has been AWOL for months now. To get help here you will need to provide some more information to get us started. Is anything unusual appearing in the VAICOM log (with debug turned on of course, and be sure to show the startup sequence). You might also look for any issues in the DCS log. Also, think hard about what else might have changed. Update to the firewall? Windows update? Sorry I can't be of more help.

What else are you running? I've seen reports of symptoms like this when incompatible software has been installed, like the NS430 module, or DICE.

If you ever installed a release version using the DCS installer then you may have a registry key for the release version. If so, then VAICOM will see that and try to install its files for that version, even if you no longer have that version installed. These won't be used for anything and so this shouldn't affect operation or performance but if it annoys you I recommend finding the registry key and deleting it. I'm at work and forget the exact path in the registry to that key, but it's not hard to find. There is a separate registry key for the open beta version. Don't delete that one! They are both in an Eagle Dynamics section of the registry.

That is not the same problem described in this thread at all, and you've already posted all of this in another thread. It's not productive to spam multiple threads with the same posts. I tried to offer some help in the other thread, but I think you may have uncovered a bug.

Your TX setup looks correct. Listening was resumed as is normal on the second TX1 button press, but VAICOM appeared to then go through its new mission / new module initialization during the first 1/3 second after that, and this caused listening to be suspended after a very short interval, and before you released the button. That's very weird unless you were in the process of starting up the mission. Otherwise, this does seem to be a bug. You might post the VAICOM startup log to ensure that VAICOM is starting up correctly. Sorry I can't be of more help. BTW, I've never had to reinstall VAICOM after a VoiceAttack upgrade, provided the VoiceAttack upgrade is installed to the same folder as previously. UPDATE: Are you running DICE? A thread from more than a year ago about this problem with 2.5.25 was released concluded that DICE incompatibility was causing troubles. The thread starts here: https://forum.dcs.world/topic/273957-listening-suspended/. The discussion of DICE was towards the end of that thread. The earlier parts also discuss possible solutions involving MP settings, but those apparently did not work for some people.

So it looks like VoiceAttack is not recognizing the word "kneeboard" but instead thinks you said "and the board." But you say that it does recognize "kneeboard" under other circumstances? The Dynamic Switching stuff is for MP only. Have you tested in SP? Personally I uncheck everything on the RHS of that screen except Sound Notification, and keep the VOIP Control set to Broadcast Parallel, and have no problems. If VoiceAttack sometimes is recognizing the word but not at other times then I'm wondering if there is some kind of timing or resource issue. Keep in mind that the voice recognition is done by MS Speech Recognition and not by VoiceAttack or VAICOM PRO. So whatever is causing the problem is something that is disrupting the core operating system voice recognition. I had a lot of these problems when I first started using VAICOM and found that getting a better microphone made a huge difference. But I can also believe that if you are pushing your system to the limit there might not be enough CPU cycles or other resources available for voice recognition to work reliably. I'm wondering, for example, if turning your graphics settings way down, or switching to 2D instead of VR would make a difference.

Older versions are available at the bottom of the downloads page here: https://www.vaicompro.com/downloads.html. You might try rolling back to see if it solves the problem, which could provide a clue. Otherwise I suggest you post all of your settings here, including the PTT setup in VoiceAttack. Also, show us what appears in your VoiceAttack log when you try to use TX4, and provide the VAICOM log as well. Turn on debugging in VAICOM first.

Where does that message appear? My sense is that problems with audio interfaces are often an issue with VoiceAttack's setup, and you might have better luck going to their forums. Do you get the error if you start VoiceAttack with an empty profile? Also it's VAICOM, not VIACOM.

You can try the built in SRS integration modes in VAICOM, which will permit you to use the same PTT for SRS and VAICOM. But I find those modes very awkward and I strongly prefer using a separate PTT for SRS. Furthermore, the one button approach is not going to give you full functionality on SRS since you can only bind it to one radio SRS radio. Also, keep in mind that VAICOM's AUTO mode is only available if Easy Communications are turned on, and not all MP servers support Easy Communications. The way I've done it is to have three separate PTT buttons configured for VAICOM corresponding to the TX1-TX3 channels. The same three buttons are configured as radio selection buttons in SRS. I leave the SRS option for radio select to also serve as PTT turned off, and instead bind a separate PTT button for SRS. That way I get full PTT functionality on up to three radios for both VAICOM and SRS out of four buttons, and do not need to rely on easy communications. When using VAICOM I just key one of the three TX buttons and give my voice command. Nothing goes out over SRS. When using SRS I use the same three buttons to select a radio, but then release the button and press the SRS PTT before talking on PTT. That way SRS hears my voice, but VoiceAttack and VAICOM do not. Another option is to leave the SRS option for radio select to also serve as PTT turned on. Then the three TX buttons also are PTT for SRS. This means that those listening to you on SRS will hear your VAICOM voice commands (and vice versa). In some respects this is more realistic, but I prefer to keep the SRS and VAICOM communications separate. BTW, if you also bind TX5 for VAICOM you can use that to talk to ground crew, and it also works for giving your custom VoiceAttack commands without having them go out over the SRS radio.

Not sure what you mean by "AI RIO Profile." VAICOM has its own VoiceAttack profile, which you can embed in or chain to other VoiceAttack profiles if you like. But the VAICOM part is the same no matter which module or seat you are flying. You need to do the Finish step whenever you do something that adds a new voice command to VAICOM. That is, new extension or feature set, or new aliases you create yourself, or new commands you add via the F10 import feature.

See p. 38 of the manual.

That's correct. But also important to launch VoiceAttack before launching DCS after an update or repair.

Do you see the lit up "FINISH" button in your screenshot? That means you haven't properly completed the FINISH step, which is a well documented, annoying, but unavoidable part of the installation process that must be followed whenever you do an update of VAICOM that adds new commands. Read the manual for more details.

Reversals of this sort sometimes occur when you do not hold the TX button down long enough when giving your command. Make sure you hear the acknowledgement beep before releasing the button. The second issue likely is something else. It would help to get screen shots of your PTT page and to see the log file (turn on debugging first) that shows the error. My suspicion is that you do not have the TX set properly for single PTT mode. This may be module dependent.