sthompson

The new video includes multiple sighting of the A-10C II. You can tell by looking for the banged up nose, visible at 1:23, and for many shots where it is clear that the bird does not have the pave penny pod.

I think you might be able to set this up as follows by programming the following into your profile: 1. Define the "radio" buttons to set a variable indicating which radio has been selected but do NOT have them invoke VAICOM or start listening. 2. Define your PTT button with two different functions (one for press and one for release) to read that variable and then conditionally invoke one of the VAICOM API commands that simulate a TX press or release. See the API section of the manual for details. For example, you could program buttons 1 and 2 to "select" radio 1 or 2 (respectively) by setting a variable equal to the string "TX1" or "TX2" (respectively), but do nothing else. Then define a button 3 press to send ptt.hotkey.TX1.press or ptt.hotkey.TX2.press to VAICOM depending on the setting of the variable. You would also define a button 3 release function to send ptt.hotkey.TX1.release or ptt.hotkey.TX2.release. Then button 1 or 2 would select TX1 or TX2 but the TX function would not be invoked until you pressed button 3. You presumably would also disable all of the currently defined TX buttons. As Weegie said, the VAICOM TX functions start and end VA listening so you should NOT define a push-to-talk button in VA itself. Caveat: I haven't tried this myself. Tried it and it worked.

Known issue. Same problem in the MiG-15 for me. I'm surprised to hear that someone else does not have the problem. Are you sure about that?

But VAICOM will turn off the mic upon release of the PTT if (1) you have AIRIO, and (2) are flying the Tomcat, and (3) the pilot ICS mic switch is set to Cold Mic. That's because REL HOT and the listening mode are reset to match the hot mic setting in the pilot cockpit in those circumstances. If this applies to your setting then REL HOT will be turned off dynamically every time you give a command to VAICOM, and that will prevent VA from hearing your commands from the MINE profile. To avoid that, keep the ICS mic switch set to hot mic. This isn't necessarily a problem, because if you prefer hot mic for your own commands you probably want it for Jester too. But keep in mind that VAICOM and Jester in particular will be listening always if you take that approach, and at least in my environment that means a lot of annoying random beeping when VAICOM thinks it heard part of a command, and occasionally Jester does something I didn't command. Personally I prefer Weegie's approach of requiring a PTT for my own commands, and like him I use TX6.

It was never here. This is the thread for the older, no longer supported version of VAICOM. For version 2 and above look here: https://forums.eagle.ru/forum/329-vaicom/

I don't know if you can move just the mission files. However you can move the entire "Saved Games" folder to a new location. (Use Windows drag and drop while logged in as the corresponding user.) DCS will then find the mission files at the new location, along with anything else it looks for in Saved Games.

You might want to check out VAICOM (see the Input/Output forum) which will let you avoid using the radio menus completely. I routinely call the boat using my voice from further out using this tool. It's far more immersive.

Wish list item for a modification to this feature: It would be nice if VAICOM respected the hot mic switch in the RIO seat when I am sitting there. I'd really like it to stop listening all the time when I'm the RIO. Right now the hot mic function seems to follow the switch setting in the pilot seat only, and there does not appear to be a way to force it off from the RIO seat. I find that when I'm RIO I'm getting constant beeps when VA thinks it has recognized something.

I've had similar issues in the Mig-15 due to a spiky throttle. The Mig doesn't like to have the throttle go instantly to idle and then back to max (or vice versa) due to a controller malfunction. Cleaning the pots in my throttle solved the problem. I'm speculating but am wondering if something similar could happen in the A-10C.

Well, as I said before, you can make Intercom available in the F-5 over TX5 using the current version of VAICOM by simply rotating VAICOM's PTT dial to MULTI. And if you already have TX5 bound as an SRS key too then you can also talk to the ground crew using TX6 with the dial in that position.

Obvious perhaps, but VAICOM is going to say that AIRIO commands are not available unless it detects that you are in the Tomcat, which it obviously didn't do in the first part of your log file. Assuming you were on Hoggit and in the Tomcat when you gave those commands, the focus should be on why it isn't recognizing that you were in the Tomcat when you gave the first set of commands. You might report on whether there are any known differences in server settings across those MP servers. Seems like you only have the problem on Hoggit.

I think the idea is that every time you push the PTT then VA would (1) initialize a variable with the current module name if it is not already initialized. (2) Compare the current module name to the saved variable. (3) If they are different then update the saved variable and take other actions (which could be loading a new profile). The overhead for that would be pretty low since only (1) and (2) would be executed on every press of the PTT. But since the VAICOM plugin is probably doing those things already, the proposed modification of the plugin is probably slightly more efficient. But wouldn't it be easiest to just create a new voice command to do these things when requested, rather than on every PTT push? The advantage of making this automatic seem pretty low compared to just pushing TX6 and saying "Module Initialize" or the like, as needed, to invoke code that loads an appropriate profile for the current module. Personally, I sometimes go for days flying the same bird and so would prefer that the checking be done on demand rather than have the overhead of monitoring. The "Module Initialize" command could be in a separate profile that you include within each of your module specific profiles so that it only has to be updated once when you need to modify your module switching code (e.g. after installing a new module).

