AVCS4 Immersive Voice Control Radios for VoiceAttack

[SemlerPDX]

@danster:

Bug report saved!

I don’t see it among the bug reports on my website here: https://veterans-gaming.com/semlerpdx-avcs/bug-reporting/

This may indicate that nothing at all is working properly in your case…. it should have opened my website to a new report page, told you to place your cursor in the large text are, then say ‘Ready’ or ‘Done’ to paste the report contents (bbcode formatted, you can review before posting) then press ‘Save’ on the webpage to post the report.

As an alternative, can you please say, “Open the Error Log” and then manually create a New Bug Report at my site* (just fill out the minimum number of required fields, then paste the contents of the Error Log into the large text area at the bottom and click ‘Save’ to post this report on my website. I’ll review the log as soon as I have time.

*IF this error log is blank, then please post up and we’ll have to chat in Discord or something with faster back-and-forth, because that would indicate some ‘new user curve balls’ that I had not anticipated, and if we can find out how you got down that road, we can help make sure no one else runs into your specific issues in the future.

Click Here to create a Manual AVCS Bug Report: https://veterans-gaming.com/semlerpdx-avcs/bugs/

[danster]

Manual report saved.

I did try the Create Bug Report process via VA , but the voice command after “Create a Bug Report” says "Are you sure…."and cuts off. Sorry if I’m being dumb. Anyway I continued the process, the website came up, I clicked as directed and got a “Report saved” message.

[Judy1301]

Hello SemlerPDX. First let me thank you for your amazing VA BMS profiles. I’ve been using them for ages, with a lot of satisfaction.
I’m back in BMS 4.35 after a few months with DCS, but I have an issue. I’ve installed your latest CORE and BMS profile and the installation went smoothly. The problem is in the time necessary for BMS to react to my vocal commands. I’ve timed it and between the moment I say, for instance, “Request taxi for departure” and the moment the command is actually sent to BMS, it sometimes take 20-30 seconds. I remember your previous profile with the blue radio menus scrolling almost instantly. Now, it takes the profile 10 seconds to go from one menu page to the next. Please note that I also use the Viacom Pro profile for DCS and that it could be something in the VA settings. I hope you can help me with this because it can be annoying. Imagine the time it takes before I get an answer to my “Declare” calls
Thanks for your help

Judy

[SemlerPDX]

@danster:

Manual report saved.

I did try the Create Bug Report process via VA , but the voice command after “Create a Bug Report” says "Are you sure…."and cuts off. Sorry if I’m being dumb. Anyway I continued the process, the website came up, I clicked as directed and got a “Report saved” message.

This is my official bug reporting page, https://veterans-gaming.com/semlerpdx-avcs/bug-reporting/, and the last new report listed is from September 3rd 2020. There are no new posts pending approval in the approval queue, so I’m not sure if we are having a miscommunication issue here or what. Please go to this link, click ‘Create a New Report’ and copy/paste the contents of your AVCS Error Log in the comments section (say, “Open the Error Log”)

If you are unable to get that voice command to work, you can find the physical file located at:

%ProgramFiles(x86)%\VoiceAttack\Apps\AVCS\core_errors.log

If this file does not exist, or if it is empty, then please let me know here. This would indicated much deeper issues down to basic AVCS CORE profile initialization failing before even getting to AVCS4 BMS profile issues, let alone other command issues you are having.

@Judy1301:

Hello SemlerPDX. First let me thank you for your amazing VA BMS profiles. I’ve been using them for ages, with a lot of satisfaction.
I’m back in BMS 4.35 after a few months with DCS, but I have an issue. I’ve installed your latest CORE and BMS profile and the installation went smoothly. The problem is in the time necessary for BMS to react to my vocal commands. I’ve timed it and between the moment I say, for instance, “Request taxi for departure” and the moment the command is actually sent to BMS, it sometimes take 20-30 seconds. I remember your previous profile with the blue radio menus scrolling almost instantly. Now, it takes the profile 10 seconds to go from one menu page to the next. Please note that I also use the Viacom Pro profile for DCS and that it could be something in the VA settings. I hope you can help me with this because it can be annoying. Imagine the time it takes before I get an answer to my “Declare” calls
Thanks for your help

Judy

Hello there, and thanks for the kind words! I feel just awful about these keypress timing issues, especially since I believe I have them sorted out for the next version yet have been delayed for the last few weeks working on a major website update and overhaul. If you are from a country that expresses Pi as 3,14 (as opposed to my countries standard of 3.14) then this is part of the soon to be patched out (hopefully) international decimal separator issue that has stumped me for around 6 months. I honestly never knew that other countries around the world may use a ‘comma’ for this, and felt I was a bit worldly after ten years running an international gaming community Live and learn!

Any of my voice commands which use keypresses or keypress macros can be tested using a simple blank notepad - call a command, and watch the letters type out. If there is larger than 0.10 second (max) delay between keypresses, then it is indicative of the international decimal separator issue. If you are not from a region which uses ‘comma’ or ‘,’ for decimal separator, then it could be that my previous failed attempt to resolve this for some users is failing to detect which to use.

We just got several inches of snow dropped on my city, a city that doesn’t get snow most years, so everything is shut down until it melts and I guess I’ll use the time to get this new version with so many fixes and corrections wrapped up and released. I meant to have it out first week of Feb before I got so busy.

If you’re able:
A temporary solution (if you are familiar with VoiceAttack, and command editing, and won’t suffer a brainz explosion working with one of my commands) you can manually force two decimal variables to hard-set to a valid decimal number.

AVCS_BMS_TimeBetweenKeys
AVCS_BMS_TimeKeyIsHeldDown

Edit the profile, open the command, “[yes;yep;yup;yeah;S;U.S.;guess] _”
(under the category ‘Commands - Systems - Voice Authorization Scripts’)

This command has no real actions, it’s just a recognition helper For a quick fix, we can add in a couple Decimal Variables, and then say, “yes”, and it will run and set (fix) these for you *(and say this at least once each time after you finished loading AVCS4 BMS in a new session):

Set decimal [AVCS_BMS_TimeBetweenKeys] value to 0.05
Set decimal [AVCS_BMS_TimeKeyIsHeldDown] value to 0.05

Like this:
- _

[Judy1301]

Thanks a million !!! That did the trick
I now have a very reactive response with your profile.
I indeed live in a 3,14 country (Belgium), but my keyboard is US QWERTY, just like my default language and regional settings set to US English in WIN10.
Your profile is excellent and your service second to none :clap2:

[Amadeus75]

Another big thumbs-up from Austria (QWERTZ, German Language and “3,14”).
Your workaround works like a charm
Thank you for your awesome efforts - I’m happy to use 1.3.92b again.

[Wingedsky]

Hi Semler, here is an other post about PTT. Sorry for That
0.92b Core and v1.3.92b AVCS4BMS installed, PTT Buttons Assigned in AVCS4 BMS (UHF and VHF press and release). Initialization ok

W10, VAv1.8.7.12 x32 in administrator mode, Listening ON, PTT mode ON.

When I first try to say a command, recognition is green, and nothing write in the test text file. Nice, it works as expected.
UHF ON, Declare, q2 on text file, cool …
UHF OFF (release), declare again, and … q2 again… WTF… try with VHF ON ,Declare , q2 … Hummmm:?
I try with other commands and AVCS reacts as if PTT mode is OFF.

I shut down VA, relauch it, try an other command, then same behaviour.

I think I do something wrong.
I read at least 3 times all the 14 pages and can’t find what is wrong.

Maybe some idea, help ?

[SemlerPDX]

@Amadeus75:

Another big thumbs-up from Austria (QWERTZ, German Language and “3,14”).
Your workaround works like a charm
Thank you for your awesome efforts - I’m happy to use 1.3.92b again.

Thank you for the report - patch has been released, simple config update so everyone will get it next time they load AVCS4 BMS - no need to download or import a new profile version or anything. Will copy my reply here:

Okay - now I can see exactly what the issue is, and it makes sense, too. It seems that I did not add in the specific keypress variable for that command, where it was formerly (incorrect) “Check My Six”, and I added the correct phrasing to that for “Clear My Six” but not it’s keypress counterpart (7)

I’ve patched this up, and pushed it out for all users. Just follow the prompt next time you restart VoiceAttack and load AVCS, and it will apply.

I will get the next full profile update released before too long, including the fix for handling international decimal separators, and other fixes/improvements. As always, I really appreciate everyone’s patience and support through these beta test rounds… I know they are long, and I’m a bit of a perfectionist, but I’m just one guy and it’s a passion project.

[SemlerPDX]

@Wingedsky:

Hi Semler, here is an other post about PTT. Sorry for That
0.92b Core and v1.3.92b AVCS4BMS installed, PTT Buttons Assigned in AVCS4 BMS (UHF and VHF press and release). Initialization ok

W10, VAv1.8.7.12 x32 in administrator mode, Listening ON, PTT mode ON.

When I first try to say a command, recognition is green, and nothing write in the test text file. Nice, it works as expected.
UHF ON, Declare, q2 on text file, cool …
UHF OFF (release), declare again, and … q2 again… WTF… try with VHF ON ,Declare , q2 … Hummmm:?
I try with other commands and AVCS reacts as if PTT mode is OFF.

I shut down VA, relauch it, try an other command, then same behaviour.

I think I do something wrong.
I read at least 3 times all the 14 pages and can’t find what is wrong.

Maybe some idea, help ?

Be sure you have set both a “PRESS” as well as a “RELEASE” for each of the buttons. That behavior would happen if you had not set the “RELEASE” commands to the same button(s) respectively. What they do is return a boolean variable to ‘false’ in this current version, so since they have not been set to a key to fire each time it is released, this bool never goes back to ‘false’, and PTT mode is basically overridden and essentially ‘off’. Get those set and you’re good to go!

I feel for ya, don’t worry, this is all on voice command in the next version, hopefully coming as early as next weekend (or sooner). You’ll all no longer have to ‘manually’ edit dummy commands just to assign your desired Push to Talk keys (or Release to Talk hehe) – this new voice controlled PTT key/button assignment system is great, just a little more testing and polish, and it’s ready for prime time. The next release may be the end of the beta rounds, with more improvements coming in time such as the teased themed GUI’s, and others.

[Wingedsky]

Thanks for the answer Semler, but yes the log screen is very clear : both UHF and VHF are pressed, then released …
For sure I do something wrong but can’t find what …

[Amadeus75]

@SemlerPDX:

Thank you for the report - patch has been released, simple config update so everyone will get it next time they load AVCS4 BMS - no need to download or import a new profile version or anything. Will copy my reply here:

“Clear my six” is running fine now.
Your auto-update-thing ROCKS

[Suriken]

Are you talking about voice control here?
Works very well VoxCommando.
Here is an example of commands, though in Russian.
Do not look at piloting. This is an example of voice control.

[Wingedsky]

@Wingedsky:

Thanks for the answer Semler, but yes the log screen is very clear : both UHF and VHF are pressed, then released …
For sure I do something wrong but can’t find what …

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 array

Could it be in relation with my issue ?

[Amadeus75]

Wingedsky, maybe I found out something (maybe not, but let’s try).

Press the key, say the command… but then WAIT until the command is recognized before releasing.
The “moment of recognition” must fall inbetween of “press” and “release”, I guess.
Just leave your thumb on the button for a second longer.

[SemlerPDX]

@Wingedsky:

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 array

Could 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!

[Wingedsky]

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:

[CriticalMass]

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)

[Mylonite470]

@CriticalMass:

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.

[Sabre]

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.

[Amadeus75]

@Sabre:

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” ;))