Weegie

Yeah that's probably the way I'd go too. There are some oddball retruns in various aircraft and TBH I'm rarely in the A-10 Do fly the Viggen a lot and some in there are the same, trying to fugure what's going on is an exercise in futility Good luck with it

To add to your reply Max. For me anyway, VA can be exteremely hit and miss in what it recognizes when it comes to number ranges. With my own profiles, with some commands I can use a wildcard to input a number some not. Others the ".." will work then others I need to place all the numbers into the group. The final one in itself presents a problem for me as the numbers need to be placed with a "0" prefix to work reliably (I have no idea why). For example [0..3] has to be replaced with [00;01;02;03] however that then sends the zero too which Vaicom doesn't recognize. I tried that as an experiment and VA recognized the Select and number, but as the command itself is peppered with zeros Vaicom doesn't recognize it. I then thought about using the Wildcard as an input but that can't be used as Select is already a command so using Select* doesn't work as VA sees Select & Select* as the same syntax and will not let you use it.

I was wrong the command is fine, but I think the problem is the syntax used for the ranges example [1..3] Although the ".." should work according to the VA manual to specify a range. I frequently have problems using this type of syntax and there isn't any rhyme or reason I've figured for when it works and when it doesn't It's probably working great for Hollywood, but I actually get "select 253.0" registering as unrecognized in the Voice Attack command window. Clearly VA has recognized what I've said but the command isn't triggering. Yes I have the Radio control commands in the Vaicom profile

You can put in custom text in place of the value returned by default Refer to Ctytler's videos

Had a quick look at this, like both Max and you, no joy. I think the syntax is messed up in the Voice Attack command, so I don't think it will ever work as intended As nobody (except Hollywood) knows what Vaicom is looking for changing it in the VA profile is a fruitless exercise...........I tried and failed miserably If there is a specific aircraft that you want to call out frequencies for, then I've got a command that works for some, but not inside Vaicom, you need to append it to Vaicom and it'll work. Bailey's profiles also incorporate a frequency select comand, so if you download his profiles you could extract the command from there and append it to your Vaicom profile https://forums.eagle.ru/showthread.php?t=242416 Shout up if that's not clear

Got a problem that's surely been encountered before Got a DCS server on a seperate computer that both a buddy and myself fly on To get on that server I have to use my local IP, my buddy my WAN address I've got that hooked in with SRS and got the sever for SRS on that machine too My problem is although I have my local IP plugged into the "Favourites" for that server in the SRS Client, it works for a while then kicks me When I look at the server address in the DCS SRS Client window I see the server address has changed to my WAN address, which I can't use as I'm on the same network. I can retype/copy paste my local address back in and it will reconnect but it's a PIA. Why is it picking up the WAN address and is there a way to disable it from doing so? Asking here as I'm not on Discord and would rather not install it unless I have to

As you've found out there are many (probably too many) ways to configure SRS & Vaicom and get them to work. I'm sure many use the Vaicom automatic settings to trigger SRS after a command and save yourself using another using another button. I couldn't get it to work to the point where I was confident I wouldn't be screaming Vaicom commands with SRS active and sounding like a complete dork over the airways. So my personal and I emphasize personal choice, is to set Vaicom up so my radio selections in Vaicom PTTs also tune the SRS frequencies. However my PTT for SRS is standalone and completely separate from Vaicom. That way I know for sure if I'm using SRS or Vaicom As far as the menus popping up, that always happens after an update. The accepted fix AFAIK is to exit DCS close & restart VA/Vaicom then open DCS again, after that the menus don't pop up

Ok checked it Large slice of Humble Pie for Weegie. The radar is still Ok, thanks for chiming in Bagpipe. It was great to see it working dunno what I did, probably just goofed up on the lighting To be fair the HUD is not too bad, but that dammed Taxi, landing light is non existant

Not sure but it could be server config? I believe server Export settings can be disabled on the server end. Could that be the issue?