I recently started flying the Hog. I've been going through training on the old version but the issue/question reported here seems to be common to both the A-10C and the A-10C II Tank Killer modules. I've been flying with Easy Communications OFF but with "Select Tunes Radio" and "Instant Select" both turned ON. In one mission I wanted to use radio 3 to communicate with Batumi on 40.400 MHz. So I manually tuned that radio to 40.400 and called Batumi for taxi permission. No response. However if I then gave the command "Batumi, Select" and then called for taxi permission it worked fine. At first I thought this was a failure of Instant Select to select Batumi as the recipient. Upon further investigation I realized that the problem is actually with "Select Tunes Radio" together with my improper use of the radio. The Select command was causing radio 3 to tune to 40.400 MHz AM. This is a bug because that radio is an FM only radio and so such tuning should be impossible. Batumi ATC should not be reachable on that radio, and if you try to reach it using the Hog's Mic switch aft command Batumi does not respond. Or perhaps I should call this a feature because it lets you do something that DCS ordinarily does not permit. In any event, I don't know whether the behavior is intentional in the design of VAICOM, and thought I would report it here in case Hollywood sees it as a bug instead of a feature.

Yes, that is what I meant. Understood about the potential issues. Regarding how these programs extract module information from the game, they communicate with the game using client server network protocols that are implemented on the game side by lua code that is hooked into DCS and so has access to the current state. The export.lua file is where the "hooking" gets set up. VAICOMPRO also gives commands to DCS, and this requires additional modifications of the DCS code to implement that. As far as I know, SRS does not give instructions to DCS and only uses info extracted from DCS and so does not require similar additional modifications.

I'm not sure what you mean by "in VAICOM" but it appears that this code could be run from inside the plugin itself. Is that what you mean? I would suggest that there might be other actions than switching profiles that someone would want to do when a new module is selected. So I would change the command phrase to something like "New Module Command" or similar rather than "Select Aircraft Profile." It would be nice if rather than loading an entirely new profile you could just execute some VA commands that unload one daisy chained profile and load another. I do not see such fine control of profiles listed in the VA documentation, however. Also, if you "included" the VAICOMPRO profile in each of your module specific profiles then you would only need to define the "New Module Command" once, in the VAICOM profile itself rather than create separate copies for each aircraft.

This usually means that VAICOM is not doing its automatic updating of DCS prior to running DCS. It's important to start VAICOM before you run DCS, especially right after a DCS update. So, kill VA, repair DCS, restart VA, then restart DCS. That might solve the problem. If not, it would be helpful if you would do the following: (1) start VA with the VAICOMPRO profile, do CTL-ALT-c to open the VAICOMPRO window, and check the debug box on the config tab. (2) Close VA. (3) Repair DCS. (4) Run VA again. (5) Capture and report the contents of the log window here so that we can see what VAICOMPRO is doing when it starts. Also let us know which versions of DCS you are using and where they are installed. Also what are your settings on the Config tab of the VAICOMPRO window.

A thought: I purchased the chatter license separately, not as part of a bundle, so the following may not apply to you. I received a separate validation key for it and had to validate that key separately on the "about" tab before it would start working. Did you receive a separate key for chatter? Another possibility is that you installed the chatter DLL in the wrong place. Where does it sit? It should be in VoiceAttack\Apps\VAICOMPRO\Extensions.

I suspect you have something amiss in the registry values for DCS. You might get this if there is a registry value for DCS (not the open beta version) that points to the root of C:. It would be helpful to report the log file generated with debugging turned on, since that will report the files that DCS is updating and where it is getting the locations to update. Also, what do you mean by "stand-alone and beta both checked?" I don't see any place to "check" both of them at once in VAICOM.

Couldn't you create a voice command to switch profiles? It's not quite as convenient as having the switch done automatically when you load a new module, but it should work.

VAICOM Pro is not a fraud. But before it will work, you need to also purchase a license for VoiceAttack. See the following statement from the VAICOM Pro FAQ: Q: Is this a stand-alone app? A: VAICOM PRO is a plugin specifically for VoiceAttack which means you need to have VoiceAttack (licensed version) installed on your system to be able to use VAICOM PRO. Your screenshots indicate that you are not running a licensed version of VoiceAttack.

No. The training "sticks" whether you do the Finish step or not. Training helps Voice Attack recognize those phrases. But it won't pass them to VAICOM unless you do the Finish step.

It appears you are not using a licensed copy of VoiceAttack. VAICOM requires a licensed version.

skypickle, you are confusing the training process with the Finish process. They are independent. You can train without doing a Finish or vice versa. You need to do the Finish process whenever new keywords are added to the dictionary. Do follow the directions in the Finish instructions exactly. It may appear that you are deleting the entire keyword list and then re-adding it. What you are doing is deleting all keywords from the VA profile and then adding back in all keywords that are in the VA keyword database. Those may seem the same, but they are not the same if the Finish button is hilighted.

Use Multi instead of Normal on the PTT page rotary switch and it will be available. And the ground crew hears anything you say on any radio anyhow, so you don't really need that unless you are stickler for realism.

It's also a good idea to update the registry keys that point to DCS when you move the installed location. Some utilities use these to find the installed location.