Weegie

Think if it's waiting for additional input it means it's not recognized You could try either WIndows speech recogniton tutorial or/and the individual commands contained within inn the menu with the plug in That's about all I know, I'm having some difficulties my self trying to get the aircraft modules recognized

Mainstay The standard command for Ground power is "Ground Power On" I added "Connnect Ground Power" to my profile via the editor Cannot remember where I got this but attached is the reference list I got soomewhere and use, it's attached Vaicom Compiled.zip

Hi Dutch It means that the particular command cannot be executed when you say something. Obviously it would become really confusing if your push to talk buttons could be activated via a voice command, so they are voiice disabled and only operated by a Dx button or keyboard sequence When you use PTT you are telling VA to listen, it then exectues other separate commands within the plug in, so the PTTs start and stop the listening Tx6 is an additional Tx which is in addition to the 5 normally employed by VAICOM (4 for the radios and 1 for the ground intercomm) If you open the VAICOM profile by clicking on the box with the arrow just to the left of the profile window then open the Push to Talk list you should see Tx 1 to 6 and you can set it in there Hollywood did a video on You Tube the bit about push to talk is around 5:08, but it would be useful to listen to the full thing There is another video where he does an update too whiich is useful I hope that helps

Voice Disabled means just that, these commands are not voice exectuted. Voice Attack can execute commands from Dx buttons, Voice, Keyboard strokes etc: If you open the command you will see the option at the top and a check box next to it Some commands are grouped because that's the Plug In which is beyoond my level of expertese. If you are on'yt getting a 60% hit rate repeat the voiice training a few time then do the training on VAICOM specifically as detaied in the manual. It's a big manual but there is a lot of stuff in there and Hollywood has done a great job with it IMHO, you'd pick up a lot iif yoou take the time to go through both it and the Voice Attack manual. I'm not having a go it's a PIA to do all that reading (ask me how I know), but it is worth the hassle IMHO

Just downloaded they look terrific from the pictures, thank you

Thanks for the reply Checked my activations and I've used 2 which is correct an initial and when I reloaded 7 a long time ago due to a computer crash, so although the menus are annoying I can live with them until I purchase the graphics card then I can disable the modules and re-enable. Hopefully that will cure the menu pop ups and get rid of this minor annoyance BTW nice rig, I hope to update mine in the not too distant future

