SugaFoYoPancake

I tried updating DCS today to the newest branch but I'm unable to due to this error. This occurs when the updater app is downloading the version info for the installer, but it never finishes the download and "file is not a database" error message pops up and the update fails. I've tried updating through the regular application, Skate Zilla's Updater Utility, and through the CMD prompt but nothing has worked. Attempting to repair and clean DCS also has the same issues and both fail when the try to download the version info. I've also downloaded a new instance of the updater app but that also did not work. autoupdate_log.txt

Hey Hollywood, firstly I'd like to say how great this plugin is. I've been using for quite awhile now and it's made interactions with AI smooth as silk. But lately I've been having issues. It first started with some registry entry issues when I moved DCS to a separate SSD, but I eventually got VAICOM working again with some edits to the entry. But now I can't get VAICOM to recognize alot of recipient names. Essentially every Caucaus recipient name no longer is recognizable and it just reverts to the closest ATC when I first load in to a mission, regardless of what my radios are tuned to. More specifically, this is generally what pops up in VA when I make a call to an ATC: 7:20:16 PM - TX1 | VHF AM: [ ATC ],[ ],[ ] Inbound [ ] [ ] 7:20:16 PM - Constructing message... 7:20:16 PM - Unspecified recipient called: using default unit for this category 7:20:16 PM - Have result, identified as command : Inbound 7:20:16 PM - Captured sentence: inbound 7:20:16 PM - Recognized : 'inbound' 7:20:15 PM - Listening suspended 7:20:15 PM - Joystick : 'Transmit TX1 release' 7:20:14 PM - (awaiting additional input) 7:20:14 PM - Have result, identified as recipient : Kobuleti 7:20:14 PM - Captured sentence: kobuleti 7:20:14 PM - Recognized : 'kobuleti' 7:20:13 PM - Listening resumed 7:20:13 PM - Joystick : 'Transmit TX1 press' Wingman names and some AWACS and JTAC callsigns work, but its very inconsistent in what it chooses to run. Also, NTTR ATC names seem to work more consistently, but only when I say them with little pause between the recipient name and the callout. VAICOM has always worked very well in the past and this only started happening either after I updated to 2.5.5 or after the registry edits. Any ideas on how to solve this?