Hollywood_315

@Bob Thumbs up mate :thumbup: @Rackham PM sent @Precog PM sent

@Bob Yes, well spotted! Thanks. This can happen if you have a space or funny character in your username. Added to the buglist. Adding the quotation marks should fix it. @Mick Support for the 'Other' (F10) menu is there, but to be fair it's pretty rudimentary. Reason is that this menu has not been possible to program against: content could be just about anything, depending on the mission specifics. In VAICOM there is a callsign 'Mystery' for this that you can call with Proceed command e.g. 'Mystery, Enfield 11, Proceed'. This will take you to the next step (F1) in this menu. If you want to make more extensive use of this menu with VAICOM, I suggest these steps: *) In the mission call 'Mystery, Options' and hold PTT, this shows the available commands. *) Use 'Proceed' voice command for F1 option, use F-keys if there are more options listed. Grtz

Hey Precog Thanks - I posted reply in VAICOM 2.0 thread here: http://forums.eagle.ru/showpost.php?p=2703761&postcount=272 Grtz

Hi Precog, Thanks, good to hear! Sure in principle you can add any command you like. Just add it to Special Commands category, or create a new one. If you add a new voice command you can use it while holding down any VAICOM PTT hotkey. If you want to add new commands to be used specifically without pressing any PTT key at all you will have to use a VoiceAttack trick: In Profile options, there's the 'Override listening if my spoken command begins with...' option. If you add a word there for example 'computer', you could say 'Computer, Briefing' without any PTT keypress. Grtz

Hey Bob Good to hear you're making progress. You will need to remove the interfering F9 keyboard hook from your TrackIR config, i.e. change it to a different key. Airfield names recoginition will improve over time as you use it more, also you may want to add these to your MS Speech Library. Feel free to send me a PM if you need help with this. Cheers

Hey guys Although I can hold a soldering iron and understand most of the basics I'm pretty noob when it comes to DIY electronics. So question please: I get that a 16x16 matrix will be needed for this. Am I correct in assuming this will be a sh*t load of work to build myself? I mean seems that way to me, with a diode on every intersection and all. Or are there ready off-the shelf solutions for this on the market that I could easily order, i.e. a prefab matrix PCB with ready crosspoints that I could instantly start wiring my switches onto? Thanks a lot

No problem - good we got that solved! :joystick: You can activate the chatter function by using 'Chatter' voice command, e.g 'Chatter On' or 'Chatter Off', and also you can use a key for this, NUM. by default.

OK can you try and hold the PTT key longer? From the second screenshot it appears you're releasing too soon. Do not release the PTT key until the command is fully executed i.e. until you've heard the two beeps. I'll send you a PM with some more checks.

Hey Lux Thanks man :) Not quite sure what could be causing this error, first time I've heard of this one, but it may be related to admin settings or VA version or something like that. Anyway let me send you a PM with some checks to go through and we'll figure it out. Grtz

--- NOTICE: VAICOM 2.0 thread --- --- NOTICE: VAICOM 2.0 thread --- @All VAICOM version 1.1 is discontinued. Please follow this link and post your VAICOM 2.0 related questions there: http://forums.eagle.ru/showthread.php?p=2534446 Thanks, Hollywood ---------------------------------

Hey dadunn, I posted reply here: http://forums.eagle.ru/showpost.php?p=2697360&postcount=260 I assume you are using VAICOM 2.0 version. Feel free to send me a PM if you have more questions Grtz

