sthompson

That's only a problem if you insist on mapping different PTT buttons per aircraft. And if you must do that then there are workarounds via more sophisticated programming within VoiceAttack. Many of us have been using VAICOM alongside SRS for years without any problems to enable both voice chat and voice interaction with the AI. ED has some catching up to do. I'm encouraged, however, by a Wags video posted today that closes with a hint that the new DCS voice chat will (perhaps not right away) enable a variety of user-created options.

You can do that already with VAICOM PRO Community Edition.

Glad to hear that this is working for you again. But for the record, that is the VAICOMPRO log, not the VoiceAttack log. Also, it would be helpful for the future if you could report back what the fix was.

That happens to me as well. It's caused by some switches on my throttle that turn a particular button on continuously until I move the switch to a different setting, at which point another button goes on continuously. Evidently VA polls the stick immediately and finds a button pressed and assumes that's the one you want. Fortunately reset clears it, at which point you can press the correct button. So I don't think this is the source of your problem since everything is working fine for me event though I experience the same thing when I assign buttons within VA. But what's happening in your VA log? There may be some clues there if you have enabled VAICOM debugging. (I leave VAICOM debugging on all of the time. Doesn't seem to add noticeable overhead.)

It might help to see the VA log (with VAICOM debugging turned on first) when this happens. I don't have Virpil hardware and so cannot provide detailed advice. However if I were having this issue with my VKB hardware I would first go into the stick configuration software and run some button tests to make sure the press and release are working as expected. It's possible, for example, that your stick is sending a pulse when you press and hold, instead of holding the virtual button down. It also occurred to me that this might be related to the SRS/VOIP integration settings in VAICOM PRO, some of which require special setup of the TX commands. You might look into that if you have used SRS/VOIP integration. I've found it to be very unnatural and so use a completely different approach from the one in the VAICOM PRO manual. Finally, are you sure you have the TX programmed correctly? Consider activating a clean VAICOM PRO profile, then export the TX section to its own profile. Then import and switch to that profile (which will have only the TX commands) and edit it until it's correct, and export it as a new VAP file. Finally, switch to your regular VAICOM PRO profile and import the edited profile for your TX commands. One last thought: If the switch in GUID you experienced was not related to a hardware change (e.g. replugging in the stick after having it disconnected from its usual USB port) then you might suspect a hardware problem, such as a loose connection somewhere, as the ultimate culprit. Personally, I never unplug my flight sim peripherals to avoid such problems.

Most likely VoiceAttack is still looking for buttons under the old GUID and not seeing button presses associated with the new one. Go into VoiceAttack options (not your VAICOM PRO profile), General tab, and click on "Joystick Options." "Unassign" the old joysticks (the ones with the old GUID) and then enable new ones. Push OK. Then OK again. You may also need to update the button settings on your TX commands in the VAICOM PRO profile. I went through this drill just recently when I got a new throttle.

If you use the "fix registry" option then you won't need it checked any more.

And there's the rub. You are not buying digital aircraft, but rather a license to use their digital aircraft under their terms. This is spelled out pretty clearly near the top of the END USER LICENSE AGREEMENT that you have to agree to when you license a module. Near the top it reads 2.1 The Program is licensed for your use. This Licence confers no title or ownership in the Program ... 2.2 All title, ownership rights and intellectual property rights in and to the Program ... are owned by Eagle Dynamics SA, affiliates of Eagle Dynamics SA or Eagle Dynamics SA's licensors. So you don't really own anything when you buy a module except the right to install and use it. However it's not true that they have the right to take away your use at any time without notice or reason. The EULA spells out when they can deny use or take away your license. See https://www.digitalcombatsimulator.com/en/support/license/ if you want to read the whole thing. It's blessedly short compared to many online licenses.

https://forum.dcs.world/forum/42-guides-amp-tutorials/

Use the custom path option in VAICOM along with the "fix registry" check box to point to the new DCS root directory, and then VAICOM will do the unpleasant registry editing for you. Once the registry is fixed you will not need to use the custom path anymore, but there is no harm in doing so. That's all you need to do. I see no reason to not use the latest version of VAICOM, and you could upgrade that either before or after moving DCS.

A more definitive test would be to see whether you have the problem when this is the only mod. If not then there is some kind of interaction.

This is very helpful. Thanks. I suspect my problem was in trying to keep up with the AI who just seem to zoom upward. I probably had too much pitch. Gear and flaps were definitely both up.

This raises another question I've had. My understanding is that the prop lever adjusts the RPM setting of the prop governor, and the governor then adjusts the prop pitch to maintain the RPMs. I assume this means it lowers the pitch when the prop RPMs are below the set level, and increases it in the opposite case essentially equivalent to shifting gears in a car to keep RPMs roughly constant as speed changes. This raises a question my mind about how to manage prop RPM and throttle for maximum acceleration in level flight or while climbing. I've found it hard to maintain speeds above 150 MPH in a climb, let alone accelerate to a higher IAS.

Very nice video Thanks for making this. I have a couple of related questions: Why do you wait until just before takeoff to turn on the generator? What's the point of opening the radiators during warm up? Wouldn't the engine warm up faster with them on auto? What are the recommended settings for climb out or descent or diving? (In the Blue Nosed Bastards of Bodney campaign I find that when the AI starts to climb from sea level to 20k I can't keep up.) You got into combat settings a bit in the discussion of Military and War Emergency Power, but I'm not sure I understand fully engine management during combat. Do you keep RPMs at 2700?

VAICOM version 1 was a free product that relied exclusively on VoiceAttack scripting to emulate keystroke operation of the DCS comms menus. (It also relied on certain mods to DCS itself.) VAICOM 2 (also called VAICOM PRO) was a commercial product that replaced the VoiceAttack scripting with a plugin module for VoiceAttack. That version eliminated keystroke emulation and instead used direct communication between the plugin and the internal DCS code. This change vastly simplified the interface between VAICOM and VoiceAttack while greatly expanding the functionality of VAICOM. For example it added extensions that allowed one to communicate with Jester in the F-14 using voice commands. Last year VAICOM PRO stopped working upon the release of DCS version 2.8. Rather than update it, the developer released the code to the community for further development. Volunteers took up the task of updating the code. The Community Edition resulted from that, and is the current version. So it is similar to the commercial version (which is no longer available or supported) but is a free community supported program that works with the latest version of DCS. If you want the latest you should go the the VAICOM PRO Community Edition channel on Discord, or go to the Github page directly. Do not try to use VAICOMPRO.com, which is no longer active.

That is not the recommended method for invoking VAICOM. I would look carefully at your TX commands in the VAICOM profile of VoiceAttack. Normally you would be programming these to respond to the HOTAS buttons directly without relying on keystroke emulation. You might want to review the PTT configuration section of the VAICOM manual.

The menu never comes up in that example. Your description in the OP said that it used to come up and then go away automatically. That's not what happened in the video. Thinking more about your OP, when you write "key the radio Mic" I assume you mean you key one of the TX functions. The same key should not be bound to any DCS functions. I suspect you have the same key bound to a TX and to a DCS function that calls up the menu. If so, you should delete the DCS binding. Note the instruction in the VAICOM PRO manual that says "make sure the keys/buttons used with VAICOM PRO PTT are not mapped to HOTAS MIC or Comms Menu functions in DCS config." The manual notes: "The functionality of the plugin is not impacted if these [DCS mappings] are not cleared but it’s highly recommended to clear them to avoid any menus being shown when pressing these buttons, which would spoil an otherwise menu-free experience." You might also check whether you have "Disable Menus" checked on the Preferences tab. I've never used that, but it might help with your situation. Possibly a setting got changed when you moved to the Community version of VAICOM PRO.

Except that the post currently marked as "the" solution is about something else entirely.

Minor gripe. Why is this post marked as the "solution" to this entire thread, which covers many different topics other than the one discussed in this post? Can it be unmarked? @BIGNEWY

I don't understand this. The aliases in the VAICOM PRO profile were all things that would be updated automatically via the FINISH step in previous versions with no need to update the profile. Why should we need a new VAP file if aliases can be updated via the FINISH step? Replacing the entire profile means losing more than just your custom commands since the profile includes other things such as the TX key mappings and probably other settings I'm forgetting. I think it's a bad trend if profiles will need to be replaced frequently when VAICOM is updated.

It never worked the way you described in my experience, and I've been using it since the beginning. If you opened the comm menu you could select an option using the "take" command, but you would need to push the appropriate TX button for it even to start listening. I suppose if you had the mic button and the TX function assigned to the same key then it might work the way you describe. In any event, if you open the comm menu it will not go away unless you select one of the menu options using the mouse, a function key, or the VAICOM "take" command. The current version is the same as the paid one in this respect.

If you look more closely at the list you will see ATC from the Persian Gulf map, the Normandy map, Marianas, and others.

After completing the excellent "Desert Thunder" campaign I've been trying the Thunder Strike Campaign included with the JF-17 module. I'm pretty disappointed to find almost no discussion of this here, since I'm having considerable difficulty with it. First, the "cinematic" introductory sequences result in underground views for the most part, and are thus pretty useless. Second, the "Reconnaisance" mission 4 seems to have multiple issues. In part because of the cinematic intro, one must get the plane started and down to the other end of the field in less than 5 minutes, and then you need to stay in burner most of the way to WP4 in order to not be too late. Furthermore, some of the reconnaisance targets are obscured by clouds. And I can't figure out any way to complete this mission without getting shot down by either a SAM or the Mirages. Does anyone have any tips? Has this campaign been abandoned?

You guys are dreaming. They can't even get the track system to work reliably at present, let alone let you add a second flyable plane. That said, it would be cool. I recall being able to race a "ghost" of myself in one of the car racing games.

Try mapping Pause. That works for me, although the mission then starts Paused and you need to push it again to get things going.