sthompson

FWIW, in one of his videos Wags says that he uses Saturation 50% and Curve 30 for both X and Y TDC controls in the Hornet.

You may be confused if you used the ministick assigned to the TDC. You do that assignment through the Axis Options page. But the depress function is not on the same page. It's definitely in Options.

I'm not clear on what you are asking about in #1. VoiceAttack and VAICOM PRO allow you to speak to the computer. They do not speak to you. Any English you hear in a YouTube video was spoken by the live player making the recording or is part of DCS itself. If your goal #1 is to learn whether VoiceAttack will recognize your spoken English with your accent. You can test that using the trial version of VoiceAttack. Likewise you can test how well VoiceAttack will work in your noisy environment using the free trial version. You don't need VAICOM PRO at all to test those things as they are purely functions of VoiceAttack that you can test in the free trial version of VoiceAttack. For what it's worth, I have found that even in a relatively quiet environment, VoiceAttack needs a decent headset microphone to work reliably. When I switch to the microphone built into my webcam the error rate goes up significantly. Regarding your suggestions that VoiceAttack and VAICOM PRO should offer money back if not satisfied, keep in mind that credit card processors keep a portion of proceeds of a transaction, so you would only get back a part of your $10, or else VoiceAttack would have to bear the actual cost of your free trial. The price likely would have to be higher as a result.

Why would you want to bind it to a switch? I just use the keyboard. This is not something you are going to be doing frequently while flying. I often fly in DCS using VAICOMP PRO without opening that window at all.

Agreed. Especially since the module descriptions are often different and sometimes inconsistent between the two locations (e.g. early access status mentioned in one place and not the other).

That would be "padlock mode." I haven't used it for a long time and I don't know if the F-5 supports it. Not all modules do. In the old days when I played Flanker 1.0 I used this all the time and found that an essential complement to it was the "mini-Hud." The Mini-HUD showed you the view direction towards the nose of your plane so you could maintain spatial orientation even while looking over your shoulder at the enemy creeping up from behind. Without it padlock mode is much more challenging. There is still a mini-HUD option in DCS if I recall correctly, but it doesn't work in most modules. Unfortunate in my view, since padlock mode would permit one to overcome some of the view limitations of DCS.

I would hope for a solution that does not require a specific kind of HOTAS. The proposed fix would not work on my CH gear.

You might give some more specific information about what you mean by "interprets the word correctly" and "doesn't seem to have it in its list for me." Those could mean more than one thing. But here are a few tips that may or may not be related to your problem: Make sure on the MP tab of the VAICOM PRO configuration widget that you have VOIP Control set to "Dynamic Switching" and that the "Use Switch Command" box is checked. Also, "SRS Integration" and/or "Voice Chat Integration" should be checked, depending on which you are using. Finally, if using SRS you need the SRS option "Allow VAICOM TX Inhibit" set to ON.

Since VAICOM may need to modify DCS lua files upon startup it's best if you start VAICOM PRO before you start DCS. this is especially important after either updates.

That isn't entirely true. Depends on the module and radio. For example, in FC3 modules the radios can be tuned, volume set, etc. using the overlay. And on servers that have enabled "expansion radios" those are also tuned using the overlay. But if the radio is tuneable using cockpit controls then you can't tune it using the overlay. But you can't tune an SRS radio by any means if it is listed as "unknown." If the "game" light isn't coming on when you are in game, or if it is on and you are in the cockpit with the power on and the radio turned on, but the overlay still says "unknown" for every radio, then there is a problem with your installation and you probably want to post in the SRS support channels. (Primary support is on Discord but Cribob monitors the original SRS thread on this forum too.)

I experienced this with older versions as well. I'm surprised to hear that it was working before the last update. I recall doing a long mission in the Mig-15 and in the track my engines never started because the "turn on the ground power" command did not replay. The unreliability of the track replay system is disappointing because in the predecessors to DCS it worked very well. I remember using it with Flanker 1.0.

I had this issue start recently after an update. I finally solved it by looking at all of the settings. There is one called Enable FM Radio Tone. It had been selected somehow. I deselected and the problem went away.

