Weegie

No problems at all MAX, I have so much fun with it too, that's why I'm determined one way or another to get it running Never thought of keepiing the files I do know about it but never thought to look at them. Checking now I see whenever I did the repair (about 30 times) the backups for the repair appears to be saving the same things every time. The jester AI scripts are getting replaced Mods\aircraft\F14\Cockpit\Scripts\Jester AI\init.lua and JesterAI_Page.lua and Scripts\Speech\common.lua and speech.lua and Scripts\UI\gameMessages.lua and Scripts\UI\RadioCommandDialogPanel\RadioCommandDialogPanel.lua and TabsheetBar.lua That's a great start as I've got something to go on and can try comparing these luas with a repaired version (Another Repair SIGH!!!) to see what lines are changing I'll check Bailey's scripts it would be nice to have separate start up profiles anyway. I try to have redundency where I can, for instance I've got commands for all the radios, TACANs and ILS for the modules I have for Caucasus, Syria, Nevada and Gulf. My VA profiles are already quite extensive. Usually for the repair I use Skatezilla's tool, which as far as I can see, is simply calling the DCS Updater and implementing it. As for the sound mod yeah that's when I discovered the Auto Start was broken. I wrongly assumed it was the Mod, but that was coincidence. It may have been broken for a while as I've been flying the Viggen a lot and it uses a differrent setup to ED modules to Autostart the jet. Since I discovered it was VA/Vaicom I stopped all other mods in OVGME, moved all mods out the Saved Game folder, leaving only Vaicom script files and retried. Sure enough Vaicom broke the AutoStart. I also tried VA on it's own not implemeting Vaicom and the AutoStart worked. I'm not stone cold sure but I gotta be 99.99% that it's something in Vaicom script that's breaking my setup I'm currently running the latest OpenBeta v2.5.6.5046 and I do have a stable version in the same saved games folder that I haven't ran in ages, I'll update that too in case something is getting carried over. Haven't tried to roll back yet, but that is probably in my stars Here is a screenshot of my Config

Thanks for helping, I'm lazy so usuallly cannot be bothered learning all the start up procedures for all the modules I have. MAX I've tried it mapped to a switch and manually using the keyboard. Once it started playing up I've been testing exclusively with the keyboard. The command for the Viper and Hornet (and nearly all the rest) is L_Win+Home as already said. I haven't tested all the other modules but I think it breaks the Auto Start for all the ED modules and perhaps some or all of the 3rd party too. The 2 I've tested are the Hornet and Viper, both broken I agree that it's probably just a lua file and a few lines of script but not having a repair log is so dammed annoying. If I knew what was being repaired I'd know what was getting ammended. Then I might have a chance. I'll look to see if I can ascertain what Vaicom places into DCS itself Yeah I made a start up in VA for the Viggen and it worked a treat, the Viggen is probably the easiest to start of all, but as I can't do without Vaicom, if I don't fix it looks like I'll be spending a few days writing VA commands to auto start the modules one at a time

Well it's sorta working still flaky though after a few starts I'm still having to repair, damm thought I had it sussed Completely removed Vaicom and reinstalled but still no joy Just cannot understand what on earth is going on, the repair is very small it tells me it loads 0.2 MB. If I knew the file that was being corrrupted I might have a chance but it doesn't

Ok I just reset the luas for Vaicom from the Vaicom Reset Window and after yet another repair seem to have the AutoStart back up and running and everything seems to be back to normal WHEW!!! I've been at this a good bit of the afternoon trying to isolate what was the problem Just shows that even although Vaicom can't interfere with other functions in theory wierd things can happen that shouldn't

Thanks I'll try reinstalling the luas see if I have any luck

Ok took everything out the MODS folder except Vaicom Disabled all other OVGME mods Repaired DCS and confirmed it all works. Came out DCS started Vaicom only, no piggybacked profiles, restarted DCS no Auto Start. I'm not saying it's generic to Vaicom but whatever is happening when I start Vaicom is definately screwing somehow with the Auto Start

I hear you MAX but I cannot understand it. I disable the Plug in Everything works, I enable the plug in and the AutoStart breaks, Oh it's not just the Viper I just tested the Hornet and it's exactly the same, probably all the modules with the exception of the Viggen (which is VERY different) At the moment I have everything (including the Viper Sound mod running and Vaicom disabled and the Auto Start works a treat) I enable Vaicom BOOM no Auto Start. Next is to disable everything except Vaicom and then test to ensure something isn't conflicting along with Vaicom and causing it

I thought that this was at first another mod but I've been going through all my mods and the other programs I use (StreamDeck and TARGET) All of these don't break the AutoStart for the Viper but I found when I started Voice Attack the AutoStart on the Viper no longer worked. I then needed a repair, to get it operational again and starting VA would break it After messing about some more I disabled the Vaicom plug in, restarted Voice Attack and tested, the AutoStart still worked. Could have it wrong but it looks to me that when I run the Vaicom plug I'm losing the AutoStart for the Viper, I haven't tested the other modules yet Any ideas?

I just disabled Vaicom then did a repair and restarted, with the Vaicom plug in disabled and Voice Attack running, the AutoStart works fine So it would appear, at least for me, it's Vaicom that's breaking the AutoStart. A little strange as I thought if this was generic problem then it would have been reported already

Thanks BIGNEWY I can get it to work if I do a repair but don't start Voice Attack Guess I'll just to need to keep experimenting to see if I can narrow down what on earth is going on If I find anything I'll report back

