@ jcenzano One question.
in your profile (_BMS_433_chipi_V3.0 GERMAN keyboard-KEYSPEECH-COMMS only.xml) , some commands are beginning with SHFT ESC and some are not.
Whats the sense behind it ?
The shift ESC thing is an inherited thing from the profiles in which I based mine in the very beginning.
I think it was there to somehow “reset” the key strokes that the voice command program is sending to bms.
Let’s say that you want to send the W-1 command, but for whatever reason you had typed a single W with your keyboard before sending the voice commanded keystroke.
If you send the command without the shift ESC, you would get the W W 1 typed.
With shift ESC, it was supposed to clear any previous key strokes so you would get only the proper W 1 sent by the voice program.
Anyway IIRC that comes from the shoot days and even possibly from the falcon AF.
I don’t know whether it’s effective or even it causes any undesirable effect.
Typically, as you know, OSB 12,13 and 14 are typically page select buttons. Don’t know if that might have anything to do with it.
It’s a crazy world. I remember one time I couldn’t connect with my USB-C connector. I unplugged it and turned it around. Not supposed to matter, right? Solved the problem. Go figure.
So, starting with the first step, testing it, then second step, testing it, then third, and on and on and on, and I ended up with a working series of steps (that looked exactly like the original command, except one worked and the other one didn’t). Solved the problem. Go figure. Thanks for the suggestion.
<TLDR>: Instead of using the MPO cockpit switch, press key “o” to toggle MPO on/off. The “Kick” response will only occur when the pitch is full down.
So try this: when going through Big Movements and DBU movements:
a) Do pitch UP, get VCC Response “Nose Up”,
b) then do pitch down and hold it there (full down), get VCC response “Nose Down”,
c) wait for VCC response to stop completely, then
d) press and hold O key (or your assigned button for O keypress) for about .5 to 1 sec, get VCC response “Kick”.
e) Let go of O key and then press O key again (this disengages MPO - verify when you get back in the cockpit)
f) then continue on with roll and yaw testing.
VCC4BMS uses a small .dll file (F4SharedMem.dll) to look into BMS’s data stored in memory during 3D. Unfortunately, Manual Pitch Override (MPO) switch position is not one of the pieces of data stored in BMS’ shared memory. So, in order to define MPO for VCC4BMS, we have it search for when the “o” key is pressed (“o” key is the default keyboard command for MPO Switch Toggle). For real, when this evolution is done, MPO is engaged when Pitch is full down (because it is easiest for the Crew Chief to see the elevons drop fully down in MPO ON).
Additionally, if you ever get stuck in a VCC4BMS command, you can always tell the Crew Chief “Disregard” or “Standby”. This will break the loop that VCC is in that is holding up the events, and allow you to continue issuing commands.
I don’t know about "stand up guy,"😂but yes, I’ve been a US CFI-I for over 20 years now.
I’m not sure if I can get all the military Instructor Pilot (IP) terminology and panache but could try, especially if others are helping. I would probably need a better quality mic, but willing to buy a good entry level one. Most of experience is actually Private level students which is basic “primary” instruction, second most experience is Instrument instruction, and my favorite interest in BMS is air to air: BFM, ACM, BVR (and have done just a little “instruction” in VFS with that), also formation and AAR.
22.214.171.124 Added EMF theater data.
*Added a new command to store the ‘selected airport’ as STPT and select it. Use: store [selected;][airport;airfield];store [selected;][airport;airfield] as [nav point;steerpoint]
After that you can say: Inbound for landing, followed by Set course… & Set nav mode tacan
*Started adding elevation data to theater data.
*Fixing wrong coordinates when entering Lat/Long.
*Added config option to select the STPT to store the “selected runway”
*Added config buttons to “Show All Phrases” & “Show Theater data”
Added command [say;report][airport;airfiled][runway;runways]
This will report the ‘selected’ airfield runways.
*Adding config option to run plugin in ‘Debug Mode’
*Adding buttons to show VA log in the config Help Tab
*Adding buttons to clear VA log in the config Help Tab
Adding vocal command to show last saved VA log: [show;display;open][va;voice attack] [command;log] file
@hoover Thanks, but I think it’s covered enough. I’ve been testing extensively for some time now and the release is imminent. It has all the latest fixes & additions. Trouble now is building the tutorial content to explain everything new which I’m working on.
@Sabre I’ve mapped mine to both UHF and VHF so I can use either one to talk to the AI. I’m using @SemlerPDX’s profile.
Atlas is there a way to use 2 different DX buttons (UHF/VHF) as PTTs in VoiceAttack?
There is a way you can accomplish this, though the native Push-To-Talk hotkey option in VoiceAttack will only allow one.
If you create two commands in VoiceAttack, each with a trigger option of a Joystick button press, one for UHF, and one for VHF, you can use these to toggle listening to achieve something similar to what I have used for my PTT system in my AVCS4 BMS Radio Menus profile for VoiceAttack by adding the “Start Listening” action as the top most action in the actions list.
You would then create two more commands, each with the action to “Stop Listening”, and with the trigger option of your Joystick button set with the checkbox for “Shortcut is only invoked when all buttons are released” - one command doing this for your UHF button, and another for your VHF button.
This way, when you press one of these, VoiceAttack begins listening, and when you release one of these, VoiceAttack stops listening.
Of course, if using my AVCS4 BMS profile, you’d just load it up, and then say, “Set a Push to Talk button” - can set up to 6 total PTT’s as mouse or joystick buttons or keyboard keys.
@SemlerPDX Hey SemlerPDX! Truth be told, I’ve been itching to delve into your AVCS for a while now. Guess it’s about time I took the plunge. Now, regarding my initial question - it’s a swirling storm of variables. For instance, it could well be tied to how I’ve been juggling processes across cores in ProcessLasso.
Here you can download my file for VAC with right commands.
It’s a very simple version .
I kept only one o two sentences for commands.
My good french accent is not easy for vac (nobody’is perfect LOL) so i changed in flight menu “flight” to ‘formation’
I changed also some sentences to be easiest and more intuitive to my mind
“tanker name” formation request fuel for example
Sorry to hijack this thread, but I just found out about this the hard way when I rebuilt my system, and now find that I am unable to register, and so use, this software. I have been using VAC for years, have it configured just so for many sims, and now find myself up a certain creek without a paddle.
Does anyone have any idea of how to get this sofware working or know if there’s any way to contact the dev?
Jeeves BMS Radio Plugin, now v0.2.0. with many more commonly used menu item phrases, including “Runway N N” phrases for Tower calls, and “Four-ship F16” etc. (Idea from the excellent UOAF profile.)
Ability to change aircraft type on the fly with “Update Aircraft Type F18/F16/etc”.
User controllable “DirectMenu” framework so user can set specific menus to not display while listening for menu item choices. This lets a user mark which menus they don’t need displayed, since they use them all the time and know them well, while letting other menus they don’t have memorized still display normally. (Lightly tested.)
User controllable “directMenuGroup” framework to allow grouping multiple menus together that listen (like a DirectMenu) for any menu items from all menus in the group without having a menu up. This is quite useful and still allows normal use of the menus included in the group. Two menu groups have been added. The “Approach” group contains Approach 1 & Approach 2 menus and the “AWACS” group contains AWACS Tactical & AWACS Vectors. You can still pull up the specific menu by specifying “Approach 1/2” or “AWACS/Overlord Tactical/Vectors”. You can add your own directMenuGroups.
Arco 3, Viper 1 - Request Flight Refueling
Update Callsign Hunter 6
<<Say your flight position in Hunter 6 or say ‘Skip’>>
<<New Callsign Hunter 6 1, Reinitializing Profile>>
Tower, Hunter 6 - On Final Runway 2 6
Axeman 2, Hunter 6 1 - Check In
Update Aircraft Type F18
<<New Aircraft Type F18, Reinitializing Profile>>
Tower, Hunter 6, Two-Ship F18 - Request Formation Landing