Hollywood_315

Yes I got the basics to work using postman, wil dive in some more to see if I can inject comms menu commands e.g. send a 'break right' command to wingman (normally triggered by F-keys menus). I'm guessing this lives outside of export context but no idea on all this yet. Guess I have some research time ahead :joystick: all tips welcome Anyways good stuff this is a potentially powerful tool it seems.

Sounds interesting! I'll make sure to check this out thanks

This looks just awesome, fantastic job. Small question: is the LED bg color pure green or do you insert RGB strips that allow for color mixing? Reason I ask is I like my panel backlighting to be 'electric green' ie green with some blue mixed in. I could always do the LEDs myself of course but just wondering. Cheers and keep up the good work! Verstuurd vanaf mijn SM-G935F met Tapatalk

Hey Dooley - good to hear you got it working. Sorry for the late response, let me know if you need more help. Grtz

Thanks guys, @nguludi PM sent. Feisty's tips are good, check #5 specifically https://forums.eagle.ru/showpost.php?p=2892067&postcount=434 @FeistyLemur This is correct for Easy Comms ON but with Easy Comms OFF you can use any radio.

Fixed as per above https://forums.eagle.ru/showpost.php?p=2889598&postcount=415 @Bottle-RUM thanks for updating. Grtz

Hi Rum, - Holding PTT long enough, i.e. until you've heard the beeps? - Using US international keyboard layout? - Are both PTT Press and Release commands properly bound i.e. to the same joystick button? I'll catch you on PM.

Thanks for this, I'll have a look and see if I can figure it out. Will send a PM after I've done some testing. I need to check what the exact steps for Type3 actually are again lol I now realize that may not have been properly documented anywhere. If I'm not mistaken it's this: (briefing stage) > clear to engage > call 'No Mark' > target destroyed > call 'Confirm Kill' or 'Attack Complete'. Verstuurd vanaf mijn SM-G935F met Tapatalk

