Missing Alias 'for' won't go away!

[valleyboy]

Hi All,

last resort posting here, however I have a missing alias in Vaicom Pro and it will not go away!  I've re-loaded the profile multiple times, the only way to get rid of it is to reset the profile back to standard.  I've clicked on finish and pasted into the profile etc.  It still remains. 

It seems to get picked up while playing online, not been able to narrow down where exactly.

The missing word is 'for', and I've tried to add it into the database as an alias somewhere to make it go away - however it states the word already exists.

However it then states it's missing.

 

Has anyone else here come across this? 

Is my only fix to reset the keywords and make sure it doesn't import new words?

Thanks for any help

[MAXsenna]

Hi All,
last resort posting here, however I have a missing alias in Vaicom Pro and it will not go away!  I've re-loaded the profile multiple times, the only way to get rid of it is to reset the profile back to standard.  I've clicked on finish and pasted into the profile etc.  It still remains. 
It seems to get picked up while playing online, not been able to narrow down where exactly.
The missing word is 'for', and I've tried to add it into the database as an alias somewhere to make it go away - however it states the word already exists.
However it then states it's missing.
 
Has anyone else here come across this? 
Is my only fix to reset the keywords and make sure it doesn't import new words?
Thanks for any help

I assume you "test" the difference between the Keywords Editor and the VoiceAttack profile, and one missing alias/keyword is reported missing. You can safely ignore it, doesn't affect VAICOM at all.
I assume you also have enabled "Import F10 menu items". Turn that off and only enable when you are sure you want to import the menu. It's best suited for Single Player in my experience, or Multiplayer when you always play on the same server running the same mission. These items are imported with the prefix "action". I tend to always keep the command as it is, while making an alias that suits me. That way I can easily go through every "Action something" and remove them manually if they give me grief, or clogs up, which they tend to do if one always keep the import on.
Cheers!

Sent from my SM-A536B using Tapatalk

[sthompson]

I have had the same issue for a long time. I assume it has something to do with the difference between homophones four and for but I've never tried to track it down. Doesn't really seem to matter for my usage.

[PeneCruz]

Have you tried a keywords reset? if that fails you could delete the VAICOMPRO/database folder and let it rebuild.

[MAXsenna]

3 hours ago, PeneCruz said:

Have you tried a keywords reset? if that fails you could delete the VAICOMPRO/database folder and let it rebuild.

OMG! I completely misread. When OP wrote "reset to default", I missed the "profile" part, and I assume he meant the Keywords Editor/Database and not the VoiceAttack profile. LOL

@valleyboy My point still stands. Do not import the F10 menu unless you actually want to import specific items. Probably that alias got "corrupted", so it's hard to find it in the Keywords Editor. As Pene says, a database reset will solve this. The KWE has some issues assigning a trailing "1" if one doesn't pay attention when one is creating aliases. What's strange is that you can't find the "for" as it should be in the editor, as it says it's already there. Importing a clean profile will of course not help you in anyway. 

Cheers! 

 

[valleyboy]

Thanks for the replies all, if I do a keyword reset all is fine again and I have no missing aliases as that's what I've done previously. 

It's once it starts adding words in from the F10 menu that things eventually go wrong.

It's once it starts and when I finalise the keywords, no matter how many times I click finish, and paste into the profile etc - the word 'for' still comes up as missing when testing.

I think the solution is as above, keywords reset and deselect the import F10 menu and I won't get this problem.

I think you can get issues when there is a missing keyword as the ability to train specific words becomes a little more difficult as the test has to be successful before getting to that segment of running through words in the database to train, I have one of those accents that Voice attack HATES, so have to constantly try and train things 

I'm just confused as to why it says it's missing, but when I try and add it in somewhere it turns around and says it's an existing word.

I cut and paste the entire keyword database into notebook and searched for 'for' and it only ever came up in other sentences or words - not as a standalone word.

 

Cheers all, going to reset keywords database now for sanity sake 

[sthompson]

1 hour ago, valleyboy said:

Thanks for the replies all, if I do a keyword reset all is fine again and I have no missing aliases as that's what I've done previously. 

It's once it starts adding words in from the F10 menu that things eventually go wrong.

It's once it starts and when I finalise the keywords, no matter how many times I click finish, and paste into the profile etc - the word 'for' still comes up as missing when testing.

I think the solution is as above, keywords reset and deselect the import F10 menu and I won't get this problem.

I think you can get issues when there is a missing keyword as the ability to train specific words becomes a little more difficult as the test has to be successful before getting to that segment of running through words in the database to train, I have one of those accents that Voice attack HATES, so have to constantly try and train things 

I'm just confused as to why it says it's missing, but when I try and add it in somewhere it turns around and says it's an existing word.

I cut and paste the entire keyword database into notebook and searched for 'for' and it only ever came up in other sentences or words - not as a standalone word.

 

Cheers all, going to reset keywords database now for sanity sake 

I have had a similar experience except that I never import the F10 menu. So I do not think that is the cause, or at least not the only cause. There may be an underlying problem that can be activated in more than one way. The problem word is always "for," which makes me think this is a bug.

 

[MAXsenna]

@valleyboy Right, like I wrote, just ignore it. The best way to train is to go through the initial Microsoft Speech Recognition training multiple times in any case, or start dictating Word documents. VAICOM now has implemented "Wisper(?)", and if you choose to start using it, the training is completely redundant. 

Cheers!