TheMOP

Sure on the new Super Carrier :) ! Thank you, too, Greyman!

Thank you Hornblower and everyone else for all the effort you put in this to help me! :thumbup:

Hollywood, OMG, that was the solution!!!! Database in VAICOMPRO was corrupted … deleting the two folders solved it! Finally it's WORKING :thumbup::thumbup::thumbup::thumbup: Just tested in DCS and everything seems to work just fine :) Thanks Hollywood, Hornblower and everyone else who supported! Great people, great forum! You would not believe how happy I am right now! THANK YOU ALL SO MUCH!!! THANK YOU ALL SO MUCH!!!

Hi Hollywood, did what you said and used revert & finish button, transferred the keywords to VA. I was surprised because then I got "unrecognized: Batumi" back from VA, which puzzled me. I loaded the vanilla VAICOMPRO for DCS .vap profile again and compared: The keyword list that VAICOMPRO holds is much shorter the keyword list in the .vap profile. To compare: 1. current keyword list in VAICOMPRO (I believe the same before and after "revert"): *Bomb*; *Bullet*; *Dart*; *from the East*; *from the North*; *from the NorthEast*; *from the NorthWest*; *from the South*; *from the SouthEast*; *from the SouthWest*; *from the West*; *GBU*; *Guided*; *Gun*; *Marker*; *Maverick*; *Missile*; *Paint*; *Paveway*; *Pickle*; *Rocket*; *Smoke*; *Stores*; *Strafe* This is quite short and surprisingly missing all the places (like "Batumi") ?! 2. the keyword list in the vanilla .vap file (much longer, containing the places also): *AAA*; *Abort Inbound*; *Abort Refuel*; *Abort Takeoff*; *Abu Dhabi*; *Abu Musa*; *Admiral Kuznetsov*; *Advise Ready for BDA*; *Affirm*; *Air Defense*; *Al Ain Airport*; *Al Bateen*; *Al Dhafra*; *Al Maktoum*; *Al Minhad*; *Anapa*; *Anchor Here*; *Anvil*; *Apply Air*; *Approaching for Refuel*; *Arco*; *Armor*; *Artillery*; *ATC*; *Attack*; *Attack Complete*; *Awacs*; *Axeman*; *Azeville*; *Badger*; *Ball*; *Bandar*; *Bandar Abbas*; *Bandit*; *Batumi*; *Bazenville*; *Beny*; *Berlin*; *Beslan*; *Biniville*; *Boar*; *Bogey*; *Bogey Dope*; *Bomb*; *Bombs Away*; *Bozo*; *Break High*; *Break Left*; *Break Low*; *Break Right*; *Breakaway*; *Briefing*; *Brucheville*; *Bullet*; *Bullhead*; *Cancel Approach*; *Cancel Departure*; *Cardonville*; *Cargo*; *Carl Vinson*; *Carrier*; *Chailey*; *Check my Spee*; *Check Out*; *Checking In*; *Checking Out*; *Chevy*; *Chief*; *Chippelle*; *CLARA*; *Clear Left*; *Clear my Six*; *Clear Port*; *Clear Right*; *Clear Starboard*; *Cleared Hot*; *Close Formation*; *Close Group*; *Close the Canopy*; *Close Up*; *Colt*; *Column*; *Commencing*; *Complete and Rejoin*; *Complete and RTB*; *Confirm*; *Confirm Remaining Fuel*; *Connect Air Supply*; *Contact*; *Contact Sparkle*; *Contact the Mark*; *Continue*; *Copy*; *Copy Kill*; *Copy Miss*; *Copy Nine Line*; *Cover Me*; *Creech*; *Cretteville*; *Crew*; *Cricqueville*; *Crystal Palace*; *Dallas*; *Damage Report*; *Darknight*; *Darkstar*; *Dart*; *Deathstar*; *Declare*; *Descent*; *Deux Jumeaux*; *Directions to Base*; *Directions to Final*; *Directions to Tanker*; *Disconnect Air Supply*; *D-link Target*; *D-link Target by Type*; *D-link Targets*; *D-link Targets by Type*; *Dodge*; *Dreamland*; *Dubai*; *Dublin*; *ECM Off*; *ECM On*; *Element*; *Enfield*; *Engage*; *Established*; *Evreux*; *Exit Area*; *Eyeball*; *FARP*; *Fence In*; *Fence Out*; *Ferret*; *Finger*; *Firefly*; *Flight*; *Flight Kiss Off*; *Fly Route*; *Focus*; *Ford*; *Forde*; *Four*; *from the East*; *from the North*; *from the NorthEast*; *from the NorthWest*; *from the South*; *from the SouthEast*; *from the SouthWest*; *from the West*; *Fujairah*; *Funtington*; *Game Over*; *GBU*; *Gelendzhik*; *Go Combat*; *Go Cruise*; *Go Echelon Left*; *Go Echelon Right*; *Go Finger Four*; *Go Heavy*; *Go Helo Left*; *Go Helo Right*; *Go Helo Tight*; *Go Home*; *Go Line Abreast*; *Go Overwatch*; *Go Port*; *Go Spread Four*; *Go Starboard*; *Go to Tanker*; *Go Trail*; *Go Wedge*; *Go Wide*; *Gopher*; *Graceland*; *Groom Lake*; *Ground Power Off*; *Ground Power On*; *Ground Target*; *Group*; *Gudauta*; *Guided*; *Gun*; *Guns Guns Guns*; *Hammer*; *Havadarya*; *Hawg*; *Heads Up*; *Helos go Echelon*; *Helos go Spread*; *Helos go Trail*; *Henderson*; *Hold Position*; *Hornet Ball*; *Hostile*; *In from the East*; *In from the North*; *In from the NorthEast*; *In from the NorthWest*; *In from the South*; *In from the SouthEast*; *In from the SouthWest*; *In from the West*; *In Hot*; *Inbound*; *Inbound for Carrier*; *Inbound Marshall Respond*; *Inbound Straight*; *Indian Springs*; *Infantry*; *Instrument Approach*; *Interrogate*; *IP Inbound*; *Jaguar*; *Jettison Stores*; *Jiroft*; *Join*; *JTAC*; *Kaemka*; *Kalitka*; *Kapel*; *Keep It Tight*; *Kerman Airport*; *Khanskaya*; *Khasab*; *Kick out to 1 mile*; *Kick out to 10 miles*; *Kick out to 2 miles*; *Kick out to 3 miles*; *Kick out to 5 miles*; *Kick out to 8 miles*; *Kish Island*; *Kobuleti*; *Kolkhi*; *Krasnodar*; *Krymsk*; *Kutaisi*; *Lantheuil*; *Lar Airbase*; *Las Vegas*; *Laser On*; *Laughlin*; *Lavan Island*; *Lead*; *Lessay*; *Lincoln*; *Liwa Airbase*; *Load Cannon*; *Lochini*; *London*; *Longues*; *Madrid*; *Magic*; *Mantis*; *Marker*; *Maupertus*; *Maverick*; *McCarran*; *Meautis*; *Minvody*; *Missile*; *Mission*; *Molay*; *Moonbeam*; *Moscow*; *Move Closer*; *Movers*; *Mozdok*; *Music Off*; *Music On*; *My Contact*; *My Enemy*; *My Target*; *Mystery*; *Nalchik*; *Nearest Airfield*; *Nearest ATC*; *Nearest AWACS*; *Nearest Carrier*; *Nearest Patrol*; *Nearest Tanker*; *Needs Oar*; *Negative*; *Nellis*; *NellisControl*; *New Target*; *No Joy*; *Normandy*; *North Las Vegas*; *Novorossiysk*; *One*; *One Minute*; *Open Formation*; *Open the Canopy*; *Open Up*; *Operator*; *Options*; *Otkrytka*; *Out Cold*; *Outlaw*; *Overhead Approach*; *Overlord*; *Paint*; *Paris*; *Pashkovsky*; *Patrol*; *Paveway*; *Perry*; *Perth*; *Picauville*; *Pickle*; *Pig*; *Pincer High*; *Pincer Left*; *Pincer Low*; *Pincer Right*; *Pinpoint*; *Place the Wheelchocks*; *Platform*; *Playboy*; *Playtime 10 minutes*; *Playtime 15 minutes*; *Playtime 20 minutes*; *Playtime 25 minutes*; *Playtime 30 minutes*; *Playtime 35 minutes*; *Playtime 40 minutes*; *Playtime 45 minutes*; *Playtime 5 minutes*; *Playtime 50 minutes*; *Playtime 55 minutes*; *Playtime 60 minutes*; *Podkova*; *Pointer*; *Pontiac*; *Proxy*; *Pulse*; *Pump*; *Pyro*; *Qeshm Island*; *Radar Off*; *Radar On*; *Radio Check*; *Ras Al Khaimah*; *Ray Target*; *Reading Back*; *Ready for Departure*; *Ready for Takeoff*; *Ready for Tasking*; *Ready Precontact*; *Ready to Copy*; *Reference My Spee*; *Reference My Steerpoint*; *Reference Point*; *Remarks*; *Remove the Wheelchocks*; *Repeat*; *Request BDA*; *Request Departure*; *Request Engines Start*; *Request HMD*; *Request Hover*; *Request Landing*; *Request NVG*; *Request Picture*; *Request Rearming*; *Request Refuel*; *Request Repair*; *Request Startup*; *Request Takeoff*; *Request Tasking*; *Request Taxi for Takeoff*; *Request Taxi to Parking*; *Request Taxi to Runway*; *Request Vector*; *Request Vector to Bandit*; *Request Vector to Base*; *Request Vector to Bullseye*; *Request Vector to Tanker*; *Return To Base*; *Rifle*; *Rocket*; *Rockets*; *Roger*; *Rome*; *Roosevelt*; *Rope*; *RTB*; *Run Inertial Starter*; *Saint Laurent*; *Saint Pierre*; *Sainte Croix*; *SAM*; *Sarge*; *Sas Al Nakheel*; *Say Again*; *Say Needle*; *Section*; *See You At Ten*; *Select*; *Senaki*; *Server*; *Shaba*; *Sharjah*; *Shell*; *Shift Beam*; *Ship*; *Shiraz Airport*; *Showstopper*; *Shpora*; *Silverbow*; *Sirri*; *Skala*; *Skunk*; *Smoke*; *Smoke Off*; *Smoke On*; *Snake*; *Sochi*; *Soganlug*; *Soldiers*; *Sommervieu*; *Sparkle*; *Spot*; *Spread Out*; *Springfield*; *Standby for BDA*; *Standby for Report*; *Status*; *Steady*; *Stennis*; *Stop*; *Stop Refueling*; *Stores*; *Stow the Boarding Ladder*; *Strafe*; *Straight Approach*; *Strike*; *Sukhumi*; *Take 1*; *Take 10*; *Take 11*; *Take 12*; *Take 2*; *Take 3*; *Take 4*; *Take 5*; *Take 6*; *Take 7*; *Take 8*; *Take 9*; *Tally Beam*; *Tally Mark*; *Tally Ray*; *Tally Smoke*; *Tally Sparkle*; *Tangmere*; *Tanker*; *Tanks*; *Tarawa*; *Target Visual*; *Tbilisi*; *Ten Seconds*; *Terminate*; *Texaco*; *Three*; *Tonopah*; *Torba*; *Tower*; *Tower Overhead*; *Tower Request Takeoff*; *Tracking Beam*; *Tracking Smoke*; *Tracking Sparkle*; *Traffic*; *Troops*; *Trucks*; *Turbo Off*; *Turbo On*; *Tusk*; *Two*; *Unable*; *Utility*; *Uzi*; *Vaziani*; *Vehicles*; *Vessel*; *Vetka*; *Warrior*; *Warsaw*; *Washington*; *Weapons Free*; *What is my Target*; *Whiplash*; *Wilco*; *Winger*; *Wizard*; *Yunga* Is that maybe the root cause? Is there a way to bulk import the keywords from .vap to VAICOMPRO? Or am I going in the wrong direction here ...