Thanks I'll revisit it, would be great if I'm wrong as I seem to spend most time with the Viggen

There are quite a few things still wrong with the Viggen and it took me a bit of time to sort some of them out. I'm not carping it's a fantastic module and it was a bold step of HeatBlur to produce it and I thank them for it. It is just so different fun and quite challenging is some respects yet very simple to operate in others. Real Swedish design and out of the box thinking, love it. The main problems I'm having with it at the moment though do affect my love of the module and that's the lighting implemented by ED seems to wreaking havoc on the Viggen. The Radar, HUD and the landing/taxi light could do with a fix sooner rather than later The HUD almost seems to mist up, from time to time The Radar is all but unreadable, just a green or red glow with few features (which is real shame as in original form when launched it was a game changer at the time) The taxi/landing light is non existant from inside the pit. All the other stuff I can live with until Heatblur get around to it, but I'd love to see the lighting issues addressed

Title says it all Had the Viggen since day one and even though its still got some stuff to sort out absolutely love it But after all this time I've only just fully understood how to set the parking brake...................Jeez

I had a look but was struggling too, if in doubt try different configs eg: Rotary button etc: I've found some commands where Rotary works buttons don't sometimes switches Thanks though good of you to post the solution appreciated

Bit late here but you can easily add toggled functions using Voice Attack. The downside with VA is you need to send the game keyboard strokes. That doesn't bother me in the slightest but I know some don't like it On my setup I use TARGET and VA, TARGET for the stick and VA for the throttle (Winwing Taurus). When I "SHIFT" in TARGET I send out a Dx button down out from TARGET that VA picks up. "UNSHIFT" a different button down and the "SHIFT" BUTTON up. You could easily do it with just one Dx being up or down depending on the "SHIFT" state. To "SHIFT" (or any other mode you require) simply make a Boolean constant called Shift as an example. Make a command that has "Shift" envoked (True) when a Dx is sent, or a button pressed on the device, if you prefer. For "UNSHIFT" a separate command but it makes "Shift" false, it is invoked using the same Dx or button, but tick the invoke when all buttons are released You can then add that Shift vairiable to your command. Your commands can then have buttons that don't care about the shift state, or only operate when Shifted or Unshifted. You can make as many Shifted or modes states as you want, using the same sort of logic. I also added in short tones for press and release so as I know which state I'm in, Works pretty well for me. Voice Attack can also operate a Double Tap or a Tempo presses too. I really like Voice Attack and find it both flexible annd reasonably reliable.

Simon Pretty sure Bailey has a profile for the Hornet & Gazelle Which you can find here, Oh and the free TF-51 https://forums.eagle.ru/showthread.php?t=242416 I've got one for the Hornet I'd gladly pass on if it would be any use, although I'm more into flying the thing than the weapons. My profile for the Hornet doesn't do weapons but has radio and Tacan codes for airfileds in Caucasus, Nevada, Gulf and Syria, not sure what Bailey's covers but it is a great profile for sure. You can mix and match the profiles to pick the stuff you want and drop the stuff you don't (or you can run them both at once, that may give some conflicts but nothing beyond the wit of man to sort out) Drop me a PM if you decide to get VA think it's about $15-20 If you need asistance with it I'd be only too happy to help, I'm no expert, Bailey is very knowledgable and I'm sure he'd help too John

Simon I don't know what modules you have (if any) I don't have profiles for the Su-25T or the TF-51 if you are flying the free modules, but I'd be more than happy to make you some up if want. You'd need to tell me the kind of things you're after. There are also some made for the P-51 by Bailey (another member who produces fantastic profiles) and the TF-51 is not so different just no guns that's all If you have some purchased modules post up what you have and I'll see what's avaialable either from Bailey or me There is also an Addon to Voice Attack called Vaicom that's a paid plug in and probably only applicable if you really get hooked on the sim Check out You Tube for Voice Attack and DCS and you'll get many videos showing what it can do and how to set it up. Here is just an example of one of my profiles..................and a programmer I am NOT, the video was made for another guy on the forum. I have Vaicom up in that video (the little pop up box in the top right) but not using for any of these examples Just a thought John

