sthompson

From page 23 of the manual: Prerequisites For working with Multiplayer, on the MP page the ‘Use with Multiplayer’ setting must be enabled. On the MP server, the setting Allow Player Export must be enabled. VAICOM cannot get all of the required info about game status if it's disabled. I'm not familiar with the specifics but I believe this is a limitation of DCS, which blocks access to certain data when export is disabled.

I'm pretty sure that "link to radio power" just means that you will only hear chatter when the radio in an active module is turned on. It has nothing to do with volume. And Chatter volume is controlled through VoiceAttack, not DCS. Try turning up the volume for your VoiceAttack app using the Windows volume mixer. Of course that probably will increase volume for all VoiceAttack sounds, including VAICOM's audio cues if you are using them. There are API commands for turning up the chatter volume but I suspect they just duplicate the function of the Vol knob on the PTT page and so probably won't help. In the end, I suspect that the problem is that the chatter audio is intentionally low volume so as to not distract too much from your own comms, especially when wearing headphones.

You can run your own server for this. The server program is included with SRS and no installation necessary. It includes test frequencies where you can transmit and it will echo back what was received.

No. And I redid speech training to see if it would help. No luck there.

These are obviously different VAICOM commands, both important if you fly off carriers. However for me VoiceAttack consistently interprets both as "select" with very high confidence. I guess because they have the same consonant sounds but different vowel sounds. I've tried training and recorded my pronunciation of each in Windows Speech recognition but the problem persists. Any ideas? What would be a good alias for Salute? Launch is used for something else.

If you are having the problem and you reboot but do not start VoiceAttack or DCS then you sometimes still have the problem? If so, the problem can't have anything to do with VoiceAttack or VAICOMPRO. If Virpil's own software indicates something is odd then it sounds like a hardware problem, or it could be a conflict with some other software. But can't be a conflict with VA or VCP if they haven't been started following a reboot. In any event, I would stop using VoiceAttack for a while. Do a repair of DCS and delete export.lua so that no third party code is running inside DCS. See if you are still having problems. If so it isn't VA or VCP causing it.

This is due to recent changes in VoiceAttack that moved its install location. The installer for VAICOM will need to be changed to match but that hasn't happened yet. The fix is to do a manual install of the plugin, which is really nothing more than unzipping a file to the VoiceAttack APPS folder.

I couldn't view the video in the forum but could download it. It shows a Tacview replay of an F-16 evading a rear aspect AIM-120C by rapidly rolling continuously while flying straight. Not a barrel roll as the longitudinal axis vector only rolls a little bit during the rolling maneuvers. The missile just flies right by.

I see what you mean now. The problem occurs if you did not have plugin support already enabled prior to starting VoiceAttack to configure it as on page 7. If not then the plugin doesn't get run until you restart VoiceAttack, but you need it to run to create the profile. So there should be another "restart VoiceAttack" at the end of the Configure VoiceAttack Options" section to make sure that the plugin gets run at least once before you try to import the profile. I don't have any conflicts with SRS. What are your symptoms there? FWIW, in my export.lua file (in Saved Games\dcs.openbeta\Scripts) the lines for initializing SRS come last, after the lines initializing TacView and Vaicom. Possibly you have those reversed if you installed SRS first. You might try switching them to see if it fixes your issue.

I just checked the manual and I see no such instructions. According to the quick setup guide the initial steps are: Make sure VoiceAttack runs as administrator and plugin support is enabled. Download the plugin installation file and unzip it to the apps directory. Launch VoiceAttack and configure VoiceAttack settings. Check DCS options. "Next, import the profile" Assign HOTAS buttons in the profile So you definitely need to restart VoiceAttack after installing the plugin but before importing the profile. In any event, hope you have it sorted now.

VAICOM PRO is primarily about voice communications with the AI. However it now has a kneeboard feature that (among many other things) let's you dictate notes to a page. No typing required. Requires VoiceAttack.

I hate to say it but RTFM. The "Quick Setup Guide" describes the next steps. Other files are created only after you launch VoiceAttack and configure the VoiceAttack settings. In particular, once you have VoiceAttack running with the VAICOM PRO DLL loaded (which requires you to first enable plugins in VoiceAttack) then the plugin will create the other files, including the profile that you need to import.

I finished the campaign this week. Just came here today to say how much I enjoyed flying it. I'll look forward to your next one. Looks like I'll need to learn the MiG-21!