Hey dadunn, There seems to be a config problem with your HOTAS: you should not see these view switches. First of all make sure you have followed the steps in the user manual e.g. remove all HOTAS MIC joystick bindings. It's important that your Warthog sends the emulated keyboard keys using press-and-hold: I don't know if you use TARGET for this but if you use Autohotkey instead make sure to check out Davisons post (#2 in this thread) and carefully follow the steps there. Feel free to send me a PM if you need more help with this.

Hi - just wondering: are you using up-to-date version ie VAICOM 2.0? On top of the first post of this thread you find the link to the thread/download for 2.0 version. Feel free to send me a pm if you need more help. Verstuurd vanaf mijn C1905 met Tapatalk

I just discovered this little tool and managed to get it to work without issue. Big props to overpro! So I now have two new devices in Windows, both are called 'C.V.P Joystick'. Anybody know a trick how to rename them?

LOL no worries good to hear it's been flagged I'm sure it'll be resolved. Grtz

@Feisty Yep, confirmed! Good job on digging this up :thumbup: I will attach a note to first post. With the snag now out of the way: enjoy VAICOM!

Still seeing subtitles while the selection box has been set to OFF... 1.5.3 release version. Has this been put on the bug list at all? C'mon ED, ON or OFF, this should be such an easy fix my grandmother could do it :smartass:

Ok thanks a lot for the update. I'll send you a PM later with a question or two regarding the Nalchik thing. Appreciate the feedback. Verstuurd vanaf mijn C1905 met Tapatalk EDIT: Issues caused by trying to use SELECT command for ATC in Easy Communications OFF mode. This doesn't work: SELECT command is only available with Easy Communications ON. In addition, specifically for Nalchik airfield a bug was identified, see post below. Thanks @FeistyLemur

Hi Feisty, Sinball You are using the right VA version i.e. 1.5.8. There's an issue with VA's most recent beta (they're working on it). Per Kozmyk's suggestion, check which DCS version you are running and adjust the patch (post #1) accordingly: http://forums.eagle.ru/showpost.php?p=2671397&postcount=242 If the path is not set correctly, your Easy Communications setting will not get read properly which would lead to the symptoms you're describing. For instance the Select command for ATC only works in Easy Comms ON mode, see manual. Let me know if this works: if not send me a PM and we'll narrow it down. Cheers

Hey Feisty This is going to sound dull but have you tried 'Select Aircraft F15C' instead? i.e. notice the word ordering. You may want to inspect the category Special Functions to check the exact phrasing. Hope this helps. BTW you say these commands in one go, without pause. Grtz

Hi there, No need to change your HELIOS, export.lua, or anything like that. Basic VAICOM setup is straightforward, step-by-step guide is in the user manual. If you want to change your PTT keys or add HOTAS there are a few more steps. Check along this thread for tips 'n tricks. BTW VAICOM is free of charge, you will just need to get VoiceAttack licensed version from their site which is 8 USD.

Thanks! Here's a big word of thanks to all generous donators. You guys are the greatest! If anyone has strong feelings about a specific DCS module that is currently missing and must be put on top of the list for VAICOM support: make sure to let me know. BTW no need to mention the Hornet, you can be sure that one will be tackled instantly when it comes out :D

setup summary OK well I got it to work and at the risk of oversimplifying here's what I did: *) Install Java 8 both x64 and x86 versions. *) Copy 'Leavu Client' folder (in LeavuEri_2.1.zip) into 'C:\Program Files (x86)\' *) Create a shortcut for LEAVU2.jar and place on desktop. *) Then copy contents of dll folder (in LeavuEri_2.1.zip) into C:\Windows\SysWOW64 *) Copy contents of of KeyBindings folder (in .RAR) to 'C:\Program Files (x86)\LeavuClient\Leavu\KeyBindings\' *) Copy contents of of Presets folder (in .RAR) to 'C:\Program Files (x86)\LeavuClient\Leavu\Presets\' *) Place the Export folder (in LeavuEri_2.1.zip, folder Fc2 Exports\Config) with all its contents in 'C:\Program Files\Eagle Dynamics\DCS World\Config' folder so that this becomes 'C:\Program Files\Eagle Dynamics\DCS World\Config\Export' *) Copy the export.lua (in .RAR, scripts folder) to 'SavedGames\DCS\Scripts' folder (create folder if doesn't exist yet). *) Open Leavu (shortcut) and load preset 'G3 - Capt Z side by side' *) Fire up HELIOS and press the leavu button in the profile to reset the displays *) Run DCS (in single display config), and leavu should auto-connect once you start your mission *) I later went into HELIOS profile editor to apply the keyboard bindings from MFD3 as here: http://forums.eagle.ru/showpost.php?p=2675565&postcount=94 so that these now also work. EDIT: per request my HELIOS profile attached for reference (slightly modified from captZ's original): inspect layer MFCD_buttons. Above is for DCS1.5 release version, you get the picture for 1.5ob and 2.0oa. Tested on Win7x64. All disclaimers apply :-) Good luck HELIOS DCS F-15C v2.4a.zip

OK got it to work in all three versions now :thumbup: Turns out I had some additional lines in my export.lua, one related to TacView, by moving that line all the way to the end of script all versions happy.

This all works beautifully on 1.5 openbeta, I'm a bit lost at the moment why I can't get it to work with 1.5 release and 2.0 openalpha. - using same export.lua - copied the same 'Export' folder to Config folder. With 1.5rv and 2.0oa LEAVU doesn't connect to the sim (stays at 'conecting to sim..'), whereas with 1.5ob it connects nicely. I'm sure I'm missing something simple.