FoxVox Free voice control software for BMS
-
I have just released FoxVox v2.2 which brings in vJoy support along with several stability and performance improvements surrounding the recent features. I am in the process of producing tutorial videos on the vJoy functionality and a complete instructional for the Virtual Crew Chief library coming soon.
-
V2.3 is out along with a new plugin called FoxVoxParser in the library section which provides for reading BMS key files into FoxVox as well as creating vJoy bindings automatically. There will be a new update to the VCC library which I plan will become the new default along with more details and a short video tutorial on this as well, which I’m still working on.
Special thanks to @Wheelchock for his valuable help in testing the beta version and providing feedback prior to release.
After this, plans are already made and work on v2.4 will begin…
-
Have to say after the update nothing works anymore. No command is recognized. Hoped for a big step but thats sad…
-
@jojojung Sorry to hear that nothing works anymore, but there’s not much for me to go on with that statement. I have not changed the voice recognition aspect of the code with the new updates - everything new revolves around conditional variables, plugins, and vJoy support. There must be something else at play besides the new update.
-
I have just posted an updated library for BMS 4.37.3 update finally - thanks for being patient. The library going forward has the Virtual Crew Chief now by default, but it can be bypassed by setting the default Voice & Key configs to ‘Flight’ (or just deleting the command groups entirely if preferred).
I am still working on the tutorials for the new updates, but they are not implemented in the new library yet anyway, so I’m not rushing on that. The new library should run smoothly with the current release.
-
@foxster I don’t understand a thing in the new library.
Is not possible to use both crew chief and normal radio?
I see that group commands for atc, flight, awacs etc are disabled in it…
Am I understanding something wrong? (probably) -
@Virus Yes it’s possible. At the start, only the crew chief is active but once the engine starts, that changes. If you want the other commands active right away just enable them on the default config and save it that way. Inactive/active status is tied to the active configuration which changes during crew chief interactions.
-
Hi @foxster
Amazing stuff right here! I just started with Falcon BMS and this is such an amazing tool when playing in VR.
However I cannot get my VCC to get passed the engine start. I can trigger the Whats going on, the Comms Check, the loud and clear reply, but when I say start two, it doesn’t move forward from there, he replies but never gets back with a good start. Neither ingame nor when testing outside BMS.
Is there another plugin that I need to work with the VCC? Or might something else be going on?
For now I’m still really enjoying the handsfree radio calls, so thank you for that!
-
Hello.
First of all, thank you for this masterpiece, Foxster.
Two questions:
1.- As far I´m spanish, I´ve made a personalized dictionary. Is there a way to maintain my phrases when there is a dictionary change? I´ve installed the U3 dictionary and all my phrases have dissapeared.
2.- I have a some of “Push to Talk preventing Visor from excuting on voice group Close”, what is the cause of this?
Sorry for my english
Cheers
-
@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!