VAICOMPRO seems to get my radio calls but does not actvate anything in DCS

Since it appears that Batumi is recognized in your test, I'm wondering if the issue is that you have not selected Batumi as the recipient. This is not automatic unless you have "Instant Select" turned on. Also, is your radio powered up?

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:

[ATTACH]238069[/ATTACH]

This example screenshot was taken without DCS started like yours.

Try holding it for a bit longer and see what happens

Sent from my SM-T835 using Tapatalk

How long are you holding the TX button down after you have finished talking?

 

Try holding it for a bit longer and see what happens

 

Sent from my SM-T835 using Tapatalk

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)

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)

Sent from my SM-T835 using Tapatalk

Ok - are the VA options for speech recognition configured as shown in the VAICOM manual (just trying to step through and see where there may be differences with my setup)

 

Sent from my SM-T835 using Tapatalk

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

1. Cancel Blocked Commands: ON --- CHECK
   
2. 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!

when you tried VSPX, did you reset all of the necessary settings, to make sure that you are not stuck somewhere between the two modes?

From the manual:-

Switching Between Modes

To change between Default and VSPX modes, follow these steps:

• In Preferences, (de)select VSPX option: you will see a pop-up. Press OK.

• Follow the FINISH steps in the keywords editor to update your VA profile,

• In VoiceAttack options put these settings as follows:

Unrecognized Speech Delay

VSPX OFF: 0ms.

VSPX ON: 600-1000ms: 700ms recommended.

Done. The green light on the editor page shows whether VSPX is activated.

when you tried VSPX, did you reset all of the necessary settings, to make sure that you are not stuck somewhere between the two modes?

 

From the manual:-

Switching Between Modes

To change between Default and VSPX modes, follow these steps:

• In Preferences, (de)select VSPX option: you will see a pop-up. Press OK.

• Follow the FINISH steps in the keywords editor to update your VA profile,

• In VoiceAttack options put these settings as follows:

Unrecognized Speech Delay

VSPX OFF: 0ms.

VSPX ON: 600-1000ms: 700ms recommended.

Done. The green light on the editor page shows whether VSPX is activated.

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?

Suggest to keep your voice command simple for basic testing.

Run a DCS Repair first: manual lua tweaking is almost guaranteed to cause problems.

Then enable Select Tunes Radio and instead of 'Kutaisi 411 request takeoff' try 'Kutaisi..Select' (beeps, tunes radio) followed by a simple 'Ready for Departure' and work from there.

This assumes export.lua is cleared form third party entries and VA is running as admin with no antivirus/firewall interfering. If needed inspect DCS.log for further clues.

Suggest to keep your voice command simple for basic testing.

Run a DCS Repair first: manual lua tweaking is almost guaranteed to cause problems.

Then enable Select Tunes Radio and instead of 'Kutaisi 411 request takeoff' try 'Kutaisi..Select' (beeps, tunes radio) followed by a simple 'Ready for Departure' and work from there.

This assumes export.lua is cleared form third party entries and VA is running as admin with no antivirus/firewall interfering. If needed inspect DCS.log for further clues.

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:

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:

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?

These log entries are benign and unrelated, ED forgot to uncomment a line somewhere.

I see this entry too on occasion but everything still works 100% here on the testbench.

Just to be clear did you already clear your database with the Reset tab and perform the FINISH steps.

Without DCS running, what shows in the VA log if you just say Batumi while holding (and keeping held) TX1.

 

 

I have attached a shot of my log window for comparison (it is with the debug option on)

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 :(

Probably something got corrupted in your database somehow, suggest to delete both the Database and Config subfolders and restart VA.

These log entries are benign and unrelated, ED forgot to uncomment a line somewhere.

I see this entry too on occasion but everything still works 100% here on the testbench.

Just to be clear did you already clear your database with the Reset tab and perform the FINISH steps.

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"):

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):

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 ...

Probably something got corrupted in your database somehow, suggest to delete both the Database and Config subfolders and restart VA.

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!!!

Really glad it is working:thumbup:

Really glad it is working:thumbup:

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

\o/\o/ Nice one \o/\o/

Now get to something relatively easy.

AAR and Case 1, 2 and 3 recoveries in the Navy jet of your choice should be a breeze now. :)

Good job gurus

\o/\o/ Nice one \o/\o/

 

Now get to something relatively easy.

 

AAR and Case 1, 2 and 3 recoveries in the Navy jet of your choice should be a breeze now. :)

 

Good job gurus

Sure on the new Super Carrier :) !

Thank you, too, Greyman!