So I have a slightly odd set up I am running DCS on an SSD and have Win 7 on a separate SSD I am in the process of transferring everything across to Win 10 on yet another SSD So now I can run DCS from either 7 or 10 depending on what I choose with the boot manager. I did not disable the modules prior to installing 10 It all works a treat with one exception, when I run DCS from 10 I get the activation requests for every module, but simply exiting from them and doing nothing will result in DCS opening as normal with all my modules enabled and the whole thing works a treat Is there a way (and I'm not holding out much hope here) that I can get rid of the pop up windows requesting activation every time I start, or will I just need to live with it? As I will be updating hardware shortly (new graphics card at least) I'm loathed to burn an activation simply to stop these pesky menus from popping up. It's not such a deal breaker anyways, but it would be nice to eliminate them if I could Many Thanks in advance to anybody who takes a look to see iif they could help

Ok I stopped all mods running, deleted all the luas that Vaicom uses and did a repair That brought back the in games comms Next I opened VA with Vaicom profile and had the profile set to point to where DCS OpenBeta resides and ticked the OB tick box Opened a mission for the Viiggen, just a simple one where I'm sitting on the runway at Senaki and executed an "Abort Takeoff" this was recognized and responded to. But still no recognition of the aircraft just "--" in the pop up box for Vaicom on the PTT page I've attached the log file as I enabled the "Run in Debug" option I'd appreciate if Hollywood or somebody who knows Vaicom in depth would take a look to see if they see anything wrong VAICOMPRO.zip

Vaicom is seeing a mismatch on the data base I think You need to update the profile Jump to 11:07

Definitely was, I have no idea if it was taken back down or not or if it even works now I do have a copy of it, if you cannot find it and really want it drop me a PM I'll see if I can dig it out

Tried that SmirkingGerbil, no dice I'm afraid. I had not thought of it though and your reply was much appreciated because you never know, but I'm stumped how it would work as it would place the luas in the wrong place I'm really glad it worked for you, I'm getting pretty frustrated with it. I disabled all my Mods too, just in case, no difference. I don't think it's even interfacing with the game any more

The problem is deeper than your fixes I'm sad to say I tried them already and no difference both before and after re-install After implementing each fix I also came out of DCS entirely and shutdown VA, then restarting both VA and DCS, no difference In fact after the re-install things are worse as the comms do not seem to be getting recognized at all Before a re-install I had my own profile running and Vaicom linked to it, I know that's not recommended. Although I was not getting module recognition on the pop up at least I had comms. Now running Vaicom on it's own I currently have no comms I only run TARGET and Track IR and for one trial I ran without TARGET enabled, all of these attempts have proved entirely fruitless Any other ideas because it has me completely stumped Inside the Special Tab Vaicom is there and installed along with chatter

I need some help here Hollywood I cannot get the pop up to recognnize the aircraft and never have done. I ran a complete Voice Attack & Vaicomm delete & reinstall Currently only running Vaicom as the profile, previously I did manually install the luas requested and I noticed that luas that need to sit inside the game itself were not there, but placing them into the correct folders did nothing During the reinstall I moved both VA & Vaicom to C: they were previously installed on D: unfortunately absolutely no difference whatsoever Anything you need to look at this?

Got a question on Chatter If linked to radio power when using easy comms in Multiplayer I don't seem to hear anything is this correct or is something screwed up?

Yup Me too First thing I do after centering Track IR is lower the seat then its no longer a problem

I run aircraft control profiles and I had Viacomm included too but it was a PIA as had to stop and start VA to get Vaicom to work again Thanks to slicker55 I deleted all the Vaicom commands out my profiles then linked Vaicom to them instead No more crashing of Vaicom, early days yet but I can change profiles without any problem awesome

Any chance of a readme or some more explanation I am struggling to understand Sorry for being so dumb

Ok I've found a way to make Vaicom less fragile so I no longer need to shutdown VA to select a new profile Instead of having Vaicom as part of a profile I've kept it separate from the commands I use to activate various aircraft systems Then what I've done is linked Vaicom to my aircraft profiles and so far it works a treat. I no longer need to shutdown VA and can now switch profiles on the fly and Vaicom no longer stops working Video on how to link here

Can't help with codes for Persian Gulf I very rarely fly in it at the moment I found Heatblur's kneeboard a bit cluttered so to make things more readable on a kneeboard I made a list for radios and TILS I've attached it anyway if it helps AJS-37 Airfield Data.pdf

I'm using Vaicom + with my own profile for switches and radios etc: it works but it can be a bit fragile. Should you change profiles the plug in crashes, in order to change a profile and get both my own profile and Vaicom to work I need to go into settings and tell VA to boot with the aircraft I want, you can't change them on the fly so to speak (well I haven't managed it so far). If I make changes to my profile that very often will crash Vaicom too. However closing and reopening VA brings everything back and that can be done without any need to come out of DCS When using my profile and not Vaicom commands I have a separate button set up to talk to VA, then I have the usual 5 button set up for Vaicom as well Hope that helps

Just in case it's not only comms Bailey did one that I had some input to it does things like tune the radios on the F-18C I've also adapted this for basic radio and some other stuff on the AV-8B and the AJS-37 Bailey's mod is here https://www.digitalcombatsimulator.com/en/files/3302954/ If you'd be interested in my modifications for the other modules PM me There is also some profiles being made by Daley which are paid for profiles, not expensive, as I recall they cover F-18C, F-15C and Mirage, $2.50 Thread here https://forums.eagle.ru/showthread.php?t=227717

I think I've found the workaround but that doesn't really let Heatblur off the hook. The Viggen was constantly causing the computer to crash, now admittedly I'm using an old Ti780 card which will be upgraded soon. After anywhere between 5-15minutes in the Viggen the whole thing locked up solid and I had no choice but to resort to a hard reset. I then got informed by the Bios that the overclocking had failed. This does not happen in any other module that I've flown in recently I found a fix through Google and that involved rolling back the NVidia driver to 391.35 I've just tested it for about 25 minutes or so and all is good (so far), but it looks like this problem has not been fully resolved in over a year and I'd consider a fault that makes the module unplayable a bit of a biggie I'm not trolling and I'm not angry or upset (now), but merely posting in case anybody else encounters this problem and is looking for a temporary band aid until it is properly addressed. I know these things can be really difficult to hunt down and fix let alone fully resolve, so not having a go just saying the problem is still lurking in all that beautiful code. I'm only posting because I love the Viggen so much it is a truly awesome module and it was so frustrating that I couldn't fly it.

Thanks for the links Sokol that's appreciated. I may just end up junking the throttle and getting a Virpil, but then if I go down that route I don't want to junk my aftermarket slew, so I'd need to find a way to have it incorporated into something. Perhaps build a button box and incorporate the slew into it.

Thanks Sokol It's not a deal breaker as I could certainly use a keyboard emulator Some of the comments on the detent are a little worrying though

Hi Boris Thanks for the suggestion but I'm not looking for a slew, I have a force sensor installed already What I'm looking for is an improved hat switch for the hat on the side of the RH throttle