Hollywood_315

Thanks Feisty. I currently recommend 1.5.12 because of the easier HOTAS direct setup possibility but 1.5.8 is indeed very stable and fine for users who are happy to work with Autohotkey. @Shane PM sent.

Shane revert to VA version 1.5.12 using this link http://voiceattack.com/smf/index.php?topic=293.0 Try it out and PM me if you need more help. Hollywood

C:\Program Files (x86)\VoiceAttack\Apps\VAICOM 2.0 package\VAICOM is not the correct install path. You may want to check that. It should be C:\Program Files (x86)\VoiceAttack\Apps\VAICOM.

Hey Monty Sure no worries. It should be doable earlier in the thread there were some German guys talking about their language setup check post #65 onwards https://forums.eagle.ru/showthread.php?p=2548040&highlight=german#post2548040 Regarding the Static ATC mod sthompson made a fix for DCS 1.5 here: https://forums.eagle.ru/showpost.php?p=2986946&postcount=499

Hey Reyco You're hearing the player voice issuing the command which means VAICOM is working properly. With Easy Comms set to OFF not hearing anything back can have multiple causes e.g. *) recipient out of range, *) radio not powered or properly set, *) wrong radio/modulation used, *) intercom panel not set properly (recipient is calling back but you don't hear), *) etc. Looks like you'll need to investigate, have fun :book:

No worries. Some missions -like this one apparently- seem designed to start in paused mode, you'll need to manually unpause those. Most missions however will automatically unpause on start.

Hey Smash Thanks. The install drives shouldn't make any difference. Can you make sure that the Start Mission and related commands have this option enabled: 'allow other commands to be executed while this one is running' I'm updating above post regarding unpause with some new finding. Cheers