@BIGNEWY no good deed goes unpunished. Despite the griping I read all the time about ED's lack of transparency, personally I think you are doing a great job. In fact ED is far more transparent about development progress than any other software company I deal with or monitor. Looking forward to more great things in the future. DCS has not disappointed so far.

I don't use Steam, but understand that others who have bought the Steam version of VoiceAttack have used it successfully to run VAICOM PRO. The key is to do a manual install (using the ZIP file download) of VAICOM PRO (not VoiceAttack) into the location where Steam put VoiceAttack. That might have been less clear in the earlier posts. So you shouldn't have to repurchase VoiceAttack.

I tried again last night and found this time that after I pushed south from WPT 2 I did get additional instructions to attack the truck convoy. I had to go further away from WPT 2 than I would normally do during an orbit. So I think the issue is that the voice over to orbit and await further instructions if followed literally does not actually trigger anything. Also, it became clear in completing the mission that getting a message that the column has been stopped does not mean that mission objectives are met. (To avoid posting a spoiler I won't say more.)

It still works for managing kneeboard pages but not for changing the size/placement of the kneeboard. To get it working try deleting the *.config file in the directory where it is installed. That might get it running again, and then try updating. Unfortunately the program appears to no longer be supported and the latest version does not appear to be linked from its website. Nevertheless I was able to update it some time ago. Do not recall the details for sure but I think it was using the *.config method mentioned.

I've tried mission 21 a few times now. I fly to waypoint 2 and JTAC tells me to orbit and standby. I orbit the WPT for upwards of 15 minutes, getting bored but enjoying the scenery. There is never any further instruction to push. When I'm sufficiently bored I push south anyhow, and find the column. After some A2G action I get a voice prompt that the column has been stopped. I RTB at Krymsk as instructed in the briefing, but do not get mission complete.

Turn on VAICOM debugging to see if you get any better information in the VA window. Try moving your rotary switch to NRML to see if that makes a difference. Also enable the keyboard button 1 on the press and release definitions and try using that instead of your joystick. (That should verify that the issue is not related to something in your joystick setup outside of VA.) If none of those makes the problem go away then I'm out of ideas. Everything you've shown so far seems correctly configured. I doubt if it's a corrupt profile since the press and release commands seem correctly set up. The actual "listening" on/off commands are being executed by the plugin.

All of that looks correct to me. Here are a few suggestions: (1) Test when DCS is not running so that no module or mission is loaded. If you still have a problem then it has something to do with module or mission interaction, although this seems unlikely. (2) Test with the rotary switch on the PTT tab set to NRML. Possibly the use of INV is related to the issue. (3) Bring up the "Edit a command" window in your profile for command "Transmit TX1 Release." Then click on the box with three dots to the right of the "when I press button" line and provide a screenshot of the dialog that opens so that we can see that you have the button correctly configured to only activate on button release.

No that is not what you would expect. The "release" on the first press should be for TX1, not TX2. This implies that somehow you have the button assignment for TX1 release not configured properly, and possibly have a problem with TX2 as well. Furthermore the second press shows "listening resumed" just as it should but with no "listening suspended" afterwards, which is different from what you described in your original post. It would be helpful if you could post a screenshot of your VA window trying these keypresses when not in a mission since behavior can be module dependent. Say something in each case while the button is held so that we can get verification that VA is listening (or not). Also, since VA can be configured to have the more recent messages at either the top or the bottom, please indicate which of those options you have selected when you post your screenshot. Also, what is the setting of the rotary switch on the PTT tab of the VAICOM widget? This can matter since PTT behavior is somewhat module dependent. If all else fails you may need to load a clean VAICOM profile and remap the TX keys per instructions in the VAICOM manual.

Since the menus for these should be constant across missions you could probably create your own VA commands to implement these features via button presses.

I agree with this. I'm in a similar situation and lately have mostly been flying the F-5, which has a nice campaign (Black Sea Resolve) that you can tackle one mission at a time, as well as MP activity on the Cold War server. Also consider the MiG-15 if you learn the F-86 because they are closely matched and there is a good MP server (Korea 1952) hosting both, as well as a decent single-player campaign. I'll probably get skewered for suggesting it, but also consider the FC-3 suite of planes. The F-15, MiG-29, and Su-27/33 are all fast jets with good weapons. The SU-33 is carrier-capable. And once you learn one of the FC-3 planes it's not too hard to learn the others because they do not have clickable cockpits and similar control bindings. Their simplifications could be an asset if you are only flying a few hours per week.

I could be wrong but I do not believe those are supported at present. You will need to go through the menus. You can always do that using "Chief, options, take <x> etc."

Is the throttle axis possibly reversed?