'tower request takeoff' = (awaiting additional input) ??

[Snacko]

Just getting back into Vaicom..  I have Easy Comms off.

When I say 'tower request takeoff', Vaicom says it recognized the command every time with high confidence.  But then it says (awaiting additional input)

How can I fix this??

 

[sthompson]

Do you include a short pause between "Tower" and "Request Takeoff" while keeping the PTT open? That sometimes will fix problems like this. Personally I use the "ready for departure" version of that command.

 

[Snacko]

Yes, I have a short pause between commands.   'Tower' and 'Request Taxi to runway', 'Request Takeoff', etc., are all recognized with 94% confidence.  

I have my radio set to the correct freq for the tower.  And I tried TX1 & TX2....   

I think I'll do a reinstall and see what happens..

[Snacko]

I reinstalled VA and Vaicom, and did a full repair of 'All' files in DCS ..  No Joy!!  

[sthompson]

3 hours ago, Snacko said:

I reinstalled VA and Vaicom, and did a full repair of 'All' files in DCS ..  No Joy!!  

Reinstall rarely fixes anything in my experience. That other commands are working suggests that your installation is OK but that you have an issue with the command itself. But to be sure you might want to run the "test" function from the editor page.

Assuming that doesn't turn up any problems, I suggest you turn on debugging, restart VA, and report what comes up in the log when you give the command that isn't being recognized.

[Snacko]

Thanks for that info..   I did the Test and it says my profile matches.  But I went ahead and clicked the Finish button to copy the keywords anyway.  When I went into my profile to update the keywords, the current keywords went from AAA, ...... Zaqazig.    When I pasted my clipboard in, it only went from pasted this:

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

Also, with Debugging on.  At startup I only saw one error:

5:01:08.227 Object reference not set to an instance of an object./n   at VAICOM.Database.Aliases.BuildKneeboardAliasList()

Arggg... What's going on!?..  

 

[sthompson]

17 minutes ago, Snacko said:

Thanks for that info..   I did the Test and it says my profile matches.  But I went ahead and clicked the Finish button to copy the keywords anyway.  When I went into my profile to update the keywords, the current keywords went from AAA, ...... Zaqazig.    When I pasted my clipboard in, it only went from pasted this:

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

Also, with Debugging on.  At startup I only saw one error:

5:01:08.227 Object reference not set to an instance of an object./n   at VAICOM.Database.Aliases.BuildKneeboardAliasList()

Arggg... What's going on!?..  

 

I've found that with newer versions of VA and VCP when you paste during the Finish step it displays something weird, but if you hit control-Home or control-End you can see that you actually got the entire string pasted in. You can verify this by running a Test afterwards to make sure that the strings match the database. If the string does match the database but appears to be corrupted then you probably have a corrupted database and you should reload the Keywords list from the Reset page, then do the Finish step again. 

You might let us know what versions you are using. I'm using VoiceAttack 64 bit version 1.14 and VAICOMPRO 2.9.5.0. I believe those are the latest versions.

I'm not sure where you are seeing that error message on startup, but it appears to be related to the kneeboard and not to voice message processing. In any event, did you delete the old VAICOMPRO directory structure when you reinstalled? I'm wondering if there is an obsolete DLL file living there that did not get deleted on reinstall.

In any event, what I suggested was to actually try the command and then report back as to what is generated in the VoiceAttack log when you give the voice command.

[Snacko]

I was going to post this earlier today, but then decided to just backup my VA files folder and start fresh.  It seems to be working now.   And I noticed that when I said request takeoff, the log said something about Advanced Commands being disabled..  So, I turned that on, and it's working now.  I don't know why Request Takeoff needed Advanced Commands on??  Maybe I'm missing something?  Anyhow, it's fixed I think.

Thanks for your help on this sthompson!

Quote

 

VA v1.14 x64
Vaicom v2.9.5.0

I also pasted it into Notepad++ to see the entire clipboard, and it was the same.  And I did notice with the current and newly pasted words in the VA textbox, that it did like you said.  When I pressed Home or End it only went so far.  But dragging the cursor up and down revealed more than was seen in the text box using Home, End, Right or Left Arrow.  And a Test afterward says they don't match.  So, I put the original that was there before, back in.   And now the Test says they match.

So, I then did the Reset on Keywords only, and Reloaded and Finished it.   And it still only pastes that short string.  Which after looking at them, are only the Appendices keywords.  And now the Test says they match the database.  And the dropdown list on the Editors tab only has those 24 words.  (I did backup the original.)  