I did some additional tests. There are currently two pending issues with VA, both reported 1) Start Mission / unpause. The Pause virtual key sent by VA is not recognized by DCS. Mission will therefore not automatically unpause on Start Mission voice command. Easiest workaround is this: in DCS config add another keyboard key to the pause function (I use `~ since that doesn't seem to be used anywhere). In the VAICOM profile edit the Start Mission command (special functions category) to send this key instead of Pause (twice). ---- UPDATE: I found that DCS interprets the Pause key sent by VA1.6 as Numlock (at least on my rig this is the case). So if you simply add Numlock key to the pause function in DCS config you don't need to change anything in VA, even easier. In DCS 1.5 things will then work as normal again. In DCS 2.0 I found that funnily enough the DCS window does not have focus once a new mission is loaded. So before you say Start Mission you need to activate the DCS window first by clicking the mouse somewhere. ---- 2) mission.lua readout VA currently chokes on reading out the mission.lua file as part of profile initialization if a keyboard key is used for PTT. The PTT function then hangs after Start Mission or Profile reset so VA needs to be restarted. It seems to be specific to DCS i.e. to the mission.lua file (it can contain Russian characters which could be causing the issue, but it may also be something else altogether). Recommended workaround is to use HOTAS buttons for PTT using the direct setup (see note attached to first post), this avoids the problem. In other news: 3) Static ATC mod This mod doesn't work for 2.0 atm but can be fixed for 1.5 by using sthompson's (thanks!!) tweak here: https://forums.eagle.ru/showpost.php?p=2986946&postcount=499 :joystick:

Hey Rick the macro builder zip is not needed, you can just ignore it. I'll be sending a PM later with some advice around the other stuff. Grtz Verstuurd vanaf mijn SM-G935F met Tapatalk

Hey Engine I had some exchange with Gary on their support forums and he was going to look into it. No followups so far. It seems that this may be somehow specific to DCS as I haven't seen similar complaints for other games. In VA there was a change made in the way DirectX keys are sent (you can no longer select DX vs. normal keysend mode) and it seems that the virtual Pause key now no longer gets properly recognized by DCS. But it could perhaps be some other glitch also. It's interesting that Profile Reset is affected, I hadn't noticed that yet myself. As far as I remember that should not invoke any Pause keysends so it may hold a clue to what's going on. Thanks for the heads up, I'll look into it when I'm back in range of my PC. Verstuurd vanaf mijn SM-G935F met Tapatalk

@sthompson Thanks, great job!

I plan to look into this when I have time. I won't speak for wartsell here but I do know he's very busy so he may not have time to work on it short term. @Bahnzo Agree may not be all that easy but let's see what can be done. It would help if we would have the Merge soon so a single version to focus on :music_whistling: I may send you a PM later to check a few things.

Confirmed, there was already an issue with the 2.0 version and now also 1.5.5 no longer works with the Static ATC mod. It seems that ED is doing some work under the hood currently to the comms menus. Not clear yet what the impact is or how long this will take before it stabilizes. If anyone picks up relevant info on this feel free to share it here. In the meantime you are advised to disable the Static ATC mod. On 1.5.5 an 2.0 you can still use VAICOM for all other communications but ATC will not work properly. Thanks

Hey Jack You can add as many commands as you like to VAICOM profiles. Just go to the profile edit page (pencil icon) and create the new commands there (probably best to put them in a new category for tidiness). You will then be able to use them with any PTT key. Any help needed send me a PM.

Thanks Brainstormer - there's no need to edit any other commands. Have a look at the note on non-US keyboard and send me a PM if you get stuck with the setup. Grtz

The comms function overall seems broken in 2.0.4.59428, pressing \ on keyboard doesn't show any menu. Likely has to do with the latest ATC expansion. It's alpha: let's see how it develops.

Hey Kozmyk That's funny I'll see if I can reproduce. Actually with ATC static mod I have 2.0.4.59428 now crashhing on mission load. If I disable the mod all good. Let me know if you can replicate, investigations continue. Cheers

Mojo did you double-check the / keybind in 1.5 config? Check the note if you're using UK keyboard layout. Grtz

Thanks Greyman yep that was kind of the idea :thumbup: Good to hear it works for you I'll follow up if there's news to share on the VA Pause thing Cheers

Hey guys thanks for your inputs. I understand there may be an issue with VA update to 1.6 regarding the Start Mission function. I haven't done testing yet myself but will investigate and see if I can reproduce. Please share any additional findings you may have here. As a general note the Start Mission uses a double pause/break command send. During testing this has proven to give the most reliable results. Most missions automatically unpause on start. Some missions need manual unpause, though I haven't traced the root cause of this yet. The *.miz mission/setting data loads normally at Start Mission, but I will check if the changes in VA1.6 perhaps have had an influence there. Any other stuff you may have encountered regarding latest VA update let me know. Thanks UPDATE: Issue confirmed. In VA 1.6 the Pause keysend functions seems to be broken so that there is no automatic unpause on Start Mission. I will report the bug to VA and update when there's a fix. In the meantime as workaround you can use manual unpause with the mouse. Still use the Start Mission voice command to load mission data and settings. In previous VA version things worked correctly, if you want to revert to VA 1.5.8.12 look here http://voiceattack.com/smf/index.php?topic=293.0.

@paulu013 Sounds good @Orso Thanks a lot for posting captain @Vampire There is no dedicated F-5E profile at this time but you could try with using an existing one Some people had ideas on this, see somewhat further down the thread https://forums.eagle.ru/showpost.php?p=2875188&postcount=389 Cheers

Hey neo - thanks, yes correct 2.0 NTTR is not fully working yet. The static ATC mod is not updated for v2.0 (although I did hear from Wartsell that he was looking into it) so there we need to have some more patience. Also the complete ATC build seems not to have been implemented in NTTR yet by ED. Regarding the other stuff wingmen, AWACS etc. that should work in principle although also there ED may not have finalized everything so results in 2.0 can vary. Indeed you should change to 'DCS.openalpha' to read the settings and mission data with 2.0. If 2.5 becomes final and we hit the version merge that should no longer be needed.

Hey thanks :thumbup: The A-10C has separate PTTs for VHF and UHF radios, used in both Easy Comms ON and OFF modes. The M-2000C profile also works with Easy Comms ON and OFF. You may need to read the separate PDF that came with the profile. The Mirage uses a single PTT radio transmit key: VHF1. With Easy Communications set to OFF, user has to manually set the radio to be used (AUX or MAIN) using the HOTAS rocker switch, and select the correct frequency/preset for the recipient.

The URI messages indicate that mission data could not be read by VAICOM. This is normal if DCS is not running. The messages should be gone after Start Mission voice command: if they persist note which DCS version you're using and check the note for 1.5 openbeta users attached to first post. https://forums.eagle.ru/showpost.php?p=2671397&postcount=242 Grtz

I'm looking into some options for a possible next-gen version of VAICOM 2.0: https://forums.eagle.ru/showthread.php?p=2534446#post2534446 The idea would be to replace the sending of keystrokes sequences with talking to DCS API's directly, injecting voice commands to AI recipients such as ATC, wingmen, AWACS, etc. I'm thinking along the lines of developing a VoiceAttack plugin dll, I checked out the basics on that, Yoda has come up with DCS remote 2 which provides a REST API on which commands can be injected over network socket / HTTP into DCS at any time during a mission https://forums.eagle.ru/showthread.php?t=162282 From first impressions this looks like a powerful tool and I got DCS to recognize basic Lo commands in export context. The missing piece at the moment is that comms menu commands cannot (?) be injected using the export environment. The ATC.lua has been modified by Wartsell for static ATC menu tables: https://forums.eagle.ru/showthread.php?t=138994 this script and others like comms.lua appear to give clues on involved objects e.g. from lines such as command = sendMessage.new(Message.wMsgLeaderRequestAzimuth) ..making me guess that there exist (global?) message tables that can be utilized. The question is how, and investigations on my end continue. However any hints from experienced DCS hackers reading this would definitely be welcome to get me going in the right direction :pilotfly: Thanks a lot Hollywood