sthompson

FWIW I was eventually able to complete the mission. The key seemed to be a more effective first pass with the Snakeyes and telling my Wingman to hold position away from the engagement area until I had diminished the AA threats. When I finally got a verbal RTB it was after defeating the SAMs and AAA and most of the trucks. This was on OB. I didn't try the F10 option. In previous attempts I had received a score above 50 and results of 50 prior to returning to base and so I thought I would get the remaining 50 for "results" when I accomplished RTB. But I never got the RTB prompt and did not get a mission complete or additional score or "results."

I'm having trouble completing this mission. I've tried many times, and with some help from Tacview have learned to down most of the convoy, including most of the air defenses, and RTB. Wingman always seems to get shot down before he can help out much. But I'm not getting "Mission Complete" and so am wondering what are the criteria here? Also I find this mission impossible to fly without labels on. The poor lighting under clouds makes the ground units blend into the background. The haze on the F-5 HUD does not help in low contrast situations, and I find myself trying to look around it to see better. Is there a mod that cleans that up? However, overall I'm having fun trying to work through the campaign. My only suggestion for a modification is to go a bit less heavy on the clouds and bad weather. The gloomy feel flying many of these missions makes me long for a virtual sunny day.

It's not a short list and the results so far show how it's hard to interpret a wish list where "all of the above" is an option. You would do better to have a shorter list of higher level items (e.g. "performance improvements," "dynamic campaign") and ask people to pick the one or two that are most wanted.

Correct. "Abort refuel" is for the tankers.

The command is "approaching for refuel" if I recall correctly. Secondly, you can do funky things with VAICOM on the the A-10 radios, such as select an AM recipient on an FM radio, and that may cause a recipient to not respond. Make sure you are using the right radio. And use a "Select" command first to make sure you have selected the right tanker if there is more than one. Simply tuning to a frequency is not sufficient to make sure that a VAICOM radio call goes to the right recipient.

Disabling ARIO in the VAICOM settings will not restore the original wheel. Instead you need to remove the ARIO DLL file from the VAICOM installation. That will disable ARIO voice commands, but not other VAICOM voice commands.

Not to mention bomber formations and flak.

Probably not through VAICOM since as the name implies it is focused on AI Communications and is not a general purpose interface into DCS internals. Possibly you could write a VoiceAttack plugin that interfaces with the DCS Bios project code that would expose cockpit instrumentation and events as VoiceAttack variables. Possibly such a plugin already exists somewhere.

Agreed. The program still works fine for creating and managing kneeboard pages. It's only the features related to changing the display of the kneeboard that seems to be causing people trouble. That's no surprise since ED changed the way the kneeboard works.

Anyone who uses SRS with any of the FC3 modules should already be familiar with how this works! You tune using the SRS overlay, and you can easily program channel presets by creating a small text file. It's well documented in Cribob's videos.

I don't know. I suggest you ask him. BTW, if all you need to do is detect a change in aircraft it's possible to do that through a simple loop command in VoiceAttack that queries the exposed aircraft variable every so often and performs whatever action you want when it changes. I've tested this and it works fine.

But VAICOM PRO uses Win 10 voice recognition to "pick up" what you say to VAICOM. It can't be correct that Win 10 voice recognition works well but VAICOM does not pick up what you say. There are a number of us who voluntarily work with people in the VAICOM forum to resolve issues people have. You are welcome to post some specifics about your experience and we can try to help you through it. The software is not perfect, but it mostly works for me and for many others in the forum. BTW, it isn't clear why you are responding to an old post, but in case you don't know, this thread is mostly inactive, and the main forum for discussing VAICOM is here: https://forums.eagle.ru/forum/329-vaicom/.

@MAXsenna my first reaction to this was to ask myself "Isn't VoiceAttack itself a virtual joystick that can send DX commands?" The answer turns out to be no. But see this thread on how to add virtual joystick functionality. https://forum.voiceattack.com/smf/index.php?topic=463.0 I like the idea! Not sure where you should report progress since this isn't actually a VAICOM topic.