Those crashes sound nasty. I cannot reproduce it myself, 1.5.12 on my rig is all stable (I'm on win7). Shooting Gallery has multiple JTACs in the area, one of them a Predator, which may needlesly complexify things for flow training. That is you may need to dynamically keep track of which JTAC you're talking to, and use the JTAC Select command. For basic JTAC flow training with VAICOM I recommend this mission JTAC Live Range and the night version JTAC Night Range. You can tweak them in mission editor for different scenarios.

@RUM Which VA version are you using? Make sure it runs as admin. Send me a PM if that doesn't fix it. @FeistyLemur The trick is to confirm the operator call before proceeding. On operator call ' target destroyed' reply with 'copy kill' or 'confirm kill'. On call 'target is not destroyed' reply with 'copy miss'. Then proceed with next pass. Some more details on this in the user manual. Verstuurd vanaf mijn SM-G935F met Tapatalk

Hi Mutz I just stumbled across your post. Let's see. Maybe you can try to skip Autohotkey altogether and bind your joystick for PTT directly (see note attached to first post): http://forums.eagle.ru/showthread.php?t=151296 That's probably the easiest way forward. If you changed \ to NUM\ check that in-game this physical key does indeed open the comms menu. Let me know how it goes and send me a PM if you need more help. Hollywood

Same here. Subtitles remain visible always, even when selection box in options is unchecked. This bug has been around for a long time now: has it been reported?

You can just install over the current install and it will retain settings afaik, I don't recall ever having had to re-import profiles.

Yes current release 1.5.12 is stable and joystick direct PTT works nicely with it. Indeed you can skip the keyboard (NUM keys) for PTT altogether and free them up again for snapviews or the like.

Thanks Feisty. With the recent versions of VoiceAttack it has become possible to trigger PTT with HOTAS/joysticks directly, so you can do without Autohotkey if you want. See the note attached to first post.

Bedankt RUM, good to hear you like VAICOM! Nevada ATC is not supported at the moment, amongst other things it has to do with that the Static ATC mod has not yet been updated for version 2.0. I expect this will be addressed, so stay tuned.

LOL - welcome mate! Enjoy

@FeistyLemur Good info, thanks for sharing! Seems that this is specific to the F-5E. @Wrench Could be related to where your apps data folder is located, you can check the note for 1.5 open beta users attached to first post if you want to see which files to inspect. Anyway you can easily set the default value for Easy Comms to False: In VA go to profile edit (pencil icon), category Process Management, command _Menu_Set_Defaults. Double click the line where Easy_Comms is set to True and change the value to False. Done.

@capthaltli There's no VAICOM profile for the F-5E at this time, if you want to fly with this aircraft you can try to adapt an existing VAICOM profile. Maybe check with @NeilWillis who has similar plans: see above a few posts earlier.

Hi Pete There should be no need to disable your existing profiles, you can use the VAICOM 2.0 profiles alongside. It's no longer required to use Autohotkey for HOTAS PTT setup: Just make sure you have installed up-to-date VoiceAttack version and follow the note on direct PTT setup attached to first post of the VAICOM 2.0 thread. If you need more help with anything let me know. Grtz

@Loz With Easy Comms OFF it can be tricky i.e. you may not hear response if the Intercom Control Panel dial is not set correctly, the radio is not powered or configured for the right transmit mode, recipients may be out of reach, etc. If you haven't done so yet, can you try an instant action mission where you start mid-air and see if you can get your wingman to respond to commands over UHF. If that works then config is ok (verify the HOTAC MIC keybinds in DCS config are set to defaults) and you can move on from there. @capthaltli No need to edit the .vap file manually. Just open VoiceAttack, edit the VAICOM profile (look for icon with pencil), category Process Management, command Menu_Set_Defaults. Look for the line where Auto_ATC_Select is set to False. Doubleclick to edit, and change value to True. Done.

Hey bouncer Thanks for the info. I cannot reproduce this problem myself but perhaps others have similar experience. There's been no change to VAICOM, so if this is across all DCS versions then the problem likely originates from VoiceAttack sw. I assume you use their latest release version. Let's keep track on this: please check that there have been no recent changes (hw/sw) on your rig that also might be related to this issue. Perhaps check the VA forum if other users report similar issues with other games. Grtz

Hi everyone, Let's catch up on the questions you have asked. Seems I'm a bit behind :D Some answers below, PM me if you need more help! Cheers Hollywood @Dogman/Loz/Beeroshima/Kuabi In general, the Invalid Radio messages in the log can point to a couple of things 1) Releasing PTT too soon ie before the beeps. 2) Wrong recipient/radio combination eg calling 'AWACS, request picture' on UHF radio, 3) A misinterpreted command, or 4) Some PTT config problem. As a new user you will need to spend some time with the program to let it get used to your personal mode of speech. The number 3) variety usually comes from a mistaken word interpretation. This is much more common when you just get started with VAICOM. In the beginning it is advisable to speak sentences much slower then you would normally, with short pauses between keywords. This will help the engine to catch on. After a while you can start speaking faster. Also many people report that adding keywords to the MS speech library helps a lot for them. This is very personal. For some this is a must, but for others such as myself only one or two very stubborn words (Novorrosyisk, anyone? :ranting:) need to be added. Inspect the log to see how your command was interpreted. See what works for you. Try your initial testing with easy comms set to ON and most of all have patience in the beginning, it will not all work perfectly from day one and you will need to invest a bit of time to get the most out of the system. @NeilWillis You can have a look at the MiG-15 profile, Chocks are also in there with the Crew commands. When you want to make new crew commands (e.g. air) yourself, inspect the menu structure, copy an existing Crew command (e.g. Request Repair) in the profile and adapt the new command: i.e. label, keywords, and inspect the code for the associated (F-)keypresses. Change these as required to match the menu structure and test. @maverickturner Well, although I haven't tested this myself VA has a profile options (look for the checkbox icon) function that says 'override listening if my command begins with'. You could experiment with what happens if you put keyword 'Click' there or similar. @M1Combat Most of it sounds like normal behaviour. The Mirage radio system only has a single PTT key (VHF1). You can check the VAICOM PDF documentation that came with the M-2000C profile. The OPTIONS command should indeed show you the (sub)menu. In the VAICOM user manual documentation more info on this. @protea1 It seems you are using Legacy Audio setting. Disable this in VA options (the wrench icon). I assume you have went though the setup documentation and note about non-US international keyboard etc. I'll send you a PM to check how you have set things up and what else could be interfering. @placebokid These are not part of the current command set for the UH-1H profile. I have not identified these commands when the profile was created. Perhaps they were added later. They could be included in the profile if the menu structure is available. Using internal logic VAICOM dynamically constructs command key sequences that are sent to DCS. @Captain Orso Yes correct. In Easy Comms ON mode, the comms menu key (\) is used and in Easy Comms OFF mode, HOTAS MIC or COMM Push-To-Talk keys (RALT+\, etc.) are used. If the latter function is now broken in the recent beta I will need to get some input if this is in fact a confirmed bug or an intentional move by ED to restructure the comms menu setup going forward. Would be good to know if this applies to all modules or just a single one. I'll send you a PM later. As a workaround you can use Easy Comms ON until resolved. Thanks :joystick:

Hey guys - thanks for the messages I'm currently on holiday with the family - nowhere near my PC or flightsims lol. I'll be getting back to your questions as soon as I can. Cheers Verstuurd vanaf mijn SM-G935F met Tapatalk

Hey Captain. Let's see. Skipping the obvious checks (numlock is on?) it seems you may have some conflict in your setup. From the log I see the combo rctrl+num5 is used by the script but you also use this as your ptt hotkey.This should be avoided, and more generally using modifiers like Rctrl is not recommended for the ptt hotkeys. Can you first check in dcs config that the right key combinations are used there ie num5 for comms menu and rctrl+num5 for mic switch respectively. Then in the profile -ptt category- change the ptt key to '5'. Try if things do work with this hotkey. If the issue should somehow remain send me a PM. Grtz! Verstuurd vanaf mijn SM-G935F met Tapatalk