sthompson

See Hollywood's suggestion in this thread: https://forums.eagle.ru/topic/254389-per-aircraft-ptt-buttons/?tab=comments#comment-4505760. Also Weegie has posted some good ideas about this recently, but I'm having trouble finding them. You might do a search in the VAICOM forum. (This thread is no longer the main place for such discussions.)

It could be related to the "SRS PTT Mapping" option in VAICOM even if you don't have SRS. I found that toggling this changes the radio assignments to TX nodes. With that turned off I'm getting the correct mappings in the Tomcat. Caveat: I tested this in the 14B. Is the issue only in the 14A?

https://forums.eagle.ru/topic/257727-happy-new-year/

There was a very recent change in SRS that might be causing this if you have SRS PTT Mapping enabled. I find that I get a reversal of TX1 and TX2 in the Tomcat when this is enabled. Try unchecking it on the MP tab or using the button on the PTT tab.

It doesn't do either of those things. It changes the radio frequency as if you entered a manual frequency. However, neither the UFCP nor the radio panel show any changes. And if I reselect the displayed preset channel it reverts to the original frequency, so the presets are unchanged. To be clear, if instead of using VAICOM I tune a frequency manually using the radio panel the manually tuned frequency does not display on the UFCP. Perhaps that is a feature of the real plane. However with manual tuning I can see the actually tuned frequency by glancing at the radio panel on the left hand side of the cockpit. But when VAICOM PRO changes the radio tuning that radio panel displays the old preset or previously tuned manual frequency as if nothing has changed. Ideally using VAICOM PRO a new preset channel would be selected and displayed, or a new manual tuning would occur and be displayed if the desired frequency does not correspond to a preset.

I don't fly VR but use TrackIR instead, but use the same trick. There is no return to "normal view" because the new view with your head naturally a bit further back is more normal than the "normal" one that implicitly has you leaning in all the time. The downside is that this changes your perspective on the instruments and HUD, and possibly you won't like the new view as much. But I don't think there is any way to quickly toggle between two default view positions. That's presumably why the OP was asking about snap views in the first place.