Hollywood, I was so hyped potentially finding something that I didn't realize the obvious: Looking in DCS might be looking in the wrong place, because even without DCS, in Hornblower's screenshot you can see that he gets an additonal "Have result, identified as recipient: Batumi" debug message, that I do NOT get. Again, Hornblower's screenshot: [ATTACH]238157[/ATTACH] My Screenshot: btw … I checked the ATC.lua file. Why the .subplace=NIL/NULL and what the connection with the VAICOMPRO .lua files is I'm not sure (at least it's not healthy to not catch NIL values in your code). As this is a print-Statement only, most likely for DCS debug reasons, I tested to comment it out and that "fixed" the error, NOT resolving anything of what I'm experiencing :(

Hollywood, I did a DCS repair, created a test mission starting hot on Batumi parking lot. "Batumi select" is understood (debug message "captured sentence: Batumi select"), but returns no beep or any reaction. Tuning in the frequency manually, again, no communication possible. BUT … your hint to look at the DCS.log may have brought some clues: Just starting DCS and loading the test mission, results in the following error logged in DCS.log: 2020-06-02 14:57:10.784 INFO COCKPITBASE: lua state still active MACROS, 55 (status undefined) 2020-06-02 14:57:10.784 INFO COCKPITBASE: lua state still active TGP_INTERFACE, 62 (status undefined) 2020-06-02 14:57:10.791 ERROR Lua::Config: Call error world.onEvent:[string "Scripts/UI/RadioCommandDialogPanel/Config/Common/ATC.lua"]:590: attempt to call global 'tostring' (a nil value) stack traceback: [C]: in function 'tostring' [string "Scripts/UI/RadioCommandDialogPanel/Config/Common/ATC.lua"]:590: in function 'onEvent' [string "Scripts/UI/RadioCommandDialogPanel/RadioCommandDialogsPanel.lua"]:1309: in function 'onEvent' [string "Scripts/World/EventHandlers.lua"]:13: in function <[string "Scripts/World/EventHandlers.lua"]:11>. 2020-06-02 14:57:10.810 INFO WORLDGENERAL: loaded from mission Scripts/World/birds.lua 2020-06-02 14:57:10.811 INFO DCS: dbox not found , skip This error is independent of the individual communication attempts, because it is there only one time. As it is related to .lua files VAICOMPRO is working with, might this be the root cause of my failed communication attempts? To crosscheck, I made another DCS repair, just started the mission and quit back to desktop. No error in DCS.log. The same part of the log looks like this: 2020-06-02 14:51:45.153 INFO COCKPITBASE: lua state still active MACROS, 55 (status undefined) 2020-06-02 14:51:45.154 INFO COCKPITBASE: lua state still active TGP_INTERFACE, 62 (status undefined) 2020-06-02 14:51:45.181 INFO WORLDGENERAL: loaded from mission Scripts/World/birds.lua 2020-06-02 14:51:45.181 INFO DCS: dbox not found , skip Then, starting VA&VAICOMPRO, starting DCS, loading mission, quitting to desktop (no communication attempts), the exact same error is back. Can I do something about that?

Hi Greyman, did the whole thing when switching back and forth including keywords transfer and speech delay settings. As seen in the debug messages obviously VAICOMPRO recognizes what I say (VSPX on or OFF), so no problem with recognition as far as I can tell. I am though not getting the "Have result, identified as command: ..." debug message that Hornblower is getting. Obviously something is going wrong in between when VIACOMPRO logs "captured sentence ..." and the "have result" part that is or leads to the actions inside DCS. Seems to be something within VAICOMPRO code maybe? @Hollywood: Is this the part where the network communication should take place and there is something going wrong here on my PC?

Hi Hornblower, thanks for your continuous support! I went through this checklist from the current VAICOMPRO manual as follows, hope I didn't miss anything important: TAB GENERAL Enable Plugin Support: ON --- CHECK, VAICOMPRO is loaded properly, I don't use other plugins Joystick Options --- CHECK, using buttons on my HOTAS throttle with no problems Load Profile on Startup: set to "VAICOM PRO for DCS World" (As suggested by Hollywood, I imported the vanilla VAICOMPRO .vap profile in VA to eliminate any potential issues arising from an edited profile.) TAB RECOGNITION Speech Engine --- CHECK, set specifically to "Microsoft Speech Recognizer 8.0 for Windows (English - US)" to avoid any issues Recognized Speech Delay: 0 ---CHECK Unrecognized Speech Delay: 0 --- CHECK (I do not use VSPX ... tried that at some point but to no avail) Command Weight: 85 --- CHECK as recommended Minimum Confidence Level: 60 --- CHECK as recommended, although I see that special words/names I trained in speech recognition are always identified but with lower confidence (e.g. "Al Minhad" ...), so I'm inclined to lower that value Min Unrecognized Confidence Level: 50 --- I believe this is unchanged to out of the box VA (?) TAB AUDIO Notification Sound: OFF --- CHECK Sound File Volume Offset: 100% --- CHECK Audio Output Type: Windows Media Components --- CHECK Playback and recording devices are all set to my Logitech Headset just to be safe. TAB HOTKEYS Recognition Global Hotkey: Disabled --- CHECK Mouse Click Recognition: None --- CHECK Joystick Button Recognition: Disabled Stop All Commands Hotkey: Disabled TAB SYSTEM/ADVANCED Cancel Blocked Commands: ON --- CHECK Use Nested Tokens: ON --- CHECK Additionally I activated: Run Voice Attack as an Administrator Generally, I don't think I have any relvant problems with the speech recognition itself (after extensive training that's working ok for me ...). It's just that after that, it seems VAICOMPRO is just not relaying what has been recognized to DCS. In DCS, the TX buttons used for VA/VAICOMPRO are not used as recommended. As suggested by Hollywood, I also used the keyboard keys, but no difference here compared to using joystick buttons. I have easy Communication off generally. PTT mapping in VAICOMPRO PTT page is set to norm. I can see the TX buttons highlight as I press them on the joystick. I think that wraps it up ... should you have anything set differently, I'd be happy to try that out!

Hello Hornblower, after Hollywood's suggestion to keep pressing the button until I get a confirmation, I waited several seconds (tried up to maybe 10sec) after I got the debug message "captured sentence ...", but unfortunately I get nothing ... no audio hint/confirmation nor any further reaction of VAICOMPRO in VA log :( (tried that without DCS started and also in game)

Hi sthompson, thanks for your hint! I'm sure I'm tuned in to the right frequency (radio is on, etc.). When in game this is even confirmed by a VAICOMPRO debug message like e.g. "[black] TX1 | COMM1: ARC-210 AM 134.000 MHz tuned for ATC unit Kutaisi [AI]" (see my original post). Additionally I confirmed the correct frequency via forcing communication via menus and I was able to communicate with the recipient via menus correctly.

It is exactly how you say, I'm missing the "Have result, identified …" for whatever reason. Here is the screen shot of my VA log from which I copied and pasted the contents in a previous post: This example screenshot was taken without DCS started like yours.

When troubleshooting the issue, I found a post on reddit a few days ago, that talked about a "config.lua" where the VAICOMPRO sound was set to 0, which was the reason he couldn't hear anything: https://www.reddit.com/r/hoggit/comments/b73n95/vaicom_listening_but_not_talking_any_help_please/ I tried to find that .lua file but couldn't find anything in DCS. Could this be a reason why I don't hear anything? As far as I understand, VAICOMPRO sound are not passed thru DCS but thru VA anyway ?!

Hi all, thanks all for your suggestions ... Reading on BSpikes case I came up with the idea to remove all VAICOMPRO lua files (Saved games + DCS World install folder), then do a DCS repair and start VA/VAICOMPRO again to make sure everything is up to date. Did that, but to no avail. Problem still stays the same :(

BSpike, yes, I can properly see the module name (tested in F15, F-16, F/A-18 ) in the PTT page of VAICOMPRO …

Yes, they are set to release and standalone correctly. I also only have this one installation of DCS (no additional openbeta install). Also, I checked that the .lua files from VAICOMPRO are present/content appended in the DCS folders like described in the VAICOMPRO manual. To my understanding, that looks good ...

Hornblower, testing this, for me the last debug message is "captured sentence: batumi". Interestingly, I do not get the "identified recipient message" and "awaiting additional input" that you obviously have from VAICOMPRO (black and purple lines): 8:15:01.589 Listening suspended 8:15:01.549 Joystick : 'Transmit TX1 release' 8:15:00.911 Captured sentence: batumi 8:15:00.730 Recognized : 'batumi' (Confidence 95) 8:14:58.716 Listening resumed 8:14:58.536 Joystick : 'Transmit TX1 press' 8:14:56.544 Plugin 'VAICOM PRO 2.5' initialized. Maybe this is were the key issue is (?)

Thanks for the suggestion, Greyman. I already set all my input and output in VoiceAttack to my Headset, overriding any Windows default devices just to be safe. I thought along your lines because besides the audio hints I do not hear the AOCS briefing readout. Chatter on the other hand works fine. But apart from audio, I also cannot see my request repeated as text and audio in DCS (as happening when you press a key and as they all get in the YouTube videos).

Hi Hollywood, thanks so much for joining in! Just imported the vanilla .vap in VA as suggested and pressed the TX keys thru until I got the debug messages from VAICOMPRO back in VA log. Still no confirmation beep. Also, I'm not in VSPX (although I tried that along my troubleshooting journey but it didn't change things). Log looks like that (you can see I pressed the TX key/button thru): 7:37:42.815 Listening suspended 7:37:42.755 Joystick : 'Transmit TX1 release' 7:37:39.821 Captured sentence: batumi 111 inbound 7:37:39.817 Recognized : 'batumi 111 inbound' (contains 'batumi') (Confidence 95) 7:37:39.817 Recognized : 'batumi 111 inbound' (contains 'inbound') (Confidence 95) 7:37:35.457 TX1 | COMM1: ARC-210 AM 131.000 MHz tuned for ATC unit Batumi [AI] 7:37:35.323 Listening resumed 7:37:35.274 Joystick : 'Transmit TX1 press' 7:33:26.142 Recognized : 'batumi inbound' (contains 'batumi') (Confidence 90) Thanks again for your support and the quick replies to everyone!

Hi Hornblower, thanks :) enjoy your meal :) Yes, I am running in debug mode (compare the [black] log messages that are coming back from VAICOMPRO debug. They make me believe that it understands my request … but nothing else happens, no confirm beep no actions in DCS.

I know (see my reply to Greyman in the main thread). I also tried "request startup", "request taxi to runway" as well as different "chief" commandos. Also "ATC, xxx inbound" is not working :(

Hello Hornblower, thanks for your support! I tried that as you suggested without DCS running, but I also do not get any audio hints (although this preference is set in the config) there. I do not have Hide On-Screen Text and Disable Player Voice checked. Edited to give more info: The only things I checked in the PREFS is "Extended Command Set", "Select Tunes Radio", "UI Sounds" & "Use Audio Hints".

Greyman, thanks for the reply! I'm aware that this is context sensitive and I also tried what you suggested. Also of course checked that comms are on and I'm on the right frequency. But I do not get any reply. Also "chief, …" for ground control is not working :(

Thanks Hornblower!

VAICOMPRO seems to get my radio calls but does not activate anything in DCS VAICOMPRO seems to get my radio calls but does not activate anything in DCS. This does not seem to be the typical "run as admin", "module not detected"/"install path" issue. I know this is a long post but I wanted to describe the issue as thorough as possible for you to better understand what I'm experiencing. I really wanted this to work for me to increase immersion in VR specifically (thanks to Hollywood for providing such a tool!) and invested a lot of energy in it (speech recognition training, installing, configuring & troubleshooting the software). I spent so much time with troubleshooting and testing each and every possible hint found in the manuals, FAQ and in various posts on the internet ... time that should have been gone into flying in DCS :). Meanwhile I'm really about to give up on this ... please help! Following along a test session, you could see the following happening in my VoiceAttack log in an F/A-18C mission on Kutaisi runway (1st message at the bottom, [black]=VAICOM Debug message): [black] 4:02:42.795 Captured sentence: kutaisi 411 request takeoff [green] 4:02:42.791 Recognized : 'Kutaisi 411 request takeoff' (contains 'kutaisi') (Confidence 73) [green] 4:02:42.791 Recognized : 'Kutaisi 411 request takeoff' (contains 'request takeoff') (Confidence 73) [blue] 4:02:42.418 Listening suspended [green] 4:02:42.375 Joystick : 'Transmit TX1 release' [black] 4:02:38.795 TX1 | COMM1: ARC-210 AM 134.000 MHz tuned for ATC unit Kutaisi [AI] [blue] 4:02:38.586 Listening resumed [green] 4:02:38.538 Joystick : 'Transmit TX1 press' I can see that VAICOMPRO is somehow connected to DCS because it properly identifies the module I'm using (tested with F/A-18 and F-16) I get VAICOMPRO debug messages in the VoiceAttack log that proof I'm communicating on the right frequencies for the intended recipient (see above "TX1 | COMM1: ARC-210 AM 134.000 MHz tuned for ATC unit Kutaisi [AI]") "sees" ATC communication that happens when I use the menus and shows it in VoiceAttack log like 3:19:14.284 ATC (Batumi): 111, taxi to parking area 3:17:34.281 ATC (Batumi): 111, Batumi, check landing gear, runway 13 3:14:47.762 ATC (Batumi): 111, cleared for visual, contact tower 3:14:31.732 ATC (Batumi): 111, Batumi, fly heading 283 for 6, QFE 29.89, runway 13, to pattern altitude SADLY, it relays none of my requests to DCS (even though VAICOMPRO seemed to understand it according to the debug message "captured sentence:..."). None of my radio transmissions is repeated in DCS (like you see on the Youtube videos) and I never get any reply (text oder audio) on anything (chief, atc/tower, ...). I can hear the short white noise sounds when pressing and releasing TX trigger buttons, but other than that, I do not hear any "Audio Hints" (this preference is turned on) which would confirm proper handling or point to an error. I also activated AOCS Auto Brief and although the VoiceAttack log shows the message "[purple] 3:59:16.416 AOCS: Starting mission briefing readout." I cannot hear the readout or see according messages. On the other hand, I'm hearing the VAICOMPRO chatter loud and clear so there should be no problem with the sound going to a wrong device (?). Running the current versions (as of date May 31st 2020): standalone DCS stable 2.5.6.49798, VoiceAttack 1.8.5, VAICOMPRO 2.5.20.0 with PRO, AIRIO & chatter license VoiceAttack is running as Admin (my Windows account has Admin rights so basically everything including DCS is running as Admin) deleted the export.lua (although I'm not using any other mods that could interfere) setting the custom DCS path in Config including registry update. I even checked that the according .lua files have been put in the right places (according to the VAICOMPRO manual) in the DCS install folder and were appended correctly where they should be as far as I can judge that. VoiceAttack.exe opened up in (Norton) firewall VAICOMPRO.exe also running as watchdog and opened up in (Norton) firewall (just in case :) ) I had a DCS repair running (cleaning any user mods) no other mods like Garmin NS430 in use at all I'm out of ideas here ... Any hint on what might be going wrong here is really appreciated. Thanks in advance!