Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
Tags
(1 edit)

Hi again,  Please let me know if this is an appropriate forum for asking questions about FOXVOX or if there is a better mechanism.  Here goes:

- When I use FoxVox in VR with DCS, everything works superbly. However, when I am just testing with JUST FoxVox open,  or with DCS in regular non-VR mode, I notice SOME commands take forever (i.e. 5-10 seconds) to actually execute even after they are recognized. Any ideas? Any way to improve this. Doesn't seem to be an issue FOR ME, in my main usage but it is odd.

I have seen other  programs that seem bothered when the Framerate is TOO HIGH (what a problem to have!!) when trying to inject commands, so in VR, it is reduced and the timing seems to work better in those cases. This doesn't apply when just testing with FoxVox only, of course.

Your BMS library works great for BMS 4.37 VR, but I haven't really tried it in Non-VR mode, but I expect that this is what the majority of users are actually doing!

- I have been using FoxVox to issue various numbered commands. I notice that whether I program "ONE" or "1" FoxVox recognizes as the numeral. This is fine, EXCEPT when I get to double digits, if, for example, the voice command F 10 is recognized, it will actually EXECUTE the command under F 1.  Similarly for F11, F12 etc. Seems that the trailing digits are ignored and anything from 10 up is recognized as "1".  Haven't tested to see if "20" gets recognized as "2" or not. Any ideas?

The more I play with FoxVox the more impressed I am!

(1 edit)

Hi @Wreckluse,

First, posting questions and comments here is perfectly fine, and I'll do what I can to answer.

With regards to the delay, this probably has to do with the microphone/sound detection changing between VR and non-VR/normal operation.  Are you perhaps using a different microphone setup when you play VR vs standard?  The delay is usually caused because the active microphone is picking up external sounds still even after speaking is completed.  The speech engine remains listening without letting FoxVox process the speech until it finally times out.  You can visually see this if the listening indicator icon remains green for some time after speaking.   To fix this, try reducing the sensitivity of the microphone, keep it away from computer fan noise and any other sources of sound that it might pick up as background noise.  You can also play with the Timeout setting in FoxVox by entering a low value (like 1) to try and force a timeout earlier.

For your question about numbered commands, I recommend you always use spelled out numbers for the voice command keys (i.e. "One", "Two", etc.) This will prevent "One" from conflicting with "Ten". If you run into a conflict  such as "One" vs. "One Hundred", you will need to put a blocking word of "Hundred" onto the "One" key so that it can tell the difference.  Alternatively you could place the "One Hundred" command above the "One" command so it will be evaluated first and will be skipped if "Hundred" is not contained in the spoken phrase.

Thanks for your positive comments about the app and I'm glad you like it!  My hope is that it can be a useful tool for anyone needing free and customizable voice control :)

(1 edit)

Yeah, the spelling out of the numbers was the first thing I tried. Here is a screenshot of what is happening.  Spoken "F ONE" gets translated to F1 and the F1 command is executed. Spoken "F TEN" gets translated to F10 BUT the F1 command is executed!

If I use a non-numeric word (I use MAP because F10 also shows the map when a menu isn't up) and "F MAP" works perfectly to invoke the F10 command.


You have uncovered a rather unusual little nuance in the recognition here.  I will post an update today that will address it.

Heh! Leave it to me to break stuff! Glad it helped to squash a bug.

Ok, let's see if it's resolved now.  I provided a little more info in the changelog you should review.  Give it a go and let me know the results.

(2 edits)

This is the P10 command for Target group.

P10 Command

OK.. This seems to have cleared up the F commands. F10 works now (I did also put F10 into the voice command in addition to FTEN).

Now I have another case, which might be special.

I need FOXVOX to spell out text for an entry box, in the format #TPn but I wasn't sure how the built in SPELL command would recognize # (HASH?) So I built commands to respond to the TARGET - P1 through P10. 1-9 work. Oddly again there is a digit thing going on. FoxVox recognizes "TARGET P TEN" as "TARGET P1 P10" and invokes P1. See attached:

Issuing commands to create #TPn text where n is the number

This might be a crazy edge case that isn't worth fixing. I used 
PX instead of 10 which works.

EDIT: I used JUST the numbers without the P and it works! I think I put the P in when I was having issues with the numbers. Interestingly it recognizes the spelled out numbers better than the numerals, ONE vs. 1, which seems contrary to the fix. When the P is before it, it recognizes the numerals just fine.Exception is FOUR, 4. I had to put "FOR" in to get it recognized, which again wasn't the case for the F set of commands

Right now spell is limited to alphanumeric only.  I'll give it some thought though.  At least we got the numbers sorted out.