FoxVox Free voice control software for BMS
-
@Rasmus I was playing with FoxVox VCC just yesterday and found the same issue. It seems the “Ready Start Two” command does not switch to the “Post Start” configuration. To fix that, I edited the “Test: rpm to 65” output command (by clicking little pencil icon) by its name and then set “Post Start” in “Config” fields for both keys and voice:
I don’t know if this is the only way or the most proper, but it worked
Remember to save the library after the change.I also noticed that you need to take care not to break the flow of the check. If, for instance, you break the flow by software recognizing your command as being further down the line, you may not be able to go back to the intended step, or you need to execute some previous command again, that would set the variables to the “correct” state. To learn what is going on, you need to track the conditions for voice commands and variables set by output commands:
The settings page for variables set by output command is displayed by clicking the round (x) button to the left of the “Output Name” label on the voice command edit window.@foxster thank you for this software and VCC library - it is much fun! For now I’ve been playing without BMS running to learn the flow and how to speak to being recognized. Is there a way to see what is the current value of variables? I think it would aid in analyzing more complex flows, like the one of VCC.
-
@Fox_15 Thank you, makes sense!
I think I figured out what was going on then, the Good Start, which is also suppose to take care of the change to Post-Start config, is not firing, inspite of all the condition going green.
Now I just need to figure out why.
-
@Fox_15 I figured it out.
You need to have Key Recognition turned on, for the triggers to fire.
-
@Rasmus Yep - Looks like you worked it out. Voice commands are just one half of the program which monitors voice input. The other monitors key input which also triggers on variable changes, and for the VCC, both need to be enabled.
@Fox_15 - What you did will indeed work but you are effectively bypassing the automatic detection of the actual engine RPM. Make sure that you have enabled both Voice and Key recognition just like @Rasmus indicates, and I recommend reverting back to the original configuration if that was also your issue. As you astutely pointed out, I did put in some constraints into the library (using variables and conditions) to make the flow fairly linear, but as you become familiar with the software, you’ll find it’s easy to adjust and rework those to be more flexible as you desire. You are by no means locked into using the default library setup so absolutely feel free to play around with it!
As for variable values, you can see the current value by hovering the mouse over the vertical dots indicator on the condition, and can also set a new value manually by clicking on it. That can be very helpful during testing. Variables coming from plugins can be viewed by clicking the ‘View Variables’ icon in the plugin management.
-
@Skorp Thanks for the nice compliment and I’m glad you enjoy it. Maintaining your phrases when there is a new update can be a little tricky, and there is no 100% easy way to do it, but I recommend you first make a backup of your library, then play around with the Import library feature. The import feature is highly customizable and can allow you to merge library files together in several different ways. Usually I merge a new library into my existing one, but you can also go the other direction.
As for the Push-To-Talk, see if you have a key or joystick button bound to the PTT on the Close command. PTT will require that the key or button is pressed in order to execute the command. You can change or clear it. The default library doesn’t have any PTT defined on it because it needs to be set to your individual joystick setup (but this might be changing in the future ).
-
-
@foxster I think is ok
![alt text]( im
Is the same as Tower, Wingman, Element, etc and those runs ok.
-
Good morning
I think I know which is the issue.
I don´t need to push VHF to FoxVox recognized all the commands groups except Open and Close commands. In these cases I need to push the button assigned to FoxVox recognize rhe commands and Push-to_talk preventing not appears.
All working
Cheers
-
Hi Foxster, thanks for your software that has worked perfectly for me in previous versions of BMS 4.37
For some reason following the update to BMS 4.37.3 and VC 2.3.0.0, BMS no longer recognises any commands. I am using the updated library for BMS 4.37.3, and have not made any other voice command changes.
The FoxVox software identifies and correctly interprets spoken inputs, but these are not invoked in BMS when in game.
I have tried changing the output process in Settings, to either BMS- or clearing altogether - and this does not solve the problem.
-
@fluffyduck9999 This is probably because the new library starts with the virtual crew chief active and not the regular flight commands. Change the active configuration to Flight (which you can set as the default) and the related commands will become active. There are many new features which unfortunately brings complications but offer a lot more functionality. I highly recommend watching some of the tutorials to learn more about the new features.
-
This post is deleted! -
Hi Foxster, thanks for replying so quickly, I followed your advice and problem is now solved - all working perfectly
Also realised that I had separated the .fvx file from the asset library, as I had not read the readme.txt file that comes with the library properly - I guess that was not helping …
-
@fluffyduck9999 Good…hopefully with the assets in place you can enjoy the virtual crew chief now too!
-
@jojojung said in FoxVox Free voice control software for BMS:
Have to say after the update nothing works anymore. No command is recognized. Hoped for a big step but thats sad…
On nearly every command it is said that command was not found. The software didnt recognize any speech anymore. Before update it was perfect and recognize nearly everything in the first try. Now there is no chance to play with voice recognition anymore.
When start the program first, and click on speech recognition the following message pops up. That was not the case in the older foxvox version. Maybe there is a connection to the problems. I have the english voice recognition activated in windows 10. So there should not be any problem.
Another question: How are the configurations switched while in game? From default to post start after engine start and to flight after takeoff. I need to ALT Tab everytime and change the configuration in foxvox itself.
I also get no good start voice massage when engine start, dont now why… -
@jojojung The error message is definitely related to your recognition problems. A quick question - what language options do you show when you click the language selection dropdown within the settings as shown here?
-
@foxster There i can choose from german or english (US).
when i choose german the error message disapear even when i reselect english right after that… -
@jojojung If you click save after changing it to English, does the message reappear again once you re-launch the app?
-
I just watched your long tutorial about the crew chief commands but the test: rpm 65 and good start does not work for me not in bms not in test only.
-
@jojojung Have you enabled Key Recognition as well as voice?
-
@foxster yes the message comes again…
when i go for german i can activate the voice recognition button and after that i can change that to english. i saved then to the file and close the program. But the message comes again when starting the program again. And the voice recognition button is crossed out again in the above menu.
No key recognition is not active.