Hi Simon Like most I have no clue about the device but first welcome to the whacky world of DCS. If you like crashing a lot and getting frustrated when starting then it's the Sim for you, took me to land the Frogfoot. Anyway I digress, I looked at the documentation but still getting my head around it. First thing to check is Windows seeing these button inputs, if it's not then that's the first thing that needs to be sorted Control Panel/Hardware & Sound/Devices & Printers/ Right click on the device and Choose Game Controller Settings, that opens a box choose the device and hit the properties button to see if these buttons are being recognized. I don't know how your disability affects you're speech, I hope that's not offensive it's not meant to be. I was just wondering if Voice Attack would be of any help to you as input device, it's a reasonably cheap piece of software that allows users to input keyboard commands via a speech input. Good for buttons, useless for axes I could be teaching my granny here, but just offering some options which might be helpful. Post away I'm sure lots only too willing to help John

Seems to be MAX time will tell of course Much indebted for your assistance many thanks

Ok I downloaded a fresh install & at first nothing just the same. However after a few times running the game, loading and reloading the luas etc: it started working. I then had the problem with Vaicom not recognising the Radios #1 & #2 well they clicked on then right off again but the Interphone and Aux were working as they should I just messed with some of the profiles clicking between them then loading and reloading DCS and Vaicom and that came back too I wish I had a decent explanation as to what I did, but it was all bit hit & miss loading and reloading the luas. All I know is that it's working MAX many thanks for all your peresverence and help & sthompson for pointing me to the manual for the "manual" install, which I also tried but eventually went back to letting Vaicom do the work

RTFM Weegie......................Thanks sthompson I tried contacting Vaicom but got the dreaded "Not Reproducable" reply although they did give me all the usual stuff to do nearly all of which I had completed already The thing I don't understand is, I looked at the backup files that were saved. As I understand it these were the broken files,replaced files. What I did was take a note of their filenames. I then went into my repaired game and extracted the same repaired files in the game and placed them into OVGME. I could now do a repair for this issue by just running the OVGME mod I had made. When I run Vaicom again then take the files as they have been ammended by Vaicom, I see some small differences in the ED code in the these files as well as the Vaicom additions. I have no idea why that happens but that's what I see. I agree it makes no sense whatsoever, these files should not change apart from the Vaicom appended code but that's not what is happening. Further I'm at a total loss as to why it breaks the AutoStart/Stop it just makes no sense. However the fault is completely reproducable for me. I run DCS without Vaicom but with VA after a repair or running the OVGME mod, no problem I can use the Auto Start. If I then start Vaicom (with or without the game running) BOOM!! AutoStart/Stop borked. If I then restart and replace the ammended Vaicom files with the Vanilla repaired ones, AutoStart/Stop works again. I've just completed a Vanilla install of the Open Beta, by deleting both my stable and Open Beta then downloading the Open Beta from ED (what a pain that is it takes forever). What I'm now going to do is delete Vaicom and complete a fresh install of it as well. I'll remove all mods, not that there were that many, as well and take it from there. Of course it may change nothing, I've had odd issues with other software before (not DCS related) where something happens that's just inexplicable and either a fresh install or it's years down the line I find the reason for the problem. My VKB software was a good example of this, but I digress I have already started to make my own Auto Start VA files, but that takes a long time to do, especially for the modern jets. However I do think it's the way to go.