Turns out it's not the mod, the only repeatability I can get of the fault is when I run Voice Attack it seems to break the Auto Start. Doesn't matter which profile as soon as open Voice Attack it fails I've attached a track, please take a look and see what's going on I'm stumped FA-16C auto start.trk

You're right there is something else going on with my Auto Start (although I have no clue what) Mod is unrelated to the problem, my apologies Thanks

Ok I'll give it another try. I noticed that the Auto start stopped working after I installed it. I disabled all my other mods, removed the sound and did a repair and the Auto start worked. When I then replaced the sound mod, without enabling any of the others the Auto Start would no longer work I do hope I can get it to work because it's an absolutely fantastic mod and thanks so much for doing it, really appreeciate all the work I'll report back later

Is this in MP? What are you settings for MP in the Vaicom Pop Up? Is the RLY light illuminating, I'm thinking that this might be connected with the Auto PTT in Vaicom. Personally I don't use it and have a seperate PTT set for SRS

Just a word of warning & it's a pity because it's an awesome mod When I installed it, it broke the Auto Start/Stop. Fine for all you guys who start the jet manually I guess but I haven't learned it sufficiently yet

Ok Just checked I think it's hubson's Audio mod that breaks it https://forums.eagle.ru/showthread.php?t=285215 Be nice if it was checked, pity I can't run it it's an awesome sound mod

Ok BIGNEWY Just did a repair and it seems to firing up fine, no idea I'll try to implement the mods I had running one at a time and see if it breaks If it does I'll report back Many thanks for the offer of assistance greatly appreciated

Ok not much to see and only lasts a few seconds in the cockpit pressed L_Win+Home nothing also mapped the Auto Start to a switch tried that nothing Why do I get the feeling I'm missing something FA-16C auto start.trk

Usually I start with the Viper running But today I tried the AutoStart from the ramp L_Win+Home Nothing happened and I didn't see any threads on it being an issue, so wondering if it was just me

That's not a problem check my location,:music_whistling: If you are having problems getting recognized you need to do the Windows Speech training and more than once. There is also training in Vaicom to get the Speech Recognition to understand all the Vaicom commands too. It takes a little while and is a PIA but it makes a BIG difference. Some phrases work better than others in Voice Attack however with Vaicom if you find a phrase doesn't work for you, you can change it in the database or add other phrases that will execute the same actions It's not initimidating really it's is like anything, go slow the first time you do the Database update and have both the Voice Attack and the Vaicom manual to hand just in case. Once you've done it once it becomes second nature. The problem is that Vaicom is a plug in to Voice Attack so you're really dealing with 2 pieces of software. I've got a reasonably large profile sitting "piggybacked" or appended to Vaicom as well and it works a treat. Voice Attack on its own without Vaicom is really powerful, add Vaicom and it really is amazing. With my VA profile I've integrated a lot of my hardware for some aircraft and its great. Just take small steps with it, there are loads of things in Vaicom I've yet to delve into and I've had it for ages. If you need help just post away, the forum is really good lots of help from people a lot more knowledgable than me

I'm not really sure but do you have the Imoprt F10 Menu checked in Preferences? According to the manual the words are added and executed by using the "Action" prefix. Haven't tried this myself though but thought it was worth posting just in case

First is Salute getting recognized? Check the main VA (not Vaicom) window and see when you say Salute its showing in the VA command window as being recognized Salute should be in the database Open Voice Attack (and select Vaicom if it's not selected already) L_CTRL+L_ALT+C, should open the Vaicom Window, with the PTT tab open (looks like this) Click on the Editor tab, all the butons should be grey, if any are orange you need to click on them to action (I'm thinking either Reload or FINISH). You should see "command list" and a drop down, left click and scroll down to see if Salute is there, commands are listed alphabetically. If it isn't then try a reload, by clicking on Reset in there tick Keywords only (make sure the other boxes are not checked)and then the Master Zero and try again After that you need to ensure the words have been added to the VA Vaicom profile. You also need to check the keyword is also in the VA listing as well. Go to the main VA Window Open the cmd window Delete that list and CTRL+V to download the new list that's already on the Clipboard It's all explained pretty thoroughly in the Vaicom help document, which is VERY helpful and worth a read. Vaicom isn't difficult but it's pretty packed with features and needs some time to get to know I also find that the Supercarrier can be a bit hit & miss at times and unless you exectute the Salute command at the correct time you'll just be left sitting there on the cat. One more thing if you go to preferences in the Vaicom Window and check the Allow Options box. This means if you can't get VA/Vaicom to work you can try saying "Options" this then brings up the DCS on screen menu. After that "Take" (for instance if you want to select F5 you say "Take 5") will select the various functions in the menu. That way you can see if the problem is Vaicom/VA or DCS Hope that helps a little

Thanks for posting the fix appreciated

Yup agree I answered to a somewhat similar question that may allso assist https://forums.eagle.ru/showthread.php?t=285082 You'll see in that response that I'm now saving profiles before an update, as I think if any modifications work are done to the Keyboard.lua in the game itself the diff.luas aren't recognized and reset everything to default. Unless you check before you exit after the update the defaults are saved and you lose the keybindings. Hence the reason for keeping a backup. Not 100% on that but I'm not the only one to suddenly find that I've lost all my bindings after an update and its really annoying

Solved I was using the same PTT button on the throttle for both the AUX in Vaicom and the piggyback profile. So it was being sent twice and must have been causing a conflict. Now moved the piggyback profile to an Open mic when using Vaicom and a seperate PTT button should I want to use it standalone That's stopped the Command canceled: Another command is not allowing others to execute (canceled: Transmit TX6 press) and the Vaicom PTT page now shows AUX in the window when activated Thanks for helping MAX must appreciated