AVCS4 Immersive Voice Control Radios for VoiceAttack
-
@SemlerPDX, many thanks for your extensive error searching support! I put the “UHF/VHF Push-To-Talk Mode” to OFF, and your profile works fine in that mode. Hence, it is my TQS COMMS buttons that don’t work properly. I have them correctly mapped in BMS, that I know, and they work fine with the “UOAF Advanced VoiceAttack Profile”. Still a big mystery to me. I cannot figure that one out. I would love to use the PPT mode with your profile, if possible. Any clues on where I may have it wrongly setup? Note that I use TUSBA, and I just installed it a couple of days ago.
Sure - just open up VoiceAttack Options and setup that controller for VoiceAttack - then you need to edit each of the VHF PTT Push & VHF PTT Release and the UHF PTT Push & UHF PTT Release commands inside my profile (top section, under initialization), and follow instructions inside those commands to set their ‘When I press button:’ to your respective joystick buttons. Lots of info in the AVCS info pics here: https://imgur.com/a/xuclI0a
-
Thank you! I had only assigned the joystick under the Joystick Options and not assigned the UHF and VHF buttons within your profile. Now I understand how it works. Thank you so much for your assistance!
-
You’re welcome! I suppose pics like that one I shared shouldn’t be buried behind a link but more prominent on the main description page - I might make a few better instructional graphics for that PTT system, text instructions are a pain especially for our friends who don’t speak English as their first language. I will include them in the next version when I implement this new Save File System I’m just finishing up for my Elite: Dangerous AVCS4 profile.
Glad you got it working! Cheers!
-
Happy to announce version 1.4 just around the corner. Coming next, I’ve created a save file system to maintain user defined settings (PTT Mode On / Audio Feedback / Keyboard Regional Layout / etc.) between updates, as well as a live update system for minor patches to systems initialization, where a majority of my AVCS4 profile gets it’s operating information.
To put it plainly, in the next and all future versions, a missing variable or typo in one of the commands like INIT_KEYPRESSES can be pushed out almost instantly to any users of AVCS4 when I receive the report (1.3 exists because 1.2 had a simple typo in the new Carrier Ready for Departure command, in the init file only). Imagine one of the text-to-speech item variations had a problem, and was saying a word wrong, I could change that TTS variable on my end, and push it out to all users who would get it almost instantly when loading the profile.
I tried a test of more than 2kb (the entire keypress init without comments is only 7kb) of info and a hundred variable updates and couldn’t increase the profile init time past 1 second, so it’s fast, powerful, and will allow featureless updates without re-downloading new profiles.
Additionally, the 1.4 version will feature an update notification system, too, to let users know of any major updates that require a manual profile update, with minor bug-fix patches being installed silently on profile load.
Never again will a typo require an AVCS4 “download new version”! For every AVCS profile or profile builder module I make for any game (BMS, Elite Dangerous, ARK/ATLAS, the Voice Controlled Profile Builder, etc.), any custom user saved settings will no longer be lost due to profile update/delete, or even complete windows reinstall (save file backup system included).
**ETA - about 3-4 weeks
Happy New Year and see you at Angels 20!**
-
Excellent news! Looking forward to the release.
Sent from my iPhone using Tapatalk
-
This post is deleted! -
Hi SemlerPDX,
first of all a BIG THANK YOU for making this profile public and supporting it!
It’s just so user-friendly and works (with some speech training) so well.Never the less i think i found a small bug. When i was giving the command to “Activate Radar”, it would recognize the command, but would only send “wwww”, the “4” was missing.
So i checked the profile options to see why. It took me some time to figure out how this all workshttps://i.imgur.com/grdsGFy.png
https://i.imgur.com/WJzCgd2.pngSo i fixed variable in the INIT section to match the recognized command –> “ActivateRadar”, now it works.
cheers
Magic -
just wow… man you’re amazing. 1.4 sounds like its going to be great!
-
Hi SemlerPDX,
first of all a BIG THANK YOU for making this profile public and supporting it!
It’s just so user-friendly and works (with some speech training) so well.Never the less i think i found a small bug. When i was giving the command to “Activate Radar”, it would recognize the command, but would only send “wwww”, the “4” was missing.
So i checked the profile options to see why. It took me some time to figure out how this all worksSo i fixed variable in the INIT section to match the recognized command –> “ActivateRadar”, now it works.
cheers
MagicI am unable to see your attachments.
*Recommended SOP until the upcoming version with my new AVCS Core and it’s integral Bug Reporting System linked to my website -> drag image onto www.imgur.com and copy the link, drop link here in message.
I believe I have identified the issue you discovered – the variable holding the info is currently:
Set Text [AVCS_BMS_KEY_WINGMAN_ActiveRadar] to '4'
And it should be “Activatate”
(once again a typo style error in config that will easily be resolved in future versions through AVCS Core’s Live Update System with a simple edit, pushing the fix to all users next time they load the profile… coming soon, I promise!!)
I have noted the change and will make sure it is correct when I drop the 1.4 version. Still have a few things to do, but shouldn’t be too much longer. Been spending 10+ hours a day getting my AVCS Core program finished, it will power every profile I create (not just AVCS4 for BMS, but my Elite Dangerous, Arma 3, etc. etc. all using various common modular profile systems like VAS, SFS, GLS, etc. all powered by CORE with Live Updates and integral Bug Reporting).To anyone using this profile now, to fix the above issue now just do as Magic49th did:
Open AVCS4 Profile to Edit:
- Open the command ‘KEYPRESS_Variables →→→((ADJUST AI COMMS LISTS & KEYS USED BY THIS PROFILE HERE))←←←’
- Scroll down to the section with many variables starting with ‘AVCS_BMS_KEY_WINGMAN_’
- Locate the specific entry labeled ‘Set Text [AVCS_BMS_KEY_WINGMAN_ActiveRadar] to ‘4’’
- Change the word “ActiveRadar” to “ActivateRadar”
*Must also be done for “ELEMENT” and “FLIGHT” variables, too:
-
Scroll down to the section with many variables starting with ‘AVCS_BMS_KEY_ELEMENT_’
-
Locate the specific entry labeled ‘Set Text [AVCS_BMS_KEY_ELEMENT_ActiveRadar] to ‘4’’
-
Change the word “ActiveRadar” to “ActivateRadar”
-
Scroll down to the section with many variables starting with ‘AVCS_BMS_KEY_FLIGHT_’
-
Locate the specific entry labeled ‘Set Text [AVCS_BMS_KEY_FLIGHT_ActiveRadar] to ‘4’’
-
Change the word “ActiveRadar” to “ActivateRadar”
teaser pic with a blog entry on what is in development for AVCS4 and what is coming: imgur.com/x0xPzyV
-
I’ve uploaded the pictures to Imgur, see my previous post.
cheers
Magic -
I am unable to get this to work. After importing it and reenabling plugin support selecting the profile mostly freezes VA (coupled with high ram/cpu usage), and killing it prevents it from being launched again (the tray shows up and the right click menu works but the UI won’t come up and I get the same high resource use as when first trying to load it) until I delete the dat file from appdata. I’m using 1.8.3, Steam version.
-
I am unable to get this to work. After importing it and reenabling plugin support selecting the profile mostly freezes VA (coupled with high ram/cpu usage), and killing it prevents it from being launched again (the tray shows up and the right click menu works but the UI won’t come up and I get the same high resource use as when first trying to load it) until I delete the dat file from appdata. I’m using 1.8.3, Steam version.
I’m not sure what could cause an issue like that. None of us have had that one yet, but I bet we can work through it…
Can you please find the VoiceAttack Errors log and post up a copy or download link?
If you have 64-bit Windows, this file should be found at:%ProgramFiles(x86)%\VoiceAttack\VoiceAttackFault.txt ```If you have 32-bit Windows, or it is not found at the above path, the file may be located at:
%ProgramFiles%\VoiceAttack\VoiceAttackFault.txt
A few questions: 1. I don't want to assume too much - so I'll just ask if this is your first use of VoiceAttack, or just first use of my profile? 2. Have you set up and created a Windows Speech Recognition Profile per VoiceAttack first use instructions? 3. You are not using a trial version, but full paid version, correct? 4. Have you used or installed any other profiles in VA? 5. If 'yes', then do these profiles function normally after failing to import my profile package? If you could get back to me with those answers and a copy of the Faults log, there may be a few more questions to narrow this down, but I'm willing to work with you until we get this resolved. It is certainly an edge case and not the standard experience most of us have had, and I feel bad for you. These things happen - but for things like this, every problem has a solution even when it's not apparent at first. *It might help if you'd post up basic computer/laptop specs for your system, so we could be sure it's above minimum - unless you're sure it's a modern system. This profile was designed and exported from an i5-4690K system from 2015, I know it at least functions fast and well as far back as this Haswell CPU.
-
I’m on Skylake. I’ve got it to work but it seems that what was breaking things was actually plugin support being enabled. Disabling it fixed the problem. Which is an issue, because indeed, this is not the only thing I use VA for, I also use VAICOM for DCS and that definitely requires plugin support to be on. And I don’t think one can have multiple separate installations of VA on the same system.
-
hmm… my profiles v1.3 and prior do not use or require plugins.
The warning during import is because the profile package does put an AVCS folder in the VoiceAttack Apps folder with the info pics link, etc., as well as the Audio Feedback Mode sound files in the Sounds folder, also under the VoiceAttack Apps location. The next version will use an app, but again, not plugins, and in fact, during testing and building it now, I have plugins disabled (I have a few for Elite Dangerous, and for Ivona Reader).And with those disabled (or enabled) I can fly in BMS right now with AVCS4 v1.3 – so we might want to ask around someone who might know more. I’m not sure what other details to ask for at this point. Like I said, this seems to be a rather rare edge case, and I’d love to find the solution to help you out, and in the event it pops up again.
If you can’t even get it imported, I guess any error messages I made for users aren’t getting a chance to tell you if anything is wrong. But you’re running the recent version of VA, your system is more than capable, and if anything wasn’t set correctly, it would import but throw error messages.
I’m wondering if simply the download got borked along the way – can you try simply downloading the file again, and try it all again? You’re not trying to import the profile package from within the download zip, are you? I mean I suppose that wouldn’t even be possible, just stumped for things to ask or try, sorry bro.
*edit: do check the VoiceAttack faults log file referenced in my last post directly following a failed import attempt - it may be that your VoiceAttack app needs to be validated through Steam, or perhaps something in my profile does not play well with the Steam edition. Either way, I’ll be asking Gary and/or the others if there is something that could be at fault in VA, but I’ll need any fault log output related to this (and I can’t reproduce the error, so we’d need that from you)
-
It does import without errors, everything breaks once I try switching to this profile. Once I do, VA hangs with high CPU/RAM usage and will not work upon restart until I actually clear the dat file in appdata (deleting the profile in process). I don’t even have any log files, it seems it never got chance to produce them. And it actually worked for some time (after I completely reinstalled VA, I would add) but then it ultimately broke again and I couldn’t get it to work since.
-
It does import without errors, everything breaks once I try switching to this profile. Once I do, VA hangs with high CPU/RAM usage and will not work upon restart until I actually clear the dat file in appdata (deleting the profile in process). I don’t even have any log files, it seems it never got chance to produce them. And it actually worked for some time (after I completely reinstalled VA, I would add) but then it ultimately broke again and I couldn’t get it to work since.
Understood.
I’m surprised there isn’t a fault log at all, just for the random things that happen over time with VoiceAttack, not involving my own profile, but other issues - if VA ever crashes under other circumstances, the file will exist. I can only assume in all the time you’ve used VoiceAttack that it’s never crashed – also, could be that a Steam Version has the file in a different location, and if that is the case, the reasons for all of this would be in that log.
Again, this is a very unique issue, there are at least a hundred people who have used this profile including myself, through various versions from the standalone to the Steam Edition, and this has not popped up yet. It must be something related to your OS environment, other software that may be running including anti-virus or malware protection, or the VoiceAttack installation itself. I’d still like to help you get past this issue, but if you cannot locate a proper VoiceAttack fault log file, I’m afraid only some of the moderators at VoiceAttack would be able to help you.
…
If you’re still interested in working through this, I’d suggest posting up this issue on the VoiceAttack forums in the Issues section, or pop on over to the VA Discord to the People-helping-People channel where many people are happy to help others with VoiceAttack. I’m sure they are familiar enough with my profile to know it’s not been created improperly or is unable to function within the VoiceAttack program as designed, so should direct you towards technical help regarding your VA installation, etc.Again, just to be clear - the SOP would be to download my profile from the download section on my website, to extract the files from the zip, and then to import the .vax package labeled “IMPORT THIS”. I assume you’ve done that, but just wanted to be sure you’re not trying to import the download .zip - apologies, sometimes troubleshooting questions can sound downright insulting, and that’s not my intent. Best wishes and good luck! I’ll be following any support issue you post on the VA website or discord to make sure I learn what went wrong for myself as well.
-
It did not crash indeed. It just freezes and maintains high CPU/RAM usage forever until I kill it. And I’m not retarded, I wouldn’t be able to get it working at all if I was trying to import the zip. It did work for some time until this stuff started happening again. I’ll try removing my speech recognition profile and regenerating it from scratch.
-
It did not crash indeed. It just freezes and maintains high CPU/RAM usage forever until I kill it. And I’m not retarded, I wouldn’t be able to get it working at all if I was trying to import the zip. It did work for some time until this stuff started happening again. I’ll try removing my speech recognition profile and regenerating it from scratch.
Roger that. Again, no offense intended, just asking questions. Also, removing the speech recognition profile may have nothing to do with this issue with no information pointing to that as an issue, but crazy things can happen in VA when the WSR profile gets borked. You may also want to backup that profile before hand so you could restore it if it wasn’t the issue - here’s a tool for the job: https://www.dropbox.com/s/9b6ffxxkm00bu2o/Windows_Speech_Profile_Backup_Tool.rar?dl=0
*re. crashes, I did not mean with this profile issue, I meant ever in the history of the time you’ve owned and used VoiceAttack, again, assuming this isn’t the first time/first profile you’ve been using.
-
I never had issues like those before. I used VAICOM for DCS (which is a plugin, not just a profile) and the UOAF profile for Falcon. That was before 1.8 version of VA came along though.
Resetting the Speech profile didn’t work, I’m still having the issue. I’m gonna try digging deeper.
EDIT: Upon digging deeper I discovered I had multiple config directories in %localappdata%\VoiceAttack.com. Deleting them and letting VA regenerate config seems to have fixed the issue for now.
EDIT2: Bingo! I found out what was triggering the issue. It gets triggered by checking “Allow Command Segment Info for Composite Commands”. That’s why deleting config fixed it. It seems that VA can’t handle a profile this complex with this option on, at least on my system. I’ll let it sit for some time and see if it unhangs, if it doesn’t I’ll just refrain from using this option.
-
I never had issues like those before. I used VAICOM for DCS (which is a plugin, not just a profile) and the UOAF profile for Falcon. That was before 1.8 version of VA came along though.
Resetting the Speech profile didn’t work, I’m still having the issue. I’m gonna try digging deeper.
EDIT: Upon digging deeper I discovered I had multiple config directories in %localappdata%\VoiceAttack.com. Deleting them and letting VA regenerate config seems to have fixed the issue for now.
EDIT2: Bingo! I found out what was triggering the issue. It gets triggered by checking “Allow Command Segment Info for Composite Commands”. That’s why deleting config fixed it. It seems that VA can’t handle a profile this complex with this option on, at least on my system. I’ll let it sit for some time and see if it unhangs, if it doesn’t I’ll just refrain from using this option.
Oh boy, that would just about do it. Likely less an issue with your system, and more a limit with the 32-bit VoiceAttack application, combined with the prefix/suffix use in AVCS4.
I suppose you had a profile that was using that or needed that? I will make sure to inform people about that on the download page, readme, etc. and I put a note on this reply to hopefully help anyone searching through this post in future.IIRC that’s an option for rare use case scenarios that Gary added a ways back to help simplify prefix and suffix command words evaluations, and I use much less resource intensive methods in my AVCS profiles. I have 3 prefixes each with over 1,500 potential combinations, and that’s before all the non-wildcard radio commands themselves (if it’s to a flight member, it’s a prefix/suffix combo - if it’s to the AI like tower/awacs/tanker, it’s a wildcard command). It’s actually best to not get into prefix/suffix use when it can be avoided and when CMDSEGMENT evaluation is heavily needed; each method has it’s purposes and using a large number of prefixes for a rather smaller number of suffix commands that all use that command starting phrase is about the only time it’s the best method to use over all the ways you can do things in VA, especially for dynamic multi-part composite commands.
A few commands with a few thousand options, or a several hundred commands with a few options…
I’m big on using the fastest methods for items, it’s why the eval for playing Audio Feedback exists in each and every command instead of just a single ‘function’ command that gets called from any command. These types of combos are also great for switches/toggles/on and off commands that all share those sentence structures in a dynamic multi-part composite format, and using methods other than CMDSEGMENT to pass the type of prefix used to the suffix with the body of the command actions.