Oh forget that we all make mistakes me more than most. The help is more than appreciated, it was just nice to get to some sort of resolution about what was going on. My bet is that it's probably down to just one line of code in one of the luas and everything else is fine. However the whole thing is really fragile, which is annoying. Perhaps when Hollywood brings out an update this might get fixed for me. It does intrigue me that nobody else seems to be experiencing this and it's just my setup. Like you say I've got a workaround and I'll work on doing my own Autostarts with VA, however that's going to be a heap of work. Oh Bailey's profiles just use the DCS Autostart feature. If I get them done I'll post up the profiles. The amount of work for the TACAN, ILS and all the radio frequencies was considerable alone and although Vaicom can do that too, it might be nice to share them so others don't have to go through all the pain of making up over a hundred commands to dial in an airbase and talk to the tower, or use the ILS and TACAN, in case Vaicom starts to play up, as it can do from time to time

Ok So I've been looking at what happens and it's above my paygrade and intellect. As an side this may interest you if you don't know about it already a File Comparison plug in for NotedPad++ (my prayers were answered) https://sourceforge.net/projects/npp-compare/ I haven't looked at every lua yet but it would appear that Vaicom puts a whole heap of code in after the conventional plug in code, I also noticed some changes to the Vaicom luas and the ED luas in the ED code itself, it's very strange but as some of it is in Cyrrilic so it's kinda hard to fathom The problem is I don't know where the Vaicom luas are stored so I can't make changes. I'm thinking everytime Vaicom loads it may append these or even replace these particular luas, which sort of leaves me stuck for now. However what I can do in the meantime is start an aircraft, then load Vaicom. So I can go onto Multiplayer in the meantime start my bird, then start Vaicom and away I go. When I want to start again I need to shutdown DCS run the OVGME and start again, in theory OVGME keeps the original files so no matter how many times I break it, I can just run the OVGME file and I'm good to AutoStart again. I'll still look into this some more especially the Dx buttons and radio keys in the DCS profile and try running Vaicom/AutoStart in the stable version to see what's going on I'm also going to look into building seperate start ups in Voice Attack as I prefer to have something that I'm not messing with all the time and isn't so dammed fragile that it breaks at the drop of a hat Thanks again for all the help so far, I'll report back on the buttons and running in stable later

Yes I do MAX got a Vaicom profile for every aircraft so as I can shuttle between my appended profile exclusively and Vaicom with the appended profile. Pretty sure I have all these buttons disabled in the DCS profile for the Txs I use in Vaicom but I'll double check it. Also unmapped my radio key as well but I'll double check them for say the Hornet and work exclusively with that module to test the AutoStart. The extra stuff is for the StreamDeck using Icarus to export data to the StreamDeck and it all seems to be working fine. The AutoStart and AutoStop are broken neither work. I'l try the stable just to see what happens there. In the meantime I tried another little experiment. I took note of the files in the backup (in other words the files that DCS replaced after the repair) and then did a Repair. After that I duplicated the folder structure and loaded the new files that were replaced from the repair into the folder structure. So what I ended up with in theory anyway was the new files and folder structure that DCS Repair had replaced. Then I zipped it and put it into OVGME. Started DCS to check the AutoStart, all good, shutdown DCS, ran Vaicom to deliberately break the luas. Stopped Vaicom then ran the OVGME file, started DCS and AutoStart still worked. Stopped the OVGME loaded files and reran, and it was broken agian. So that's working (in theory anyway) Now going to have a look in the luas to see if I can spot a change in the files before and after I've ran Vaicom

I thought it would, this is something specific to my setup although I cannot think what I've got in there is so different MAX Export.lua attached Export.lua

I'll download the Configuration Manager Trace Log Tool. It sound handy anyway I had debug enabled earler and turned it off in a vain hope that it might be causing a problem. No joy, checking the Vaicom log showed everything was fine as far as Vaicom was concerned The DCS log is a bit of a nightmare, as there are obviously things which don't load etc: and are more concerned with what ED are doing. However I'll do a vanilla install and get the log them implemet Vaicom and rinse and repeat. I can then compare the logs looking for differences. Your assistance is appreciated, but please, when you get to it, you get to it. I've got options and some more investigating to do in the meantime