Short answer: Do exactly what it says in the pop up. Longer answer: There is more detail about the Finish step in the manual. In the current version it is on page 36. (Aside: Various places in the manual tell you to look for it on the wrong page.) Detailed answer: In your case you do not have "multipart commands" consolidated in your profile and instead are displaying each keyword as a separate line. So in the profile screen (right side of your screenshot) you first need to click the icon just to the right of the "Import Commands" box in the lower left corner. It currently appears as three horizontal lines each preceded by a dot. This will change the icon to just one line preceded by a dot, and will cause all of the "AI Communications" multipart command parts (each is a single keyword) to appear in one line rather than as separate lines. Then do the things in the popup. That is, double-click on the "AI Communications" command to open it. (It's the line directly below "Keyword Collections" that has a long list of keywords.) Within this command, highlight and delete everything on the "when I say" line, and then paste in the contents of clipboard, which will hold the new keyword list. Finally, click OK to save the new version of that command, and then "Done" to save the changes to your profile.

@Gorlow, you have quite a few VoiceAttack plugins all running at once according to the log. Have you tried removing all of them except for VAICOM? Perhaps there is a conflict. You might also turn on VAICOM's debug mode and restart to look for additional cues. Also, VAICOM PRO saves a log file (not the same as the VoiceAttack log) in folder C:\Program Files (x86)\VoiceAttack\Apps\VAICOMPRO\Logs. There might be additional clues there. Finally, do you have this problem with the stock VAICOM PRO profile? It appears that your profile includes kneeboard commands activated by the joystick, so I assume it is not stock.

I think this must have changed. Tonight I had datalink and Tacan going at once on a MP server. However the TACAN option on the HSD page was not visible while datalink was active. I had datalink active and then tried turning on Tacan from the Tacan page. It seemed to go active, but the Tacan option was not visible on the HSD. When I turned off datalink the Tacan option became available. I selected it. TACAN cues displayed on the HSD. I then turned data link back on. The TACAN info continued to be displayed on the HSD. So I then had TACAN cues on the HSD and datalink at the same time.

I use VAICOM PRO a lot. I can use it to tune the radio with my voice, for example. However in the the JF-17 changes in radio tuning made using VAICOM PRO do not show up in the UFCP display. I can confirm that the radio tuning did change, since the tuned recipient responds. The new frequency also shows up in the SRS overlay. But the UFCP display remains out of synch with actual tuning until I change the tuning manually.

I'm trying the JF-17 in the current free-to-fly period and liking it very much. Except for the VAICOM integration. I'm having the following troubles and wondering if I'm alone: When I use "Select Tunes Radio" a select command does tune the radio, as verified by successful transmission to ATC. The frequency also shows on the SRS overlay. However the displayed channel in the cockpit does not change. I assume this is a problem with the module, not with VAICOM. It would be nice to get the cockpit display working to show the actual tuning. VAICOM' does not play nicely when SRS PTT Mapping is enabled. Symptoms include: No frequency displayed in the VAICOM window when transmitting. Only TX1 is available as a PTT even though SRS is supporting both of the module radios plus an expansion radio. No TX nodes are available at all unless the PTT switch is set to NORML or SNGL.

I also wish they were easier to find and that a collection of links to installed manuals were available somewhere. However I suggest that the place for this is not the main GUI interface. When I want to review a manual while flying I do not want to exit the mission just to open a manual. A "DCS Documentation" subfolder of the Eagle Dynamics start menu folder seems like a better place for these links. I actually keep such a folder handy already, but it needs a lot of manual updating. Alternatively there could be an entry on the Escape key menu (similar to the one for adjusting controls) that would let you open a manual from a paused game.

Yes, I do see something weird. You have the DCS install paths (both stable and openbeta) pointing to Saved Games. Is that where your installed copy of DCS lives? Usually it lives in Program Files or in a separate directory tree.

Turn on debug mode, restart VAICOM, then post your log file here so we can see if there are any issues on startup.

Where can I find that mod?

Any chance you could post the full update list? There is no news in the I-16 forum and I don't know where to find the announcement that you partially copied. I hope they finally give us a radio and kneeboard. Those are long overdue.

We had autodetect before this change. The only difference is that you can now trigger it while the game is running rather than just having it work once at startup.

The question was what you need to do after a DCS update, not a VAICOM update. After a DCS update you definitely need to restart VAICOM with DCS not running, and only then start DCS again. That lets VAICOM update the DCS lua files that may have been reset when DCS updated. You may or may not need to also delete export.lua first. I find that isn't necessary on my installation, and I've been puzzled why it is recommended so often. It only helps if the file was not set up correctly in the first place.

Does SRS work for you in the F-14 when VoiceAttack is not running? It sounds more like an SRS problem than a VAICOMPRO problem if it works in some modules but not others.

I've found that I often cannot use TX6 to issue one of my own voice commands. For example, I have a command "Gear" to toggle the landing gear by transmitting a keypress G. It also writes a message to the log before and after the keypress. This works fine if I am running in hot mic mode, or if I use one of the TX1, TX2, TX3, or TX5 keys to open and close the mic. But it is hit or miss --mostly miss-- with TX6. The VA log shows that "gear" was recognized with high confidence (95-100 usually) and the appropriate messages get written to the log, but there is no response from DCS. I wondered if it might be a timing issue, so I've tried pausing before saying "gear" after the mic is open. I've also tried increasing the time the G key is held to one second. These made no difference. I've tested this in the Tomcat and the Mig-15 with similar experience in both. Any thoughts about what might be causing this or how to debug the issue will be appreciated.

Option for ICS Hot Mic is no longer selectable because it follows the switch setting in the Tomcat pilot cockpit. (The checkbox on the options screen doesn't sync with a change in the switch setting until you push a TX button, however.) Further suggestions: Is VAICOM working otherwise or is it only an AIRIO issue? Does VAICOM recognize that you are in the Tomcat? (That is, is the Tomcat identified as the current module on the PTT page when you are in game using the Tomcat?) It would help possibly with diagnosis if you could attach the VA and VAICOM logs, with debug mode enabled.

Here are some directions to get you started. (Supports only TX1 and TX2 but edits to support other radios should be obvious once you get these setup.) Download attached VAP file and save in your VAICOMPRO\Profiles directory. Start VoiceAttack and load your VAICOMPRO profile if not active already. Press Alt-E to edit the profile. Click on "Import Commands" and select and open the file you saved in step 1. Make sure that all four commands are selected and click "Import." Double-click on the Set TX1 command. Click the "When I press button" selection and press your desired button for TX1. Click OK twice. Double-click on the Set TX2 command. Click the "When I press button" selection and press your desired button for TX2. Click OK twice. Double-click on the Alternative PTT press command. Click the "When I press button" selection and press your desired button for PTT. Click OK twice. Double-click on the Alternative PTT release command. Click the "When I press button" selection and press your desired button for PTT. Verify that the box for "Shortcut is invoked only when all buttons are released" is checked. Click OK twice. Delete the regular PTT commands that might conflict. Click DONE Test by bringing up the VAICOM window, PTT page, and trying out your new buttons. VAICOM Alternative PTT Profile.vap

I don't have VR but wouldn't be surprised if it over-rides the static camera movement commands too.

Did you have TrackIR running when you tried moving the camera? It will cause the camera to reset on the slightest head movement. I've created snap view of the sort you are describing in other modules (the Mig-15 for example). I found I had to suspend TrackIR while setting them up.

Same here, except for a hiatus between Flanker 2.0 and DCS 1.5. I didn't have a rig that could handle the graphics between those two. I really loved Flanker 1.0 (and 1.5), especially the IronHand missions. Wouldn't mind playing it again if I could figure out how. I sometimes get nostalgic for the Crimea map.