VAICOM PRO edits DCS lua code, but a DCS update may undo some of the VAICOM edits by replacing the edited files. Therefore you need to (a) close both DCS and VoiceAttack/VAICOM, (b) repair DCS, then © run VAICOM PRO, then (d) restart DCS, IN THAT ORDER, every time DCS updates. You should not have to do it after a VAICOM PRO update, and it may not be necessary after every DCS update (depending on which DCS files were updated). However if you are having troubles then those 4 steps should be your first attempt at a fix. Of course its possible that a DCS update will break VAICOM PRO due to changes in the underlying lua code structure. If that happens then the only fix is to wait for Hollywood to make matching updates for VAICOM PRO.

In post https://forums.eagle.ru/showpost.php?p=4361653&postcount=5520 a user indicates that the Yak-52 module is not being recognized by VAICOMPRO. I tested this today and can confirm that. The Module name does not show up in the VP Control PTT page. This is with version 2.5.20.0 running on openbeta 2.5.6.

I've written about this before but I do not think I ever got a good answer and so I'm trying again. The VAICOM PRO manual description of TX5 (Intercom) and TX6 (Aux) seems to indicate they should always be available. But I've been doing some testing and finding they are not available in PTT NORMAL mode in many modules and not available at all in others. I don't understand why this is the case. I'm wondering if this is specific to my setup, indicating some kind of problem, or is generally true for others. Am I misinterpreting the manual? Perhaps Hollywood could weigh in. Not really a show stopper, but the inconsistency has caused some confusion for me in the past. Here are results of some testing I did tonight: TX5 and TX6 are available in INV and MULTI but not in SNGL or NORM in these modules: KA-50, Mi-8, BF-109, C-101, F-5E, F-86, FW-190 Dora, L-39, MiG-15, P-51, Spitfire, TF-51, MiG-21, and SA342 Gazelle. TX5 and TX6 are not available in any PTT mode for these: CE-2, FW-190 A8 (which VP seems to identify as the Dora), and MiG-19. Related notes from my testing: (1) The CE-2 does not seem to have any radios available in PTT NORMAL mode. (2) The Yak-52 does not seem to be detected by VP at all right now. It's possible I'm misreading the manual. If so I would appreciate a more complete description of the various PTT modes, perhaps with some examples. The description of INV mode is especially confusing.

VAICOMPRO does not merely copy replacement files. Instead it edits the existing ones using lua code in those Export files. The final result is therefore not the same as the files in the export folder. Basically it automates the process that is described in the manual under "Managing DCS-side (lua) files manually." It's on p. 42 of the latest version of the manual. Also, your posts are not providing complete paths so I can't tell if the files you are mentioning are in the Saved Games directory tree or in the main DCS directory tree. There are Scripts folders in both places.

Since it appears that Batumi is recognized in your test, I'm wondering if the issue is that you have not selected Batumi as the recipient. This is not automatic unless you have "Instant Select" turned on. Also, is your radio powered up?

Look again. It's there. See attached.

"Request Refuel" is already in the dictionary as another command. It's used for ground crew refueling.

Please do fix this was very frustrated I could not advance and finally resorted to the auto success option.

VAICOMPRO.EXE wants to start VoiceAttack as administrator. I have never run VoiceAttack as administrator and have found that it works just fine running as an ordinary user. I think this works because I gave myself full control permissions on the VAICOMPRO folder. In any event this means I don't have to deal with entering an admin password every time I start VoiceAttack. It would be nice if VAICOMPRO.EXE had an option to start voiceattack as an ordinary user.

The answer to your question #4 is no. You cannot access the Jester wheel if ARIO is installed. Even disabling ARIO via the VAICOM Pro control panel does not re-enable the wheel. The only way to get the wheel back is to delete the ARIO DLL file from the VAICOMPRO subfolders.

I'm pretty sure that with Easy Comms on the default radio tuning is to the nearest field at mission start. It does not automatically switch to the nearest field at the time of a radio call. So just flying near the boat will not retune the radio. To be sure you are tuned to the correct recipient you need to tune manually, or use the radio menu, or (easiest) using the VAICOM Select command.

But that doesn't seem to be working. This thread keeps having new content added, defeating the purpose of having a sub-forum.

That's only true for Open Beta. Working fine on stable. (Well, at least as well as they ever did.) I don't understand why more servers don't revert to stable under the circumstances.