Easy's Voice Attack Profile for 4.35
-
Hi all,
Please find attached my Voice Attack Profile for BMS 4.34, created in Voice Attack 1.7.5, based on Terminator’s excellent 4.33 profile.
I’ve shared two profiles; one with all common F16 callsigns and one with a single callsign: Viper.
The reason for this division is simple: VA uses lots of memory and I’m hitting the limit of what VA is capable with all the new ATC entries.
To run somewhat leaner on RAM use the single callsign profile.
Last note: I have two push to talk scripts running as I use HOME and END as VHF and UHF PTT, respectively. This is a little more advanced stuff so if you only use a single PTT button remove these lines in the profile, or modify carefully with the VA-manual in hand.
UPDATE 25-4-2019
- Added profile with common 4.34 callsigns labeled Falcon BMS - 434 - Common Callsigns 434.
UPDATE 04-5-2019
- Common callsigns: Removed all flight numbers of 6 and above such that the profile can be edited without crashing VA;
- Fixed element commands;
- Single callsign is now listed as Falcon BMS - 434 - Callsign Viper.vap; Good option when memory is an issue;
- Python script added: easyCallsignCopyPasteScript.py; will copy the contents of Falcon BMS - 434 - Callsign Viper.vap to any of the callsigns specified in CSList in the script;
- Voice activated callsign profile switch-command added; Learn your speech engine the callsigns you want to use with Options->Utilities->Add/Remove Dictionary Words for best results.
This enables generation of this VA profile files for all callsigns available in BMS if you like.;-)
Enjoy,
Easy -
Thank you ! I started making one, but since you have, that much more flying time for me
-
Hi all,
Please find attached my Voice Attack Profile for BMS 4.34, created in Voice Attack 1.7.5, based on Terminator’s excellent 4.33 profile.
Many lines are subject to my squadron’s SOP so have a look at all the lines and see how they work. It’s setup to be reasonably flexible though.
I’ve shared two profiles; one with all (4.33) common callsigns and one with a single callsign (viper; find and replace in notepad++ to change)
The reason for this division is simple: VA uses a lot of memory and I’m hitting the limit of what VA is capable of (max 1.5Gb RAM) with all the new ATC entries.
To run somewhat leaner on RAM (just a mere 500MB) use the single callsign profile.
Last note: I have two push to talk scripts running as I use HOME and END as VHF and UHF PTT, respectively. This is a little more advanced stuff so if you only use a single PTT button remove these lines in the profile, or modify carefully with the VA-manual in hand.
Enjoy,
EasyThat’s a lot of time and work shared in one click. Thank you very much Easy!
-
Nice work Easy!
-
Thank you very much, Easy. Now I get to fly this afternoon!
-
Thanks guys glad to share something in return. found a small error in the script for (tt1), fixed.
-
Thank You Easy!!!
-
thankyou for sharing,
i have a possibly stupid question:Say I wanted to edit it to be able to say “Ground” instead of “Ground Control”
But I get this error message when I change anything in these commands… duplicates…? where? any ideas what I’m doing wrong?
EDIT: okay, voice attack hates when there are multiple instances of [1…9] in one command. For instance, you’ve got to have a [1…9] for Sentry’s number and also a [1…9] for Vipers first number
Well then I don’t understand how they got there in the first place…
I have to open up the .vap file with notepad++ and started editing it “manually” in order to change anything. -
edit: disregard
-
Gza036 VA can be a little picky with these things, did you fix your problem? I will tweak the profile tonight so that these errors can’t happen, not being able to edit is not ok. Will change to ground instead of ground control by default too; had some issues with recognition of ground only but the current fix is a little funny maybe.
-
Well, I just decided to remove all the callsigns and keep it all a little more basic for now.
Just curious how you will tweak it so the duplicates don’t happen? I’d definitely take a look at your next version. -
Its a bit silly but change [1…9] [1…4] with [1 1; 1 2;…etc…;9 4] and it will work.
-
I see.
btw i was poking around the voice attack manual… have you experimented with wildcards? surrounding things with asterisksWildcards
There is a somewhat unsupported* feature in VoiceAttack’s ‘When I say’ feature.
You can use, ‘wildcards’ around the phrases to indicate, ‘contains’, ‘starts with’ and
‘ends with’.So, let’s say you have a spoken phrase ‘attack’. Let’s also say that you want to
execute your command if the word, ‘attack’ is included in any spoken phrase. To
indicate to VoiceAttack that you want the ‘attack’ command to execute any time it is
contained in a phrase, you simply put asterisks around the phrase, like so: attack.If you want to indicate that you want the ‘attack’ command to execute if the spoken
phrase starts with the word, ‘attack’, just put an asterisk at the end, like so: attack*.
This way, you can say, ‘attack the enemy’ and VoiceAttack will execute the ‘attack’
command. If you say, ‘I would like to attack the enemy’, the ‘attack’ command will
not be executed, since the word, ‘attack’ is not at the start of the phrase.On a similar note, if you only want, ‘attack’ to be executed if the word, ‘attack’ is at the
end of the phrase, put the asterisk at the beginning, like so: *attack.VoiceAttack will execute all of the commands in which the wildcards apply. So, if you
have ‘rocket’ and ‘ship’ and ‘attack’ as commands, and you happen to say, ‘I
would like to attack the ship with my rockets’, VoiceAttack will attempt to execute
‘attack’, then, ‘ship’ and then ‘rocket’ in that order (the order in which they are spoken,
but due to the asynchronous nature of this type of situation, the order cannot be
guaranteed (use with caution).Commands will not repeat with wildcards. If you have commands, ‘rocket’ and,
‘ship’ and, ‘rocket ship’ and you say, ‘I want to take a ride in my rocket ship’,
VoiceAttack will execute the command, ‘rocket ship’ and not ‘rocket’ and ‘ship’. Also,
if you say, ‘rocket rocket rocket rocket rocket rocket rocket rocket rocket’, the ‘rocket’
command will only be executed once.- The reason it is ‘somewhat unsupported’ is basically because it is not a terribly
reliable feature and was added as an attempt to give a little bit more flexibility,
especially in the areas of immersion. Your mileage may vary. Good luck, captain!
- The reason it is ‘somewhat unsupported’ is basically because it is not a terribly
-
wild cards didn’t work for me. However you could try using them if you have very specific code words for the commands you want to make
-
OK folks, reuploaded. Changelog: Ground is now adressed as ground (sorry David) and the profiles are editable in the UI. enjoy.
-
Thanks Easy
I’m sure you’ve noticed they expanded the amount of callsigns that F-16’s use.
There are 22 now. I assume that adding all those would surely bring Voice Attack to its knees memory wise?\Docs\05 Other Documentation\radiomap.xls
I actually still can’t edit the “common callsigns” .vap myself
Any attempt to edit the large commands causes some kind of memory related crash LOL -
Someone told me that using prefix/suffix groups would improve combinatorics (whatever that means) and use less memory.
Something like what Brainling used in his profile:
https://www.reddit.com/r/hoggit/comments/3cxctz/falcon_bms_voiceattack_profile_for_ai_comms/I may try to make a hybrid of yours & brainlings
-
Someone told me that using prefix/suffix groups would improve combinatorics (whatever that means) and use less memory.
Something like what Brainling used in his profile:
https://www.reddit.com/r/hoggit/comments/3cxctz/falcon_bms_voiceattack_profile_for_ai_comms/I may try to make a hybrid of yours & brainlings
Before you spend time on it, you might wanna check out my profile here.
-
combinatronics. Brainlings profile seems quite efficient but man so much work. Keep us posted gza, this memory situation isn’t ideal. I don’t have a lot of spare time this week but when I do find some I’ll share a little python script that generates separate files for all BMS callsigns and a function Terminator made to switch between callsign-profiles should we need a brute force alternative.
BTW, nice find on the new F16 callsign list! I’ve managed to cram them all into new profile which is somewhat more optimised (aka less flexible but still ok). You’ll find it as Falcon BMS - 434 - Common Callsigns 434
-
Even after using some prefixes I’m still hitting the wall, unless I make compromises. I’d be interested in trying the multiple profile trick.
edit: yeah dude I’m no programmer, I give up on trying to make it super efficient. I’ve got a single callsign profile working real nicely. Lets bring in da Terminatah I want 30 different profiles for every callsign lmao