Hollywood_315

Hi, I confirm the Import Profile issue in current beta (.17). Reported to VoiceAttack Support, I expect they will address this soon. Note: this affects import of new profiles only, existing ones run ok. In the meantime can you download 1.5.8 release version and try getting started with that for now. I'll update when I have more news. Thanks

Hey Jack, Did you update VA to 1.5.8.17 beta? The checkbox is at the bottom of the Select Joystick Buttons window, where you assign the joystick button press. Verstuurd vanaf mijn GT-P7300 met Tapatalk

+++ IMPORTANT NOTICE FOR HOTAS USERS +++ +++ IMPORTANT NOTICE FOR HOTAS USERS +++ Hey guys, Great news! VoiceAttack latest version (1.5.8.17 beta) now supports functions for joystick button release. This means that keyboard emulation is no longer needed to use VAICOM Push-To-Talk with your HOTAS: TARGET and Autohotkey have just become obsolete! This should make life a lot easier i.e. HOTAS PTT setup much more straightforward :) Read below on a few simple steps to have your HOTAS now work directly with VAICOM. :joystick: Join me in a big word of praise to the guys at VA who were kind enough (after much nagging from my side :D) to implement this new feature. Thanks Gary!! Grtz Hollywood ++++++ --- HOTAS PTT direct setup --- 1/5/2016 You can use VAICOM PTT directly with your HOTAS. Follow below steps to make VAICOM PTT respond directly to joystick buttons. Adapt for each VAICOM profile that you intent to use. First: *) Upgrade your VoiceAttack to version 1.5.8.17 beta or higher. Existing VAICOM users: *) If you are already using keyboard emulation with TARGET or similar: disable it. *) If you are already using keyboard emulation with Autohotkey: from now on do not run Autohotkey anymore. To set up direct PTT: *) In VA, go to options/general/ joystick options. With the + icon, add your joystick e.g. HOTAS Warthog Throttle. OK. *) Load the VAICOM profile and go to edit (the icon with the pencil). Open (+) the Push-to-Talk category. Edit each command in there as follows: *) Double click to open. Check 'When I press button' and click on the [...] button. *) Select Joystick Buttons window: Press the refresh button (the circular arrow). Note: It is necessary to do this refresh every time before you set up a new button. *) Then, on your joystick, press the physical button you want to use and it will be recognized in the window. *) IMPORTANT: if you are editing the command for RELEASE e.g. 'Transmit VHF1 released', check the box 'shortcut is invoked only when all buttons are released'. Store with OK. *) IMPORTANT: if you are editing the command for PRESS e.g. 'Transmit VHF1 pressed', do NOT check this box. *) Note: Of course in above the joystick buttons used for VHF1 press and VHF1 release must be the same button! Make sure you get this right for each press/release combo. *) Note: optionally you can uncheck the 'when I press keys' option for each command if you intent to no longer use your physical keyboard for VAICOM PTT. *) Check in the VA log that PTT press/releases are correctly recognized. Done! ------

Hey landgenoot :-) For the MIG-15bis can you try with latest VoiceAttack beta i.e. 1.5.8.16 and let me know how that goes. Send me a PM if you have more questions. There were some issues with previous VA beta versions e.g. .14, but .16 looks solid. Thanks

Hey Viper, Sure no problem. The steps are like this: *) Load the profile and go to Edit (the icon with the pencil) *) Then you'll see a long list of Categories. (If not: look below in VA status bar and press the small square icon left of 'XXX commands'.) *) Press + next to category 'Process Management' *) Now look for command '_Menu_Execute'. (Note you will be editing just this one, not other commands like '_Menu_Execute_ATC' etc.) *) Double-click the command to edit. Change the lines where '\' key is referenced and store with OK. (for F-15C this is lines 3 and 6). Done! If you need more help just send me a PM.

