Advanced Shoot Profile
-
Hi arty,
I have no problem getting recognized, Neither SHOOT nor VAC have an acuracy filter and my problem is that I get too many false positives
Well those two don’t comply m8.
If it doesn’t recognize u then u have an accuracy problem… So train and train and train, the more u train the less accuracy problems u will have… simple.
-
Hey Arty,
When you train with Windows, do you sometimes have to repeat the same sentence two or three times before it shows the next one? Sometimes, it recognizes me after the first try, but sometimes it takes two or three times. Is this a microphone problem or is it because more training needs to be done?
-
yes when i change my voice speed or pronansuason (sorry if i killed this word).
But i believe this is mostly cause english aint my mother tounge.
About the cheep headsets lol I aint tight at all, its simple, no money… still (after two years) paying a huge credit card bill for last computer parts… among others… -
I was just kidding arty…:)
-
Thanks, I am working on getting Shoot working after my extended Falcon hiatus. This will be a big help jcenzano! You mentioned setting up a profile for a specific mission’s flight callsign. I used to do this with ShootComms, a utility that quickly made a profile from a generic one to have your flight’s callsign. But it doesn’t look like anybody does this anymore. I went back through my 5+gb of Falcon stuff and finally found it, if anybody is interested in it, let me know!
-
Thanks, I am working on getting Shoot working after my extended Falcon hiatus. This will be a big help jcenzano! You mentioned setting up a profile for a specific mission’s flight callsign. I used to do this with ShootComms, a utility that quickly made a profile from a generic one to have your flight’s callsign. But it doesn’t look like anybody does this anymore. I went back through my 5+gb of Falcon stuff and finally found it, if anybody is interested in it, let me know!
I’m interested, haven’t used shoot in awhile but whenever I get some time to fly will definitely make use of it.
-
Here’s the link. You will definitely need to update the ShootComm’s .ini file from the .xml. After I build that from jcenzno’s file, I’ll post it unless somebody beats me to it first.
-
Hey guys,
I just started using MS Voice recognition and would like to incorporate it in BMS Falcon. I became aware of a program called SHOOT but I need some help to set it up to work correctly.
I downloaded SHOOT, installed it but it keeps giving me errors. I tried googling for a solution but have not been successful. I might have downloaded an old SHOOT software version. I don’t know what the latest version that works with Win 7 pro is. I also downloaded a demo of VAC and couldn’t get it to work either. Just don’t know how to set it up.
The one question that I would have is, does shoot work along side of MS voice recognition or do you have to have the MS voice recognition turned off.
Is there a tutorial that shows how to properly setup and install the profiles and run SHOOT or VAC? I saw a tutorial in YouTube for VAC but it didn’t really answer my question.
Can those of you that have a lot of experience using voice recognition software please point me in the right direction to get the right application and associated files?
Thanks in advance
-
Also in my HotList: link in my signature.
-
Arty,
Thanks for your help with shoot. I played with it and found that it was touch and go during flying. I would issue a command such as “2 go cover” but it came out “2 return to base”. Needless to say that sucked in the middle of a dog fight, lol,
Any way got out of the SIM and tested the commands and it would still issue the wrong command (not all the time). During missions it sometimes failed to work.Out of the SIM and looking at the SHOOT interface, I found that when speaking the dialog box would come out and say too loud or too noisy or cant hear or wouldn’t issue a command at all. I would raise my voice and then it would issue a command but the wrong one. Is that a problem with the IIS compatibility problem that was reported when installing NET 1.1? I’m using BMS_432_chipi_V2.3 STD keyboard. I’m not sure if its the headset or SHOOT.
I have a noise cancelling microphone head set and I’m thinking of maybe buying a different one (mine is a cheapo). Any suggestions as to which head set might be best for voice comm? I’m trying to issue commands consistently without SHOOT miss interpreting the command. I have trained several times with the MS voice recognition. I get good results when using MS Voice Recognition but not while flying Falcon.
Any suggestions?
Best Regards
-
I must say I am very pleased with shoot though for multiplayer I run a different profile such that it only listens when I wish it to. Suggest you create your own profile and keep simple/minimal. If you get a persistent problem with a particular command then try using different words that are less prone to being misunderstood. Of course the whole success or otherwise of shoot depends on how much time you spend teaching it your voice.
-
Arty,
Thanks for your help with shoot. I played with it and found that it was touch and go during flying. I would issue a command such as “2 go cover” but it came out “2 return to base”. Needless to say that sucked in the middle of a dog fight, lol,
Any way got out of the SIM and tested the commands and it would still issue the wrong command (not all the time). During missions it sometimes failed to work.Out of the SIM and looking at the SHOOT interface, I found that when speaking the dialog box would come out and say too loud or too noisy or cant hear or wouldn’t issue a command at all. I would raise my voice and then it would issue a command but the wrong one. Is that a problem with the IIS compatibility problem that was reported when installing NET 1.1? I’m using BMS_432_chipi_V2.3 STD keyboard. I’m not sure if its the headset or SHOOT.
I have a noise cancelling microphone head set and I’m thinking of maybe buying a different one (mine is a cheapo). Any suggestions as to which head set might be best for voice comm? I’m trying to issue commands consistently without SHOOT miss interpreting the command. I have trained several times with the MS voice recognition. I get good results when using MS Voice Recognition but not while flying Falcon.
Any suggestions?
Best Regards
Koku-ryu
Whats happening to you is a known issue of shoot.
Don’t give up on voice command. My opinion is that it pays off,In a couple of weeks (real not falcon time) I will release profiles for keyspeech, which is the program that I think to work best with BMS,
Good thing about it is that recognition accuracy is customizable so you can reduce false positives like the one you wrote, and it is much better to be used online,.
Profiles will be v2.3.1 which is pretty much the same as v2.3, with some phrases added to tower and tanker sections.
jcenzano AKA chipi
-
Thanks for the input. I completely agree with you. I find that using the radio (hands free) is the way to go. It is real joy to be able to use it. I found the SIM to have a higher immersion factor. I really enjoyed it very much. Right now I only use two keyboard keys, one for gear the other to change waypoints quickly when I’m delivering GPS munitions. Other than that everything else is through clicking and the HOTAS Cougar.
Thanks for your SHOOT profile. It is quite extensive. I will look forward to the keyspeech profile verson release.
Best Regards
-
well a lot of parameters can fubar recognition. Like where u have your mic and your mic boost. Play with it to find the best setting. Then redo speech train, as what u done was with other settings…
in the middle of a df if u don’t speak as should no recognition program will understand u. always have in mind to use a calm normal way of speaking.
I didn’t test keyspeech as is payware but I’m pretty sure it will behave the same, when u stress your voice pronunciation.
So train as much needed to have the most of accuracy and fine tune your shoot settings…
check the profile as some commands might be wrong.
In the past I have mixed some commands and I was pretty sure all was ok… when I fixed it all was normal…
Again sure some commands out wrong… but most needed comands like declare and etc are ok…
keep your voice commands in one word or as few as u can… like: “2 go cover”. no need for 2 just “go cover”.
-
well a lot of parameters can fubar recognition. Like where u have your mic and your mic boost. Play with it to find the best setting. Then redo speech train, as what u done was with other settings…
in the middle of a df if u don’t speak as should no recognition program will understand u. always have in mind to use a calm normal way of speaking.
I didn’t test keyspeech as is payware but I’m pretty sure it will behave the same, when u stress your voice pronunciation.
So train as much needed to have the most of accuracy and fine tune your shoot settings…
check the profile as some commands might be wrong.
In the past I have mixed some commands and I was pretty sure all was ok… when I fixed it all was normal…
Again sure some commands out wrong… but most needed comands like declare and etc are ok…
keep your voice commands in one word or as few as u can… like: “2 go cover”. no need for 2 just “go cover”.
Arty, you and I are on the different pages here…:p F****g language barrier…:wfish:
First of all, Shoot worked flawlessly on XP. But most people is getting the “Shoot geting out of sync” issue.
But my point was that i have no problem to get VAC or SHOOT to recognize a phrase. It is the other way around. The accuracy threshold is low, specially in VAC, and not customizable.
If I want to issue Q1, almost 99,9% of the times that I say “Chalis, Falcon 11 request picture”, I get my phrase recognized and the command issued.
The problem is that sometimes when my wife passes by and I say “Darling, your father just send a picture”, the program will find a “false positive” and issue q1 as well. Well, example is a litte extreme because you can argue that why the heck I am pressing the PTT while talking to my wife, but it is just an example.
That is why these programs become little truoblemakers when you use them online. Because during RTB you will be talking to your wingman about the beer in the o-club and then VAC or SHOOT will start sending commandas unintentionally.
It is true that the better you train VRS, the more accurate it will become, and the easier it will be to get a “good positive”. But the big problem of false positives has little to do with training your profile, but with the way the VR programs interact with windows VR software.
And that is where keyspeech kicks in, because it is the only one with a slider to manage how “relaxed” you want the software to be to recognize the commands.
With the same profile training, the positives and false positives you get will depend on the accuracy setting.
With the slider at 100%, England’s Queen hersel willl have to come and say a command to get a “true positive”, and the program will allow only a little deviation margin from the perfect pronuntiation(or better said “reference” pronuntiation"). But normal speech will not trigger a “false positive”. Of course the more you train your windows VR software, the closer you will bring the reference pronuntiation to your own.
With the slider at 0%, the program will be more “relaxed” and the allowed deviation increases. It is easier to get a “true positive” but also “false positives” will increase dramatically.
If you are using the program offline, lower values on the accuracy slider are ok, but when playing online, it must be close to 100%. With this I have been able to fly whole online missions of 1.5 hrs without a single flase positive.
So, I hope I made my point here, because it is a little bit trick to explain.
Even if it is payware (9$) I would definitely recommned keyspeech to improve your falcon experience. Besides there is a trial period long enough to decide if it is worthy to pay teh 9 bucks.
I promise I am not related anyway to the devs of keyspeech It´s just that I found the tool that I think works best. (they need to give us a PTT and it will be close to perfect)
Come on, man. give it a try…
-
shoot getting out of synch??? what do u mean by that?
Well wife is prohibited from entering the danger zone while flying… shoot her down… or use sign language… :rofl:
During RTB beer talking is forbidden… :rofl: u have time for that later on… Mission is still a go… so no beer.
U can voice command it to go to sleep and wake up… so no problem there.
Well since it works and pleases u I’m fine. I’m just saying that this can be done with shoot too, more demanding to achieve maybe.
-
Okay, good & less good news.
I’ve installed English language using Vistalizer and worked like a charm. Then I configured my mic and ran the Windows speech recognition training, went alright. Installed shoot, overwritten the config file and downloaded an F4 BMS xml profile, worked without a hassle. Opened notepad and tried some phrases, seemed to paste the correct stuff in there when using UFH/VFH comm switch on the Cougar as ppt.
So far so good, so I was pretty excited to open BMS and test it in there.
In BMS, I say something, it doesn’t react. I say something new, and I see the command in shoot being triggerd about what I said the first time. I say a new third thing, BMS voice says what I said the second time.
Very weird. Everytime I say something, it triggers what I said previous to last instead. And it doesn’t do anything if I request the same thing twice (even with different phrases).
E.g.: “tower request qnh”: nothing; “chalis request picture”: requesting qnh; “chalis declare”: chalis request picture…
E.g. “tower inboud”: nothing; “approach from one inbound”: nothing; “ground install chocks”: declaring inboud; “tower request taxi”: request install chocksAny idea’s?
Second smaller issue. Whenever I close Shoot, and I open it again, I need to reopen the BMS xml profile manually again. Doesn’t it save the last opened one or can you define a specific one as default to load?
And a question to finish; why do all commands in the xml start with shift+escape? do make sure no menu’s where still open before giving a new one?
-
That is a well knonw issue with shoot.
That is why I moved tio keyspeech.
It costs 10 bucks, but works much better for me. Only downside is no ptt in keyspeech.I well release profiles for keyspeech based on these shoot profiles shortly.
Give it a try.
-
That is a well knonw issue with shoot.
That is why I moved tio keyspeech.
It costs 10 bucks, but works much better for me. Only downside is no ptt in keyspeech.I well release profiles for keyspeech based on these shoot profiles shortly.
Give it a try.
10 bucks is not bad. But no ppt? That’s a show stopper, I want it to work with default UHF/VHF comms on my throttle.
-
It does not affect the gameplay.
Keyspeech will be monitoring your speech continuously, and when you say one phd the predefined phrases, it will trigger the command wether out not you have your bms comms key depressed.It if up to you of you are disciplined enough to push bms ptts everytime you want to issue a command via voice.
I send an email to the keyspeech devs regarding the ptt issue and they answered that they would look into out this fall.
Any way it has a trial period of one month, I believe.