Darkxv

Thanks, fixed everything. Appreciate the news.

Hey there, I have been using Vaicom Pro with Voice Attack for DCS for a little over a year. Recently I updated DCS world and Voice Attack(I believe the problem is voice attack), and no matter what commands I give, or how I give them, they will be recognized but will never be confirmed or sent. I will continuously get 'awaiting additional input.' Never had this problem before. It is quite frustrating. Just want to be able to use Vaicom Pro again. Any ideas? Additionally, lately anytime I run DCS I have to repair it before hand or I will not be able to get the communications menu to show up and work. The communications menu that has ATC, Flight, AWACS, etc... that you use to communicate where to land, air-to-air refueling, command AI to engage bandits, let ATC know you're inbound, etc.. ----> I believe Voice Attack or Vaicom Pro is what is causing this issue and is probably related to the other issue above.. Or maybe it is not, but just one of a couple different issues making it impossible to use Voiceattack/Vaicom in DCS right now. Regards,

thanks for the post. sorry for late response. I have adjusted the missions and coalitions. also tried tuning manually but when i try and talk it will switch back to North Las Vegas, the only airfield that seems to work with the plugin. Hopefully someone figures this problem for me eventually.

To Whom Can Resolve this Issue, I've been having a problem with VAICOM PRO recently where it cannot find any of the airfields on the Nevada Test and Training Range Map except for North Las Vegas. All commands work great, and everything seems to be in fantastic working order except for this problem where its unable to tune into any airfields on NTTR. It reads: "3:58:25.204 Recipient McCarran International Airport is currently not available." "3:58:07.205 Recipient Tonopah Test Range Airfield is currently not available." "3:58:02.186 Recipient Nellis AFB is currently not available." .... and all of the other airfields give the same error in the debug menu I've incorporated the log file below... *****Additionally, on the Caucus Map I am able to select and find all airfields just fine. That being said I have only tested Caucus and Nevada, and is likely I may run into same problem on the other maps like Syria, Persian Gulf, Normandy, Mariana's, and/or the New South Atlantic Map.***** Any Solution's will be extremely appreciated. This is an awesome plugin for VoiceAttack and won't give up on it. Best, VAICOMPRO.log

I see.... Welp.. guess well just have to pray that the new FLIR Render update gets these agm-65's to stop liking the ground. Thank you for the help Tholozor and Deano. I appreciate you checked out the tracks and verified I'm not just crazy lol.

Yes, I know it has a FOV and I used it in my tracks Listed above. I mean a zoom function added too the FOV function. Like on the TGP... You have wide/narrow FOV and Zoom for both of them.

So you don't think there's possibly the lucky chance my game files could have something to do with it? Do you experience this similar phenomenon? Man it would be the dopest thing for christmas if they figured out whats happening or added a zoom function to the maverick seeker head or something, or just fixed whatever it is.... idk.... I just wished my mavericks would hit the targets I locked them onto that's all. It's already tough enough having to go back and forth between the TGP and WPN.. now I have to adjust the target crosshair above the targets after switching back and forth with only 12 miles to go going 450 to 650 knots...... gosh.... very hard work... good thing in that quickstart there weren't any intercepting bandits around.

I've been having problems with the AGM-65 maverick flying the f-16. I recorded tracks of me demonstrating the issue. It seems the seeker likes to lock the ground below/infront of targets. Here are the tracks attached below The first, where I just leave it to do its thing and auto handoff the target with the TGP. Youll see the agm-65 does get a lock but for some reason its locking the ground below and skewed off to the side of the targets... there are two targets I fire agm-65's at, and they completely miss and hit the ground. and a third target i drop a laser guided gbbu-12 on. the second track, is where I do the same exact run, but this time manually adjust the agm-65 track by slewing it above/behind the target and then hitting tms short/lock. I do this with both the first and second targets, get direct hits.. and again drop gbu-12 on the third target. This is not the only case of this. I've had the same experience in other instant action missions, other missions, custom missions, and even from ground starts where i boresight my tgp with the agm-65 seeker heads. It absolutely needs to be fixed if it is a bug, or if its just me and my installation and files that need to be fixed then please help me figure out how. Not all targets are easy to make adjustments on like these. Instant Action - Precision Preemption - No AGM-65 tgt adj.trk here is the second file below where I manually correct it by targeting above/behind the target to get an accurate lock Instant Action - Precision Preemption - with AGM-65 tgt adj.trk