AVCS4 Immersive Voice Control Radios for VoiceAttack
-
At the end of the initialization of AVCS Core, I have this
BMS Data Load Complete - Voice Attack is now loading profile
Inline function execution exception: Exception has been thrown by the target of an invocation. Index was outside the bounds of the arrayCould it be in relation with my issue ?
This could be an issue in addition to the PTT issue you are having. Again, if you are from a region that expresses Pi as “3,14” as opposed to “3.14” then two decimal variables will be messed up. These are part of the timing of the PTT keypress loops, so would effect those and foul them up. A hotfix is located in a previous reply here (reply to Judy), and I will have it all fixed as soon as I get this next version released.
Just need a bit more time to work on it. Thanks for your patience!
-
thanks Amadeus75 and Semler
Semler your suggestion doesn’t change any thing after I edited the profile as shown.
But it appear that the way suggested by Amadeus change something. I have to find the good timing for release and this way let the recognition log between the press and release log. Nice
When it works, I noticed something strange :
when I say a VHF command without PTT, I have
“9:22:36.933 AVCS4 Command Recognized, but PTT Mode is on and PTT Key Down not detected…
9:19:47.042 Recognized : ‘two say fuel’ (derived command) (Confidence 97)”Which seems normal and nothing send to the file
But For a UHF command, even if recognition ok and nothing send to the text file, the warning about PTT does’nt appear
Is it the normal Behaviour?
Edit : When the release key seems not to have been detected, I noticed that i need to do a press, then wait 1 or 2s (i don’t know exactly how long) without saying anything, then release. and it seems that the PTT is re initialize with always the same behavior as describe in this post (Ptt warning not detected only for VHF):shock:
-
I now have to keep the PTT key pressed for a second or two after speaking for the command to be recognised. I found that if I keep the key held until it’s recognised, that is the most consistent way for commands to register.
I thought it was because of JanJan’s plugin, but not sure - are there too many commands and is it parsing the best profile to use?
(and there was a minor update)
-
I now have to keep the PTT key pressed for a second or two after speaking for the command to be recognised. I found that if I keep the key held until it’s recognised, that is the most consistent way for commands to register…
That’s how it works for me, too. I have sometimes wondered if this is normal, or if that 1-2 second delay is supposed to be shorter. I’d be curious to find out.
-
I’m trying to figure out how AVCS4 BMS for VA works. I imported both core and AVCS4 bms profiles to VAC, AVCS CORE (v0.92b) is set as Global Profile in General Options (v1.8.7) and AVCS4 Falcon BMS Radios (v1.3.92b) is set to Load Profile on Startup. Core and AVCS4 BMS initialize ok. Alternative All-Humans Mode is OFF, Audio Feedback is On, Default keyboard QWERTY, UHF/VHF PTT mode is ON. I didn’t touch anything else in CORE/AVCS4 BMS profiles. Now I enter 3D and fly around Kunsan, I set UHF to 292.650 Kunsan’s ARR Approach frequency, push and hold my UHF button (UHF is highlighted) and request different approaches starting with: APPROACH Request (any) or APPROACH Declare Emergency…. Nothing happens. I check VAC recognizes commands Ok(green). What am I missing?
Do I need to add key strokes in the profile perhaps (not sure but I don’t think so)?Thanks.
-
What am I missing?
Give it a try, and keep your finger on the button just a little longer after you spoke the command.
I think it could be a timing issue with “UHF/VHF PTT mode”.Make sure you hear that audio recognition signal, BEFORE you release the PTT key.
Otherwise the command may be recognized, but not within the correct “PTT time”.
The correct log should read: “Press -> recognized -> release”
Otherwise it may read “Press -> release -> recognized”… in this case, the recognizing comes too late for PTT mode.I could be wrong, but just give it a try.
(PS: Oh, and be careful: “VAC” is not “VA” ;))
-
I assume you’ve assigned your hotas buttons for ptt? I made the error of assigning hotas buttons AND keyboard keys (the profile explicitly says don’t do that, in a round about way).
Sent from my Phone 2 using Tapatalk
-
Deleted.
-
Can I check if the profile sends any keystrokes at all without launching BMS? I’m still not sure how this profile works. I’ve tried others much more simple ones they work by sending series of tttt or 12345 etc to BMS. )) I know I’m missing here something very basic in understanding of how it works I think.
-
Yes you can without runing BMS
Just open a text file and make it active, ready to enter letters (the cursor must flash) . Say you command, and if recognize, you should see the letters and numbers write without anything else. -
I’m trying to figure out how AVCS4 BMS for VA works. I imported both core and AVCS4 bms profiles to VAC, AVCS CORE (v0.92b) is set as Global Profile in General Options (v1.8.7) and AVCS4 Falcon BMS Radios (v1.3.92b) is set to Load Profile on Startup. Core and AVCS4 BMS initialize ok. Alternative All-Humans Mode is OFF, Audio Feedback is On, Default keyboard QWERTY, UHF/VHF PTT mode is ON. I didn’t touch anything else in CORE/AVCS4 BMS profiles. Now I enter 3D and fly around Kunsan, I set UHF to 292.650 Kunsan’s ARR Approach frequency, push and hold my UHF button (UHF is highlighted) and request different approaches starting with: APPROACH Request (any) or APPROACH Declare Emergency…. Nothing happens. I check VAC recognizes commands Ok(green). What am I missing?
Do I need to add key strokes in the profile perhaps (not sure but I don’t think so)?Thanks.
Try turning PTT mode off. See if it all works well. PTT Mode (optional) is merely a helper to prevent recognizing commands during normal speech, but in reality, I rarely find AVCS4 BMS firing off commands when I am just talking to someone and not issuing commands to VoiceAttack.
You don’t need to add anything to the profile to work, but please do understand these profiles are a public beta test, and while so many things function exactly as designed, there are a number of minor issues and quirks that are still being worked out, as well as major systems like PTT Mode which are getting replaced/improved for the next version (ETA is right out the window, lost a week due to a blizzard here in Portland; spotty internet and occasional blackouts make work not worth the effort until this passes).
I have many ideas and many working proof of concepts for so many of the issues you all have reported, and I really appreciate the feedback! There’s only so much I can test myself, I have a modern gaming PC and a 2015 laptop and that’s it - not to mention human factors I could never test for. All these post really help - I’ll keep you all posted and reply when I have made some progress.
Cheers!
Amazdeus75 is correct that when PTT mode is on and set up correctly for a Push and a Release command, releasing this button too fast on a slower computer can cause the command to assume the PTT button is not held. This is also something I am working on improving, possibly using a key listener instead of the current method which sets a boolean variable to ‘true’ when a PTT key/button is depressed, and back to ‘false’ when released.
-
Amazdeus75 is correct that when PTT mode is on and set up correctly for a Push and a Release command, releasing this button too fast on a slower computer can cause the command to assume the PTT button is not held. This is also something I am working on improving, possibly using a key listener instead of the current method which sets a boolean variable to ‘true’ when a PTT key/button is depressed, and back to ‘false’ when released.
Yes, they mentioned that in this thread, I held PTT UHV/VHF buttons much longer but to no avail.
I’ll try vanila CORE/AVCS4 BMS profiles with a notepad first and see if that works.
Thanks!
-
Do I really nead to stop Nahimic app in the services? AV gives warning about it.
Thanks.
-
I imported both core and AVCS4 bms profiles to VAC, AVCS CORE (v0.92b) is set as Global Profile in General Options (v1.8.7) and AVCS4 Falcon BMS Radios (v1.3.92b) is set to Load Profile on Startup.
Is that right?
Thanks.
-
I opened Notepad and saw AVCS4 Falcon BMS Rdios (v1.3.92b) profile printed my commands at last!
Why when I say:‘approach declare emergency’ all works good, keystrokes are sent, but when I say:‘tower declare emergency’ there are 2 red warnings: Key down by variable [~slection_key] not set. No keys pressed. and Rlease by variable [~selection_key] not set. No keys released. ? Keys not assigned perhaps? How to fix this?
Thanks.
-
Why when I say:‘approach declare emergency’ all works good, keystrokes are sent, but when I say:‘tower declare emergency’ there are 2 red warnings: Key down by variable [~slection_key] not set. No keys pressed. and Rlease by variable [~selection_key] not set. No keys released. ? Keys not assigned perhaps? How to fix this?
Thanks.
Same happens btw with ‘Tower say again’, ‘Tower abort’ - the communication is reconginzed (green) but gives red squares and no keystrokes are sent?
Thanks.
-
Do I really nead to stop Nahimic app in the services? AV gives warning about it.
Thanks.
This should not be an issue. I get that warning too, it’s related to an audio driver. Don’t worry about it.
(re. “I imported both core and AVCS4 bms profiles to VAC, AVCS CORE (v0.92b) is set as Global Profile in General Options (v1.8.7) and AVCS4 Falcon BMS Radios (v1.3.92b) is set to Load Profile on Startup.”)
Is that right?
Thanks.
Yes - that is just fine. Fastest way is to set BMS as a preferred profile in AVCS CORE, and set AVCS CORE to be the startup profile, but we’re talking about a difference of maybe 1 or 2 seconds faster load time, so don’t worry about it.
You also don’t need to set AVCS CORE to a Global Profile, but it won’t hurt anything. AVCS4 BMS physically includes the necessary commands from CORE so that users do not need to set CORE as a global profile or include it into BMS profile. AVCS CORE is designed to be able to function as a Global Profile in the event someone wanted to use it for other games, such as with the (optional) included AVCS CORE Template Profile in this beta, so there will be no issues however you set it up. If there are, please report them.
I opened Notepad and saw AVCS4 Falcon BMS Rdios (v1.3.92b) profile printed my commands at last!
Why when I say:‘approach declare emergency’ all works good, keystrokes are sent, but when I say:‘tower declare emergency’ there are 2 red warnings: Key down by variable [~slection_key] not set. No keys pressed. and Rlease by variable [~selection_key] not set. No keys released. ? Keys not assigned perhaps? How to fix this?
Thanks.
This may be an actual issue, like the “Check My Six” vs. “Clear My Six” bug we found earlier. I will look into this and reply back here by tomorrow. If this is a missing key, I can just patch it out and push out another live update (patch) while I continue to work on the next download full version update. Thanks!
-
This may be an actual issue, like the “Check My Six” vs. “Clear My Six” bug we found earlier. I will look into this and reply back here by tomorrow. If this is a missing key, I can just patch it out and push out another live update (patch) while I continue to work on the next download full version update. Thanks!
Please patch ‘Tower say again’, ‘Tower abort’ as well.
I like very much now how your profile recognizes my voice commands (on the notepad). I’d really like to learn how manipulate your Core and BMS Radios to a reasonable extent. Therefore I’d like to ask more questions about your package if you don’t mind:
-
How to set BMS as a preferred profile in AVCS CORE? )) Then (I’m using a batch file launcher) I’d like VA load up BMS by default - I guess I’ll remove AVCS CORE from Global Profiles menu in VA Options but leave AVCS4 Falcon BMS in Load Profile on Startup there, is that correct?
-
If I wanted to add a couple of my own simple cockpit switchology voice commands to your BMS how would I do that?
These are enough for now. I’ll try and go flying with your voice profile and see how it works in flight.
Many thanks!
-
-
Another note: it’s strange, but your Core doesn’t recognize my ‘yess’ well for some reason, could you add say ‘affirmative’, ‘positive’, ‘go on’ to the yes confirmation?
Thanks.
-
If I may ask more: Generally I’d like VA to stay idle (not listening) until I press and hold PTT button, in this case either COMM1 or COMM2 joystick buttons. Both of these buttons should turn on listening and recognition for BMS specific voice commands and any other custom ones added.
Thanks.