Hi, I'm happy to announce that a VAICOM 2.0 profile for MIG-15bis is now available. VAICOM uses VoiceAttack voice recognition to provide deep immersion, fully replacing the F-key based comms menus. This allows for a realistic experience and faster response times when flying complex missions. Download and more info via this thread: http://forums.eagle.ru/showthread.php?p=2534446 Video: https://www.youtube.com/embed/kNyJUs3WaNE Enjoy! Hollywood

--- NEW MODULE AVAILABLE: MIG-15bis --- --- NEW MODULE AVAILABLE: MIG-15bis --- A new module is available! The MIG-15bis. You can now fly this epic aircraft without menus using VAICOM. Thanks donators! Download here: https://www.digitalcombatsimulator.com/en/files/1884218/ Enjoy! Hollywood Note: This module requires VoiceAttack version 1.5.8.16 beta or higher.

Hey Vogel, Thanks :thumbup: I assume you've done all the voice training,i.e. via Windows Control Panel / Ease of Access. Then likely something minor, e.g. subtleties in speech timing can make the difference for recognition. You just need to develop that by using it more. For this example start with saying your command very deliberate, i.e. as 'two,'..(very short pause)...'go recon 2.'. This will increase your hitrate. Then, when used more often, as MS Speech recognition learns, you'll be able to shorten your timing. Let me know how it goes. View switches should not occur when used correctly, but there's always the chance of a glitch. A common mistake is releasing the PTT key too soon (i.e. before the beeps). Also if you use Easy Comms OFF, TrackIR may be interfering with HOTAS MIC keybinds. I'll send you a PM to see if this is reproduceable and can be nailed down to anything specific. Grtz

@funkyfranky Thanks mate! Good to hear you like VAICOM. Try switching on BATT power before you start talking to crew, that should do the trick. EDIT: and radio dial set to T/R of course. Grtz

Thanks mate, much appreciated. You keep up the good stuff on the Vive thread- I ordered one, so following with interest :thumbup: Grtz

Hi, can you send me a PM please with some details of the problem? See this post http://forums.eagle.ru/showpost.php?p=2742370&postcount=307 Hollywood

Hey guys , I made the concious decision to go for the Vive as it appears to be the marginally better and more complete kit compared to the Oculus overall. Awaiting the kit to arrive any decade now. I'll be sticking to my decision, but browsing through this thread it does make me slightly nervous in terms of what to expect with DCS when I read this stuff about low framerates etc. I am no expert in this area at all (at least not yet). Will this be a matter of ED dev putting in some additional effort to improve their Vive support (assuming they focussed on the Rift first), or are there more fundamental issues at hand here? Appreciate your informed opinions on this. Cheers

Hey Corbett Well, always willing to help where I can. But generally there's a lot of things that can be specific to your setup. So the description of the problem must be a bit more more precise for me to be able to support. Below I will state -for everyone actually- how to raise a support ticket :D ----- SUPPORT INSTRUCTIONS ----- First I need you to make sure that you have read the User Manual and followed the detailed setup and usage instructions in there to the letter. Also you must have carefully checked the notes attached to the first post (#1), and additionally Davisons post (#2) if you plan to use Autohotkey for HOTAS setup. In this thread there is lots more additional useful info that could help you identify what could be your issue. Try using the 'search this thread' forum function. Then if all else fails please state the details of your problem (here or via PM), and under which circumstances it occurs. Kindly include at the least the following info: Windows version DCS version VoiceAttack version VAICOM profile Easy Comms mode ON or OFF HOTAS/Autohotkey used Other peripherals running (TrackIR, HELIOS,..) This will help to get rapidly to the bottom of it. In almost every case we manage to get things sorted out, so no worries! Cheers :beer: Helpdesk Hollywood ----

No worries mate - let me know if this re-install improves things, if not send me a PM again and we'll get it sorted out.

Shaz there must have been some glitch, I don't have a message from you in my inbox. Autohotkey must be run as administrator: for Jason that fixed it.