So, now I have the original keywords back in the profile.  AAA ... Zaqazig.   And the Editor / Dropdown list only shows the 24 Appendices keywords.  And the Test says they match?

 

 

null

[sthompson]

3 hours ago, Snacko said:

I was going to post this earlier today, but then decided to just backup my VA files folder and start fresh.  It seems to be working now.   And I noticed that when I said request takeoff, the log said something about Advanced Commands being disabled..  So, I turned that on, and it's working now.  I don't know why Request Takeoff needed Advanced Commands on??  Maybe I'm missing something?  Anyhow, it's fixed I think.

Thanks for your help on this sthompson!

 

null

Back when VAICOMPRO was a commercial product you could use some commands in a basic version but others in the "extended" command set required a "pro" license. I believe the option is a legacy from that time. Probably should be eliminated as an option now since everyone has the "pro" version in the community release. Glad to see that you got it fixed.

[PeneCruz]

Hey, the code is super tangled with pro licence options. We have them enabled for all and no check is made. 

To go back in and remove the pro licence checks and all the related coding would be a huge volume of work. As I didn’t write the code, it’s been a voyage of discovery. Just learning how things interact had been a big job. (There was very few Dev noted in the code) 

most of my time is spent just keeping it running. I’m working slowly on some expansions. But going back is not really an option. 

[sthompson]

3 hours ago, PeneCruz said:

Hey, the code is super tangled with pro licence options. We have them enabled for all and no check is made. 

To go back in and remove the pro licence checks and all the related coding would be a huge volume of work. As I didn’t write the code, it’s been a voyage of discovery. Just learning how things interact had been a big job. (There was very few Dev noted in the code) 

most of my time is spent just keeping it running. I’m working slowly on some expansions. But going back is not really an option. 

Thank you for your efforts to keep VAICOMPRO alive and working!

[Snacko]

7 hours ago, PeneCruz said:

Hey, the code is super tangled with pro licence options. We have them enabled for all and no check is made. 

To go back in and remove the pro licence checks and all the related coding would be a huge volume of work. As I didn’t write the code, it’s been a voyage of discovery. Just learning how things interact had been a big job. (There was very few Dev noted in the code) 

most of my time is spent just keeping it running. I’m working slowly on some expansions. But going back is not really an option. 

No worries!   Since I've got it working and noticed the 'Advanced Command' option, I realized that somehow most of the switches in VAICOM had been turned off somehow.  I hadn't used it in several months, and I remember I had it all setup like I wanted. But I didn't see how it could make any difference for such simple commands.

I could have just turned that on before I reinstalled, and the old install would have probably worked..

[Snacko]

PS:

Now that it's working I have another question..

When I say a command and it gets recognized, the Comms menu stays open afterwards.  I have to manually close it with F12, to get other F1, 2, 3.. view keys to work..   I don't want to disable the Comms menu.  Just not have it open when I 'say' a command.  Only open when I press the \ key.

[Despayre]

1 hour ago, Snacko said:

PS:

Now that it's working I have another question..

When I say a command and it gets recognized, the Comms menu stays open afterwards.  I have to manually close it with F12, to get other F1, 2, 3.. view keys to work..   I don't want to disable the Comms menu.  Just not have it open when I 'say' a command.  Only open when I press the \ key.

In your Vaicom options, there is an option to suppress the Comms menu from appearing. If for some reason you need to see the menu, you say "options", and then "take 1/2/3/etc" to get where you wanna be.

Edited June 2, 2024 by Despayre

[MAXsenna]

PS:
Now that it's working I have another question..
When I say a command and it gets recognized, the Comms menu stays open afterwards.  I have to manually close it with F12, to get other F1, 2, 3.. view keys to work..   I don't want to disable the Comms menu.  Just not have it open when I 'say' a command.  Only open when I press the \ key.

Have you mapped a TX as the same PTT button in the sim? If yes, that's why.
Cheers!

Sent from my SM-A536B using Tapatalk

[Snacko]

Thanks for the replys...   Good info..  

I finally noticed that if I just press TX1/2 again, the menu goes away..

[MAXsenna]

Thanks for the replys...   Good info..  
I finally noticed that if I just press TX1/2 again, the menu goes away..

Yes, because it's mapped as a PTT in the game/module.

Sent from my SM-A536B using Tapatalk