You seem not to answer the question of what VAICOM should do when such an event is raised. Let's say VAICOM has detected the event using that function. What then? Just because a plugin has detected an event does not mean that your profile commands can detect it. Some kind of further communication or action by the plugin is needed to achieve your automation goal. VAICOM has to act on the event in order for the detection to be useful. How should it act? Your comments make me wonder whether you understand how VAICOM works. VoiceAttack knows nothing about DCS internals and so has no variables that indicate the mission or aircraft except those created by VAICOM. VAICOM is the code that obtains (and sometimes changes) the internal state of DCS. (It does this through two-way network communication with lua code that VAICOM adds to DCS when VAICOM starts up. This is why you may need to start VAICOM before you start DCS.) So VAICOM has no need to detect the change in a VA variable indicating mission start or change of unit because any such variable change would have been made by the VAICOM plugin itself. There is no point in adding to VAICOM code asking VA to detect a change that VAICOM made itself. It would be far more efficient for VAICOM to just take appropriate action when changing the variable. As a consequence I see no role for the function you mention in automating something. The relevant question for achieving automation is not how to detect the change (since VAICOM detects it already) but rather what action should VAICOM take when it detects a change in mission and/or unit within DCS? It can change a VA variable, which you could detect through execution of a VA command in your profile. It does that already with respect to the aircraft and you can easily add VA commands to your profile to detect such an event and act upon it. (It also exposes the current map, btw.) Or VAICOM could use the EXECUTE method (see VA plugin documentation) to execute a command in your profile. But which one? And what if it does not exist in the profile? I have some concerns that further automation along these lines could add significant overhead to continuously running code, thus possibly slowing down other functions. All to avoid manually or by voice executing a particular command once at the start of each mission. I'm not sure it's worth it except to prove that it is possible.

I guess I still don't know what VAICOM would do when detecting a switch of aircraft at mission start? What do you have in mind? "trigger from VAICOM" is kind of vague. Yes, I understand that you want to "auto change the profile." But how exactly would that happen, working within the limitations of VoiceAttack? As far as I know VAICOM does not "trigger" any VoiceAttack functions at all at present but rather responds to plugin invocations initiated by the user. If you have a coding suggestion you might send it to Hollywood.

VAICOM could use that to detect when the mission or active module changes. But what would you have it do then? I really don't understand what you are asking for. What do you mean by a VAICOM "event?" Aircraft type is already an exposed variable. What do you want VAICOM to do when this changes at the start of a mission?

As far as I know the only "triggers" that VoiceAttack detects are voice commands, key presses, button presses, mouse events, and change in the active window. So I think the short answer is no, because VoiceAttack does not support command triggers initiated by plugins. Since VAICOMPRO clearly detects mission loading I'm sure that @Hollywood_315 could implement an exposed variable with the mission name, but that isn't available now. With such a variable exposed you could detect a switch of mission name upon a TX press pretty easily. It still would not be fully automatic since the check for a change would be triggered in response to a TX press (or voice command, or keypress, etc.). Looking through the VA documentation (which is very long and so I may have missed something) I do not see any functionality to have VA do something in response to a change in a variable. You might go to the VA website to ask about this. If VA had an option in the command dialog to respond to a trigger along the lines of "Upon change in variable value" similar to "Upon key press" then it would be fairly simple to program, once the relevant variable became exposed. The VA people are receptive to ideas that would improve the software so I would not hesitate to ask over there.

Use the Multi setting on the VAICOM PTT tab if you want separate intercom. But you don't really need it for the F-86. You can talk to ground crew using the radio.

Make sure the roll axis is enabled in the TrackIR software and you have suitable curves in TrackIR. If that does not do it check the TrackIR bindings in DCS too.

When 2.7 was released they announced that the new weather engine had no snow, but that snow would be added later.

Somehow you have listening turned on. This can happen if you are using hot mic, for example in the Tomcat.

Keep in mind that the repair will also uninstall any mods in the main DCS directories.

It should. However the repair function has an option to remove files that it finds that are not "official." I believe if you use that it will remove all of the added liveries for you. That might be a better way to go than deleting the liveries yourself.

The first time I flew Mission 11 a Mig-21 engaged. Overlord was talking all the time but never gave intel on the close in bogey, despite reporting repeatedly on pop-up groups 60-80 miles away. The Bogey came in very high so I missed it on radar, then snuck in behind my flight and took us out one at a time. I checked six only to see number two go down and a missile launched at my rear quarter taking me down. The second time I flew the mission the Hawks took out any MiG that came close and the others turned tail. None got close to the helos. So my flight also went RTB without engaging anything. Mission Complete! So some level of randomness in the experience.

I finally finished it too. The key seemed to be to fly a bit higher on approach so that my flight did not lawndart into hills, then deliver a lot more ordinance quickly than I had been trying earlier. That is, all 5 bombs on one target first pass, then all rocket pods at once on the second. Also a lot of jinking to keep the remaining ZSU-23's hit percentage low. I even managed to get back to base. A lot of fun, but I'm glad to move on. I see that the next mission has nicer weather, which will be welcome after all of that flying under low clouds.