Weegie Posted September 9, 2020 Posted September 9, 2020 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?
MAXsenna Posted September 9, 2020 Posted September 9, 2020 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? Can't see why it would as VAICOM doesn't send any key inputs. It talks directly with DCS through the network, and for the time beeing only works with radios and comms. The sound mod for the Viper is a mod. VAICOM is not a mod. Cheers! Sent from my ANE-LX1 using Tapatalk
Weegie Posted September 9, 2020 Author Posted September 9, 2020 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
Weegie Posted September 9, 2020 Author Posted September 9, 2020 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
hornblower793 Posted September 9, 2020 Posted September 9, 2020 I have just tried autostart for the Viper with Vaicom running (plus all extensions) and it worked fine - running latest OB standalone Windows 11 Home ¦ Z790 AORUS Elite AX motherboard ¦ i7-13700K ¦ 64GB Corsair Vengeance DDR5 memory @ 5600MHz ¦ Samsung 990 Pro 1TB SSD for OS, Samsung 980 Pro 2TB SSD for DCS ¦ MSI GeForce RTX 4090 Gaming X Trio 24GB ¦ Virpil WarBRD base with VFX grip, Thrustmaster A10c and F/A-18 grips ¦ VKB Gunfighter Mk4 and MCG Pro ¦ Thrustmaster Warthog Throttle ¦ VKB STECS Throttle ¦ Virpil TCS rotor base with Shark and AH-64D grips ¦ MFG Crosswinds ¦ Total Controls Multi-Function Button Box ¦ Pimax Crystal
Weegie Posted September 9, 2020 Author Posted September 9, 2020 Thanks I'll try reinstalling the luas see if I have any luck
Weegie Posted September 9, 2020 Author Posted September 9, 2020 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
hornblower793 Posted September 9, 2020 Posted September 9, 2020 Welcome to technology:D Windows 11 Home ¦ Z790 AORUS Elite AX motherboard ¦ i7-13700K ¦ 64GB Corsair Vengeance DDR5 memory @ 5600MHz ¦ Samsung 990 Pro 1TB SSD for OS, Samsung 980 Pro 2TB SSD for DCS ¦ MSI GeForce RTX 4090 Gaming X Trio 24GB ¦ Virpil WarBRD base with VFX grip, Thrustmaster A10c and F/A-18 grips ¦ VKB Gunfighter Mk4 and MCG Pro ¦ Thrustmaster Warthog Throttle ¦ VKB STECS Throttle ¦ Virpil TCS rotor base with Shark and AH-64D grips ¦ MFG Crosswinds ¦ Total Controls Multi-Function Button Box ¦ Pimax Crystal
MAXsenna Posted September 9, 2020 Posted September 9, 2020 Hehe! You're totally right! Happy for you though! Sent from my ANE-LX1 using Tapatalk
Weegie Posted September 9, 2020 Author Posted September 9, 2020 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
MAXsenna Posted September 9, 2020 Posted September 9, 2020 Well, when VAICOM re-builds the export.lua, I think it puts a folder and a some files in the install folder of DCS. And that's why it breaks after every update/repair. And one has to go and either delete the export.lua or reset it in the VAICOM control panel, and then restart VA, so it can recreate those folders and files in the DCS install directory. I think that's why you see such a "small" repair. Because it's just some Lua files. Basically text. Hmmm Sent from my ANE-LX1 using Tapatalk
MAXsenna Posted September 9, 2020 Posted September 9, 2020 Just a quick question. You start the autostart with the keyboard of course. Not by some command in VAICOM/VA or macro keyboard or similar? I have never tried autostart, so I don't really know how it works. But I know some people actually have made full autostart commands in VA or autohotkey, that both works better and faster compared to how it is implemented by ED. Are you using stable or OB, and what's the autostart key combo for Viper and Hornet? I can check my system if you want. Sent from my ANE-LX1 using Tapatalk
hornblower793 Posted September 9, 2020 Posted September 9, 2020 Max - the key command is easy to find - look for Auto start in the commands list for the viper (I think it was LCTRL + Home) Windows 11 Home ¦ Z790 AORUS Elite AX motherboard ¦ i7-13700K ¦ 64GB Corsair Vengeance DDR5 memory @ 5600MHz ¦ Samsung 990 Pro 1TB SSD for OS, Samsung 980 Pro 2TB SSD for DCS ¦ MSI GeForce RTX 4090 Gaming X Trio 24GB ¦ Virpil WarBRD base with VFX grip, Thrustmaster A10c and F/A-18 grips ¦ VKB Gunfighter Mk4 and MCG Pro ¦ Thrustmaster Warthog Throttle ¦ VKB STECS Throttle ¦ Virpil TCS rotor base with Shark and AH-64D grips ¦ MFG Crosswinds ¦ Total Controls Multi-Function Button Box ¦ Pimax Crystal
MAXsenna Posted September 9, 2020 Posted September 9, 2020 Max - the key command is easy to find - look for Auto start in the commands list for the viper (I think it was LCTRL + Home)Aha. Thanks. I was being lazy though. Hehe Sent from my ANE-LX1 using Tapatalk
Weegie Posted September 10, 2020 Author Posted September 10, 2020 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
MAXsenna Posted September 10, 2020 Posted September 10, 2020 Hi Weegie! Had too fun flying Larkins in Syria yesterday, so I didn't get to test anything. Sorry. How do you do a repair? And when it asks you to keep files. Answer yes, and you'll have them in "backup" in DCS install dir. But I guess you knew that already. Download Bailey's VA profiles. Maybe there's an autostart in there already, but if not, all the keys and switches are defined. So just make a new command, and just add what you need. Remember timings!!! Anyway, just checked. VAICOM adds a "Scripts" folder to the install directory, with two folders "Speech" and "UI", and some folders and files in those. What release and version of DCS are you running. And have you tried to revert to another version. I'm pretty sure you wrote in another post when it stopped working. Viper sound mod thread? Did it actually stop then, or did you just notice at the time? What other changes happened around that time, if any? Sent from my ANE-LX1 using Tapatalk
Weegie Posted September 10, 2020 Author Posted September 10, 2020 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
MAXsenna Posted September 10, 2020 Posted September 10, 2020 Alright! I will test myself. You pretty much do things the way I do it. Your words pretty much describes my work flow. Settings are equal as well. Except that I have debugged checked. Not that I believe it will give you any clues this time. Next step would be for me to check the DCS log. There are tools one can download, (log viewers), that will display the log in real time. I use the one from Microsoft System Center Config Manager. But I know it possible to download it. Its called Configuration Manager Trace Log Tool. It's excellent. It will highlight errors and warnings etc in red and yellow, so it's easy to see what's going on. Maybe there's a clue in that log. Worth having a look at at this point IMHO. Sent from my ANE-LX1 using Tapatalk
Weegie Posted September 10, 2020 Author Posted September 10, 2020 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
MAXsenna Posted September 10, 2020 Posted September 10, 2020 Yup. Testet the F-18 now. No issues. Only entry in the log when I got in the cockpit was from TacView, and when startup was finished successfully. F-16 is starting now. Btw. How does your export.lua look? Sent from my ANE-LX1 using Tapatalk
MAXsenna Posted September 10, 2020 Posted September 10, 2020 Okay. F-16 started as well. But it seems to claim it is finished before alignment is. Maybe it's supposed to be this way. Sent from my ANE-LX1 using Tapatalk
Weegie Posted September 10, 2020 Author Posted September 10, 2020 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 attachedExport.lua
MAXsenna Posted September 10, 2020 Posted September 10, 2020 You have some more stuff there compared to mine. I have SRS, VAICOM and TacView, in that order. Read somewhere that Tacview wants to be last, but I cannot see why that should make a difference. I have only those three entries, no spaces or line shifts between them. But this used to work for you, and suddenly it doesn't. Do you still have stable installed? Just to see if it works there? Also, I forgot to ask. Does the autostart start and stops, or doesn't start at all?
MAXsenna Posted September 10, 2020 Posted September 10, 2020 I just plugged in my Cougar, and Voice Attack crashed. Now, I'm using the radio switch(es) on my TQS as TXs in my VAICOM Viper profile (of course), so I guess that's what happened. And it made me think. Do you have more than one VAICOM profile? Could some of those defined TXs (weather it's keyboard keys/combinations) conflict with anything in DCS? I have removed all keyboard keys in my TXs. And I have unmapped any radio key in DCS from every module. Sent from my ANE-LX1 using Tapatalk
Weegie Posted September 10, 2020 Author Posted September 10, 2020 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
Recommended Posts