Hey Blue - I suggest you check the note on keyboard layout (attached to first post), you may have a non-US layout mismatch. You will also need to check that NUM keys and also the HOTAS MIC buttons are not in use anywhere in DCS config (see manual). The HOTAS emulated keys must be set-up for press-and-hold in either TARGET or Autohotkey (check Davisons post #2). If that doesn't fix things make sure to send me a PM.

Hi Jason Thanks, let's have a look This actually is normal behavior, VAICOM doesn't show you any menus. The only exception is with the OPTIONS command. You just go ahead and speak your command, keep the PTT key pressed until you've heard the beeps. First check in the VA log after start mission that the Easy Communication setting has been properly read. In the User Manual (Getting Started section) you'll find some easy examples to start testing commands with i.e. direct crew, wingmen etc. If you have issues with command execution check the note on keyboard layout (1st post) and make sure that other programs such as TrackIR are not interfering with a keyboard hook. Make sure both VA and AHK are run explicitly as admin. Let me know how it goes and send me a PM if you need more help.

Hey Shaz I haven't heard other reports of VA crashing on either Win10 or Win7, but for Win10 it's important that VA is run explicitly as administrator. The latest VA version incl. the now-latest beta all look stable from my side, on both Windows versions and with all DCS versions. If you have a consistent stability problems on your rig probably best to report to VA Support on their website. On a more general note (not related necessarily to VA/VAICOM): All the optional peripheral stuff you need for your setup, such as Autohotkey script for HOTAS, HELIOS, TrackIR etc. need to be started separately on-by-one each time before launching DCS. As this can be a pain in the ass to do every time I made several desktop batch scripts (.cmd) that do this startup sequence automatically with a single mouseclick. Perhaps below example excerpt lines from my script can serve as inspiration: .... START "TRACKIR" /affinity FF00 "C:\Program Files (x86)\NaturalPoint\TrackIR5\TrackIR5.exe" START "VAICOM" /MIN /affinity FF00 "C:\Program Files (x86)\VoiceAttack\VoiceAttack.exe" -profile "VAICOM v2.0 A-10C" .... The /affinity option you can delete if you want, I use it to assign all processes to specific CPU cores to optimize performance. Send me a PM if you need more help. Cheers

Same problem here - occasional (very) low gauge refresh rates in HELIOS with DCS 1.5/2.0oa while it used to work well before. My rig is completely op to spec so no bottlenecks there. If it's MSAA that's causing it then switching it off seems like too much of a sacrifice to fix it.

Hey Bassam Let's have a look. "Mozdok" is not a complete command by itself (e.g. "Mozdok, Request Vector" would be). Also releasing the PTT key too soon could be causing it. I'll send you a PM with some checks. Grtz EDIT: solved.

Hey hog_driver111th, I suggest you first check that VoiceAttack is running as admin. Send me a PM if that doesn't fix it. The trick with the Warthog/ HOTAS setup is that the emulated PTT (NUM) key must be held down for as long as the joystick button is pressed. You can set this up in TARGET or use Autohotkey: make sure to check out Davisons post on this (second in this thread).

Hey Dadunn The Easy Comms setting is updated when you start your mission with Start Mission voice command. Check the log after you have done this, if there are URI error messages in the log you may need to apply the tweak as in this post: http://forums.eagle.ru/showpost.php?p=2671397&postcount=242 I do assume you are using VAICOM v2.0. Check on the DCS 1.5 note attached to first post of the VAICOM 2.0 thread http://forums.eagle.ru/showthread.php?p=2534446. Please post any further questions there, and PM me if you need more help. Thanks

@Beeroshima see PM @FeistyLemur yep JTAC can be a pain in the behind in the beginning. You need to follow the correct flow steps, it's a learning curve. @Stonehouse good news, it works with VAICOM in 1.5. The thing that is screwed is in the UI but with VAICOM you don't use that anyway. In 2.0 alpha version it does not work properly (yet). Verstuurd vanaf mijn C1905 met Tapatalk

@flyinghigh PM sent.

OK guys good suggestion and how-to summary - much appreciated. Noted as input for next release updates. Cheers