AVCS4 Immersive Voice Control Radios for VoiceAttack
-
@jc1:
Is the game supposed to repeat your command after you give it through voice command?
Kinda redundant, though, isn’t it? If you need positive feedback for recognition, you could say, ‘Turn on Audio Feedback Mode’ to play a short radio cue sound so you know your command went through and fired an AVCS4 keypress macro.
-
Why does this profile require access to my system32 folder?
8:02:45.053 Inline function execution exception: Exception has been thrown by the target of an invocation. Access to the path ‘C:\Windows\system32\92D60AC8C0E3D’ is denied.
-
Why does this profile require access to my system32 folder?
8:02:45.053 Inline function execution exception: Exception has been thrown by the target of an invocation. Access to the path ‘C:\Windows\system32\92D60AC8C0E3D’ is denied.
92D60AC8C0E3D contains your GUID for AVCS. It is a flat text file that contains a SHA hash for unique user identification. Presently, it is not used, but is part of the system that will allow me to release private/closed beta testing by limited user signup. This file needs to be kept in a safe place outside the VoiceAttack program so that it can persist through reinstallation of VoiceAttack. The system32 folder is one common place for Windows and installed applications to store DLL’s, EXE’s and other files necessary for those programs to function, which is why I chose that place to store the redundant GUID for users. This is also located in the VoiceAttack Apps folder under the relative AVCS profile folder.
In most cases, VoiceAttack needs to be ‘Run as Administrator’ to interact with various Windows programs, etc. When this is not enabled, certain functions such as this check for the GUID in the secondary redundant location may fail. The solution is to run VoiceAttack as Administrator by opening VoiceAttack Options, clicking on the ‘System / Advanced’ tab, and checking the box next to ‘Run VoiceAttack as an Administrator’ – it is also important to ensure ‘Use Nested Tokens’ is checked, and that ‘Allow command segment info for composite commands’ is unchecked – see image below
edit: I wanted to add that I am trying to make a name for myself as a ‘white hat’ developer of voice control systems for games using VoiceAttack, and as a responsible administrator for a non-commercial online gaming community at VG for the past ten years; I use my real name on my work, and by-lines on my articles, and I live in Portland, Oregon, USA – I have no intentions of being an anonymous avatar online and expecting users to install programs I develop on faith alone, and I’m hoping to build a reputation of trust and integrity. I have no commercial designs for my AVCS work, though I do intend to create means for donation support from those who have and wish to continue to offer such, and this may include early or exclusive access to additional features which may comprise thousands of hours of work, as additional layers over the base profiles I release for everyone. For these reasons, I had to design a very basic user identification system that was not easily intuited or bypassed, so that I may be able to protect certain work down the road.
Apologies if actions such as the GUID check in Sys32 for my AVCS initialization has come across as untoward. All I can do is assure you all that I have no interest in harming other users, harming the name I am trying to build as a respectable independent developer of gaming utilities, or of taking advantage of the trust I am trying to build by doing things that could be considered outside the realm of ‘white hat’ program development. I am also a user of AVCS, all day every day, and it operates no differently on my PC as it does for other users, I have a 92D60AC8C0E3D in my system32 folder, too It doesn’t “do” anything, just holds a hash used for ID. You’ll note that it’s last modified date will always match the date of creation, even months down the road.
-
Kinda redundant, though, isn’t it? If you need positive feedback for recognition, you could say, ‘Turn on Audio Feedback Mode’ to play a short radio cue sound so you know your command went through and fired an AVCS4 keypress macro.
And how to you stop the BMS Radio Commands window from appearing?
Edit:
I found the answer in “falcon bms.cfg”. set g_bDisableCommsMenu 1 -
Frequent internet outages following a snap blizzard in the Pacific Northwest US has prevented me from making much headway towards the next version. I am a self taught amateur programmer, so if I tread into new ground such as I’m doing with an active key/button monitor, I find myself browsing all the Stack Overflow and dot-net-pearls for the best and most optimized methods for doing such things, and can’t make any progress when I’m offline. I used the time to wrap up the next version of my voice calculator “AVCS CALC”, and spent some time retraining in ILS ‘bad weather’ landing cuz I’m way out of practice. This is on top of a month that I didn’t know I’d be spending updating and overhauling the VG website, so I’ve blown right past any previous estimates for my next release.
I feel stupid trying to give a new estimate, but honestly, I’ll be cracking away at it this week and next, but I don’t rush things because I want them to work well… specifically, the new key/button listener for the new streamlined PTT Mode. All of AVCS is ‘passive’ to where nothing is looping or waiting except VA and the actual speech recognition engine - this will be a divergence from that, and so I won’t settle for anything but “the best method” so it doesn’t impact performance and can handle exceptions or even turn itself back on in the event that key/button listening has stopped while AVCS4 BMS and PTT Mode are still active and in use.
Again, thanks to everyone for your patience and understanding during these beta test rounds - I am fully hoping the next release will bring these out of beta, and move forward with standard versioning, addressing issues or changes as they come up.
-
I’ve just started using this VA profile and it is absolutely excellent.
Except. I’m in PTT mode, which works really well. Except…
Every now and then, it’ll send random radio commands without me touching the PTT button. I thought with PTT, that NOTHING should get sent unless the com switch is on? most of the time that works - I can sit on the runway and say ready for departure, VA recognises it, but doesn’t send. Then press and hold com switch, and repeat, and the command is sent. So I’m confident that the PTT is working as it should.
(VA also does odd things, but that’s not the fault of this profile - I keep getting asked if I’m sure about random things, or a pop up asking me to copy a profile or key layout.)
-
I’ve just started using this VA profile and it is absolutely excellent.
Except. I’m in PTT mode, which works really well. Except…
Every now and then, it’ll send random radio commands without me touching the PTT button. I thought with PTT, that NOTHING should get sent unless the com switch is on? most of the time that works - I can sit on the runway and say ready for departure, VA recognises it, but doesn’t send. Then press and hold com switch, and repeat, and the command is sent. So I’m confident that the PTT is working as it should.
(VA also does odd things, but that’s not the fault of this profile - I keep getting asked if I’m sure about random things, or a pop up asking me to copy a profile or key layout.)
That is definitely some odd unexpected behavior. There are certainly many, many commands that are not barred by the PTT mode, such as any included AVCS CORE commands, or general AVCS4 BMS non-radio commands. “Turn on Push to Talk Mode” would be a good example of a command that doesn’t respect PTT mode. All of my pop-ups are titled with a prefix of “AVCS”, and VoiceAttack doesn’t do anything on it’s own so this is definitely on me/AVCS (unless you are running other profiles at the same time, or plugins).
Without knowing which commands are specifically firing off, I’d not be able to help much. I suggest that for at least one session, you turn on command logging to file. This will populate the AVCS core errors log file with only the initial command call data (as opposed to full debugging data for each command), and then you can share that text file here and I can review what is happening. To enable this sort of logging, say, “Enable Debug Mode Level 1” – then use the profile as normal. Then, if/when a command is recognized but you didn’t say anything or it asks if you are sure, or a pop-up is shown, say, “Open the Bug Log” – then scroll to the bottom and write in a line to mark this section of the file for later review, save and close it, and return to using AVCS as normal.
Debug Mode is automatically reset to “off” when VoiceAttack is restarted and AVCS reinitialized. You can, of course, say, “Disable Debug Mode”, to turn it back off during a session without having to restart. Level 1 is the only “fast” debugging, levels 2, 3, and 4 slow down the performance of voice commands due to the heavy ‘write’ actions to the VoiceAttack Event Log, or errors log file, or both. These modes are not necessary unless command flow and functions need to be debugged on a line-by-line per-action basis.
Sorry to hear you are struggling with this stuff, there’s probably a simple solution to excessive misrecognition of commands. I assume you have fully trained your Speech Recognition Profile as described in the VoiceAttack Help Manual “Quick Start Guide”, part 5?
*this issue has given me the idea to let us create a mark point in the error log file when using any debug mode level, cuz they can get long and manually having to open it after an errant command as I’ve instructed above just smacks of effort It’s going on the list…
-
Sorry to hear you are struggling with this stuff, there’s probably a simple solution to excessive misrecognition of commands. I assume you have fully trained your Speech Recognition Profile as described in the VoiceAttack Help Manual “Quick Start Guide”, part 5?
Not struggling at all! It’s totally awesome and easy to setup. Yes, have trained the Speech Recogniton.
It’s not struggling to understand me at all - it works really well.
It’s that I can be silently flying along - sometimes on autopilot! - and suddenly the tower or AWACS pages (I think it’s AWACS actually) will flash up and page through, then a radio call is made, and I’ve not touched the PTT at all, or said anything. I guess it’s picking up some noise from my switches or movement against the desk or something, which I expect to happen, but the PTT I thought would exclude any radio calls.
-
Not struggling at all! It’s totally awesome and easy to setup. Yes, have trained the Speech Recogniton.
It’s not struggling to understand me at all - it works really well.
It’s that I can be silently flying along - sometimes on autopilot! - and suddenly the tower or AWACS pages (I think it’s AWACS actually) will flash up and page through, then a radio call is made, and I’ve not touched the PTT at all, or said anything. I guess it’s picking up some noise from my switches or movement against the desk or something, which I expect to happen, but the PTT I thought would exclude any radio calls.
(Poor choice of words on my part - I meant sorry to hear you are struggling to get VA to not recognize/act when you are not speaking to it proper.)
Actually, regarding PTT excluding any radio calls yes, it certainly does. This leads me to think that somehow the actual keys are getting fired such as Q and then a number, but the only way for you to know which is to monitor the VoiceAttack event log (the actual windows) and the phrases that get recognized. And again, if you would like this to happen in the background for AVCS, use the Debug Level 1 method from above where you can use voice commands to open the log and add a mark like “====I DIDN’T SAY THE COMMAND(s) JUST ABOVE THIS LINE===” for easy review later.
Additionally there are a number of settings in the VoiceAttack Options > Recognition tab, and you should review the VA Manual / Help Guide regarding these settings, and set them accordingly to refine the recognition ability of VA. Specifically the confidence level, since this can help avoid things like the sounds of keys tapping getting heard as phrases, and maybe Adaptive Recognition or Echo Cancellation as appropriate for you and your setup. (don’t copy my settings, this pic is for me and my setup, your mileage may vary)
-
Well, I’ve done the debug log. And it now tells me at least which commands it thinks I’m sending.
Annoyingly though, the log doesn’t show when I’ve hit PTT (UHF/VHF) or released, although the main window does.
This is from takeoff. I manually did tower, ready for departure, took off, switched to departure/approach and then did PTT, said “report airborne”. Once, and once only, then I was silent for the rest of the flight. Also, I did not push UHF or VHC comm buttons.
I’m assuming I’ve got something wrong in my config - might erase and start again.
165626478 CID:4313 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:turn off all humans mode 165626511 CID:4313 -DEBUG-000- || RID:500 || CAT:(configuration - BMS) 165638292 CID:4313 -DEBUG-02- || INFO: Executing Sub-Command (F_SFS_DELETE) with RID:4382 - valid Return should == 4616 165638896 CID:2549 -DEBUG-000- || IS:1 || ACT:Spoken || CMD:f_sfs_delete 165638944 CID:2549 -DEBUG-000- || RID:4382 || CAT:Script Functions - Save File System 165638990 CID:2549 -DEBUG-01- || INFO: AVCS_SFS_SAVED_requests = 4 165641870 CID:2549 -DEBUG-02- || INFO: Executing Sub-Command (F_SFS_TO_FILE) with RID:1268 - valid Return should == 1502 165642632 CID:2482 -DEBUG-000- || IS:1 || ACT:Spoken || CMD:f_sfs_to_file 165642679 CID:2482 -DEBUG-000- || RID:1268 || CAT:Script Functions - Save File System 165642725 CID:2482 -DEBUG-01- || INFO: AVCS_SFS_DELETE_saved = True || AVCS_SFS_BACKUP_bypass = False || AVCS_SFS_SORT_bypass = True || AVCS_SFS_RESTORE_backup = False 165648312 CID:2482 -DEBUG-16- || INFO: Executing F_SFS_BACKUP before Saving Changes to file 165648359 CID:2482 -DEBUG-16b- || INFO: Executing Sub-Command (F_SFS_BACKUP) with RID:2937 - valid Return should == 3171 165648924 CID:1582 -DEBUG-000- || IS:1 || ACT:Spoken || CMD:f_sfs_backup 165648972 CID:1582 -DEBUG-000- || RID:2937 || CAT:Script Functions - Save File System 165653071 CID:2482 -DEBUG-17b- || INFO: Sub-Command (F_SFS_BACKUP) COMPLETE -- Return equals 3171 165653712 CID:2482 -DEBUG-15- || INFO: SFS Variable(s) Saved to C:\Program Files (x86)\VoiceAttack\Apps\AVCS\save_files\bms_save\92\save.txt 165655886 CID:2549 -DEBUG-03b- || INFO: Sub-Command (F_SFS_TO_FILE) COMPLETE -- Return equals 1502 165656075 CID:2549 -DEBUG-04- || INFO: F_SFS_DELETE COMPLETE -- ----------------------------------------------- 165658296 CID:4313 -DEBUG-03b- || INFO: Sub-Command (F_SFS_DELETE) COMPLETE -- Return == 4616 165659064 CID:3945 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:the ball 165659094 CID:3945 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Carrier Page 165709861 CID:2200 -DEBUG-000- || IS:1 || ACT:Spoken || CMD:request qfe 165709892 CID:2200 -DEBUG-000- || RID:4616 || CAT:AI COMMS 3 - ATC - Common Page 165712719 CID:1972 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 165712752 CID:1972 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 165715253 CID:1835 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 165715285 CID:1835 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 165717103 CID:4237 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 165717136 CID:4237 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 165738353 CID:2533 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 165738384 CID:2533 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 165741338 CID:4187 -DEBUG-000- || IS:1 || ACT:Spoken || CMD:request qfe 165741368 CID:4187 -DEBUG-000- || RID:4616 || CAT:AI COMMS 3 - ATC - Common Page 165753064 CID:3679 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 165753095 CID:3679 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 165832039 CID:2606 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 165832071 CID:2606 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 165838649 CID:3649 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 165838682 CID:3649 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 165904445 CID:2330 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:the ball 165904477 CID:2330 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Carrier Page 165929759 CID:3874 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:lightning 2 2 165929791 CID:3874 -DEBUG-000- || RID:500 || CAT:AI COMMS - Prefix Words 165954086 CID:3452 -DEBUG-000- || IS:1 || ACT:Spoken || CMD:request qfe 165954118 CID:3452 -DEBUG-000- || RID:4616 || CAT:AI COMMS 3 - ATC - Common Page 170010357 CID:1879 -DEBUG-000- || IS:1 || ACT:Spoken || CMD:tower say again 170010389 CID:1879 -DEBUG-000- || RID:4616 || CAT:AI COMMS 3 - ATC - Tower Page 170033891 CID:3700 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:lion 170033923 CID:3700 -DEBUG-000- || RID:500 || CAT:AI COMMS - Prefix Words 170041159 CID:1692 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:ready for departure 170041190 CID:1692 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Tower Page 170045301 CID:1624 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:ready for departure 170045333 CID:1624 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Tower Page 170104285 CID:4055 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:the ball 170104317 CID:4055 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Carrier Page 170115555 CID:1346 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 170115586 CID:1346 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 170131938 CID:2964 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:report airborne 170131968 CID:2964 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 170147531 CID:1609 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 170147563 CID:1609 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 170150062 CID:2806 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 170150093 CID:2806 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 170153428 CID:1160 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 170153461 CID:1160 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 170201332 CID:2497 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 170201362 CID:2497 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 170212018 CID:3918 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 170212050 CID:3918 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 170225288 CID:2543 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 170225288 CID:2543 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 170225318 CID:2543 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 170249232 CID:2373 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 170249264 CID:2373 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 170252015 CID:3358 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 170252046 CID:3358 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 170634460 CID:2987 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 170634491 CID:2987 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 170753954 CID:1223 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 170753983 CID:1223 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 171054389 CID:2508 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:the ball 171054421 CID:2508 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Carrier Page 171200681 CID:2705 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 171200711 CID:2705 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 171314531 CID:4014 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 171314564 CID:4014 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 171328132 CID:2767 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 171328163 CID:2767 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 171333998 CID:3462 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 171334031 CID:3462 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 171447592 CID:2427 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 171447623 CID:2427 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 171542324 CID:3990 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 171542354 CID:3990 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 171542948 CID:1156 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 171542979 CID:1156 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 171608895 CID:3088 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 171608926 CID:3088 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 171649655 CID:1697 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 171649685 CID:1697 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 171652780 CID:1435 -DEBUG-000- || IS:1 || ACT:Spoken || CMD:request unrestricted approach 171652811 CID:1435 -DEBUG-000- || RID:4616 || CAT:AI COMMS 3 - ATC - Approach Page 171702126 CID:3738 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:request unrestricted approach 171702156 CID:3738 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Approach Page 171709528 CID:3545 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 171709559 CID:3545 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 171724692 CID:3426 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:the ball 171724724 CID:3426 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Carrier Page 171743449 CID:3801 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 171743481 CID:3801 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 171751321 CID:2036 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 171751352 CID:2036 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 171755049 CID:1658 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:request landing 171755080 CID:1658 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Tower Page 171755080 CID:1658 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Tower Page 171800938 CID:1698 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 171800969 CID:1698 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 171825909 CID:3544 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 171825939 CID:3544 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 171857483 CID:1347 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 171857514 CID:1347 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 171947376 CID:2091 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 171947405 CID:2091 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 172011478 CID:1188 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 172011511 CID:1188 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 172049573 CID:4173 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:report on final 172049605 CID:4173 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Tower Page 172248840 CID:1337 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 172248870 CID:1337 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 172302418 CID:2542 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 172302449 CID:2542 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 172312548 CID:2483 -DEBUG-000- || IS:1 || ACT:Spoken || CMD:request taxi for departure 172312581 CID:2483 -DEBUG-000- || RID:4616 || CAT:AI COMMS 3 - ATC - Ground Page 172325118 CID:2800 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:request taxi to ramp 172325151 CID:2800 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Ground Page 172437090 CID:4206 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 172437121 CID:4206 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 172505802 CID:1637 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:the ball 172505833 CID:1637 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Carrier Page 172510035 CID:2216 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:the ball 172510067 CID:2216 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Carrier Page 172519563 CID:4402 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 172519594 CID:4402 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 172522982 CID:1626 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 172523014 CID:1626 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 172537457 CID:1576 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:buff 172537498 CID:1576 -DEBUG-000- || RID:500 || CAT:AI COMMS - Prefix Words 172541797 CID:1767 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 172541828 CID:1767 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 172545536 CID:2303 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:buff 172545568 CID:2303 -DEBUG-000- || RID:500 || CAT:AI COMMS - Prefix Words 172551096 CID:2398 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 172551127 CID:2398 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 172555752 CID:2876 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 172555783 CID:2876 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 172600500 CID:2521 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 172600531 CID:2521 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 172624010 CID:1800 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:raven 7 4 172624042 CID:1800 -DEBUG-000- || RID:500 || CAT:AI COMMS - Prefix Words ***** The commands below were me ***** 202807901 CID:2919 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 202807931 CID:2919 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page
-
Well, I’ve done the debug log. And it now tells me at least which commands it thinks I’m sending.
Annoyingly though, the log doesn’t show when I’ve hit PTT (UHF/VHF) or released, although the main window does.
This is from takeoff. I manually did tower, ready for departure, took off, switched to departure/approach and then did PTT, said “report airborne”. Once, and once only, then I was silent for the rest of the flight. Also, I did not push UHF or VHC comm buttons.
I’m assuming I’ve got something wrong in my config - might erase and start again.
165626478 CID:4313 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:turn off all humans mode 165626511 CID:4313 -DEBUG-000- || RID:500 || CAT:(configuration - BMS) 165638292 CID:4313 -DEBUG-02- || INFO: Executing Sub-Command (F_SFS_DELETE) with RID:4382 - valid Return should == 4616 165638896 CID:2549 -DEBUG-000- || IS:1 || ACT:Spoken || CMD:f_sfs_delete 165638944 CID:2549 -DEBUG-000- || RID:4382 || CAT:Script Functions - Save File System 165638990 CID:2549 -DEBUG-01- || INFO: AVCS_SFS_SAVED_requests = 4 165641870 CID:2549 -DEBUG-02- || INFO: Executing Sub-Command (F_SFS_TO_FILE) with RID:1268 - valid Return should == 1502 165642632 CID:2482 -DEBUG-000- || IS:1 || ACT:Spoken || CMD:f_sfs_to_file 165642679 CID:2482 -DEBUG-000- || RID:1268 || CAT:Script Functions - Save File System 165642725 CID:2482 -DEBUG-01- || INFO: AVCS_SFS_DELETE_saved = True || AVCS_SFS_BACKUP_bypass = False || AVCS_SFS_SORT_bypass = True || AVCS_SFS_RESTORE_backup = False 165648312 CID:2482 -DEBUG-16- || INFO: Executing F_SFS_BACKUP before Saving Changes to file 165648359 CID:2482 -DEBUG-16b- || INFO: Executing Sub-Command (F_SFS_BACKUP) with RID:2937 - valid Return should == 3171 165648924 CID:1582 -DEBUG-000- || IS:1 || ACT:Spoken || CMD:f_sfs_backup 165648972 CID:1582 -DEBUG-000- || RID:2937 || CAT:Script Functions - Save File System 165653071 CID:2482 -DEBUG-17b- || INFO: Sub-Command (F_SFS_BACKUP) COMPLETE -- Return equals 3171 165653712 CID:2482 -DEBUG-15- || INFO: SFS Variable(s) Saved to C:\Program Files (x86)\VoiceAttack\Apps\AVCS\save_files\bms_save\92\save.txt 165655886 CID:2549 -DEBUG-03b- || INFO: Sub-Command (F_SFS_TO_FILE) COMPLETE -- Return equals 1502 165656075 CID:2549 -DEBUG-04- || INFO: F_SFS_DELETE COMPLETE -- ----------------------------------------------- 165658296 CID:4313 -DEBUG-03b- || INFO: Sub-Command (F_SFS_DELETE) COMPLETE -- Return == 4616 165659064 CID:3945 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:the ball 165659094 CID:3945 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Carrier Page 165709861 CID:2200 -DEBUG-000- || IS:1 || ACT:Spoken || CMD:request qfe 165709892 CID:2200 -DEBUG-000- || RID:4616 || CAT:AI COMMS 3 - ATC - Common Page 165712719 CID:1972 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 165712752 CID:1972 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 165715253 CID:1835 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 165715285 CID:1835 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 165717103 CID:4237 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 165717136 CID:4237 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 165738353 CID:2533 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 165738384 CID:2533 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 165741338 CID:4187 -DEBUG-000- || IS:1 || ACT:Spoken || CMD:request qfe 165741368 CID:4187 -DEBUG-000- || RID:4616 || CAT:AI COMMS 3 - ATC - Common Page 165753064 CID:3679 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 165753095 CID:3679 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 165832039 CID:2606 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 165832071 CID:2606 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 165838649 CID:3649 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 165838682 CID:3649 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 165904445 CID:2330 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:the ball 165904477 CID:2330 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Carrier Page 165929759 CID:3874 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:lightning 2 2 165929791 CID:3874 -DEBUG-000- || RID:500 || CAT:AI COMMS - Prefix Words 165954086 CID:3452 -DEBUG-000- || IS:1 || ACT:Spoken || CMD:request qfe 165954118 CID:3452 -DEBUG-000- || RID:4616 || CAT:AI COMMS 3 - ATC - Common Page 170010357 CID:1879 -DEBUG-000- || IS:1 || ACT:Spoken || CMD:tower say again 170010389 CID:1879 -DEBUG-000- || RID:4616 || CAT:AI COMMS 3 - ATC - Tower Page 170033891 CID:3700 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:lion 170033923 CID:3700 -DEBUG-000- || RID:500 || CAT:AI COMMS - Prefix Words 170041159 CID:1692 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:ready for departure 170041190 CID:1692 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Tower Page 170045301 CID:1624 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:ready for departure 170045333 CID:1624 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Tower Page 170104285 CID:4055 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:the ball 170104317 CID:4055 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Carrier Page 170115555 CID:1346 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 170115586 CID:1346 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 170131938 CID:2964 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:report airborne 170131968 CID:2964 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 170147531 CID:1609 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 170147563 CID:1609 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 170150062 CID:2806 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 170150093 CID:2806 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 170153428 CID:1160 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 170153461 CID:1160 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 170201332 CID:2497 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 170201362 CID:2497 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 170212018 CID:3918 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 170212050 CID:3918 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 170225288 CID:2543 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 170225288 CID:2543 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 170225318 CID:2543 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 170249232 CID:2373 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 170249264 CID:2373 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 170252015 CID:3358 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 170252046 CID:3358 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 170634460 CID:2987 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 170634491 CID:2987 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 170753954 CID:1223 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 170753983 CID:1223 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 171054389 CID:2508 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:the ball 171054421 CID:2508 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Carrier Page 171200681 CID:2705 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 171200711 CID:2705 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 171314531 CID:4014 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 171314564 CID:4014 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 171328132 CID:2767 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 171328163 CID:2767 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 171333998 CID:3462 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 171334031 CID:3462 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 171447592 CID:2427 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 171447623 CID:2427 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 171542324 CID:3990 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 171542354 CID:3990 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 171542948 CID:1156 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 171542979 CID:1156 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 171608895 CID:3088 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 171608926 CID:3088 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 171649655 CID:1697 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 171649685 CID:1697 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 171652780 CID:1435 -DEBUG-000- || IS:1 || ACT:Spoken || CMD:request unrestricted approach 171652811 CID:1435 -DEBUG-000- || RID:4616 || CAT:AI COMMS 3 - ATC - Approach Page 171702126 CID:3738 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:request unrestricted approach 171702156 CID:3738 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Approach Page 171709528 CID:3545 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 171709559 CID:3545 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 171724692 CID:3426 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:the ball 171724724 CID:3426 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Carrier Page 171743449 CID:3801 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 171743481 CID:3801 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 171751321 CID:2036 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 171751352 CID:2036 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 171755049 CID:1658 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:request landing 171755080 CID:1658 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Tower Page 171755080 CID:1658 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Tower Page 171800938 CID:1698 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 171800969 CID:1698 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 171825909 CID:3544 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 171825939 CID:3544 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 171857483 CID:1347 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 171857514 CID:1347 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 171947376 CID:2091 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 171947405 CID:2091 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 172011478 CID:1188 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 172011511 CID:1188 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 172049573 CID:4173 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:report on final 172049605 CID:4173 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Tower Page 172248840 CID:1337 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 172248870 CID:1337 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 172302418 CID:2542 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 172302449 CID:2542 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 172312548 CID:2483 -DEBUG-000- || IS:1 || ACT:Spoken || CMD:request taxi for departure 172312581 CID:2483 -DEBUG-000- || RID:4616 || CAT:AI COMMS 3 - ATC - Ground Page 172325118 CID:2800 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:request taxi to ramp 172325151 CID:2800 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Ground Page 172437090 CID:4206 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 172437121 CID:4206 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 172505802 CID:1637 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:the ball 172505833 CID:1637 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Carrier Page 172510035 CID:2216 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:the ball 172510067 CID:2216 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Carrier Page 172519563 CID:4402 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 172519594 CID:4402 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 172522982 CID:1626 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 172523014 CID:1626 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 172537457 CID:1576 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:buff 172537498 CID:1576 -DEBUG-000- || RID:500 || CAT:AI COMMS - Prefix Words 172541797 CID:1767 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 172541828 CID:1767 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 172545536 CID:2303 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:buff 172545568 CID:2303 -DEBUG-000- || RID:500 || CAT:AI COMMS - Prefix Words 172551096 CID:2398 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 172551127 CID:2398 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 172555752 CID:2876 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 172555783 CID:2876 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 172600500 CID:2521 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 172600531 CID:2521 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page 172624010 CID:1800 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:raven 7 4 172624042 CID:1800 -DEBUG-000- || RID:500 || CAT:AI COMMS - Prefix Words ***** The commands below were me ***** 202807901 CID:2919 -DEBUG-000- || IS:0 || ACT:Spoken || CMD:airborne 202807931 CID:2919 -DEBUG-000- || RID:500 || CAT:AI COMMS 3 - ATC - Departure Page
Okay I’ll admit that is pretty odd behavior there. I don’t even know where to start with the radio calls errantly recognizing commands especially since you have PTT mode on. You can certainly delete the configs and then restart VoiceAttack, and AVCS will re-download and initialize the configs. I am not sure how they could get screwed up, and still not certain that this is the issue, but it won’t hurt anything.
Say, “Open Advanced Core Options” … then select the very bottom option from the pop-up choice list: “CONFIG: Select Profile Config Folder(s) to Delete (restored if needed)”
Another option (though again, calls should not be recognized when PTT mode is on, and that’s kinda the point) is to increase the minimum confidence level as described in the VA Manual, under VoiceAttack Options > Recognition
Re. " the log doesn’t show when I’ve hit PTT (UHF/VHF) or released"
This is due to the nature of Debug Mode Level 1 – I designed it as a “fast and minimum” logging feature, essentially a command logger. If you’d like to see action reports of all that is happening when commands are recognized (including PTT state) you need to use Debug Mode Level 2 or higher. (Lv2 is full debug to file only, Lv3 is full debug to file AND event log readout, Lv4 is full debug to event log readout only). *NOTE: Level 2 and higher are slow, they slow down command execution speed and so you need to give extra time before assuming something is not working (which is why Level 3 exists, so you can see what is happening live in the event log).
To clear the log for new tests, just say, “Clear the Error Log”. Feel free to run some tests in Debug Mode Level 2, and toss the file up here for review if you want. I don’t know what else to suggest at this time, so go from here and report back. I’m happy to help users troubleshoot, especially because this helps me refine these profiles which are technically in a public beta phases. This feedback is invaluable. Best wishes and good luck! I hope we can get to the bottom of this!
Cheers!
-
I must be being particularly stupid.
1.I removed all the configs as above, then all profiles. I then removed VA.
2. Reboot (prob unnecessary, but hey, this is Windows).
3. Reinstall VA.
4. Import the AVCS Core Profile, let it do its thing.
5. Import the AVCS BMS Profile, let it do its thing. AVCS pops up asking what profile to load automatically, I choose BMS (I think that’s right?).
6. I click edit for the profile, set up the PTT joystick buttons.
7. I say “Turn on Push to talk mode”. “Are you sure?” … pause. pause. get annoyed because I say yes and it recognises it and then says command cancelled. Repeat a few times, eventually get the timing right. PTT is now on. Awesome.
8. Push my PTT buttons, check that all behaves as expected. Awesome.
9. Load BMS, fly a mission perfectly. No errors, no weirdness.
10. Quit BMS, Quit VA.
11. Open VA (as administrator). watch it repeatedly load and unload BMS profile, then go back to core. For about 3 seconds, when BMS Profile is loaded, the PTT buttons are recognised, then it goes back round again.
Apologies for my stupidity, but I am very confused!
-
I must be being particularly stupid.
1.I removed all the configs as above, then all profiles. I then removed VA.
2. Reboot (prob unnecessary, but hey, this is Windows).
3. Reinstall VA.
4. Import the AVCS Core Profile, let it do its thing.
5. Import the AVCS BMS Profile, let it do its thing. AVCS pops up asking what profile to load automatically, I choose BMS (I think that’s right?).
6. I click edit for the profile, set up the PTT joystick buttons.
7. I say “Turn on Push to talk mode”. “Are you sure?” … pause. pause. get annoyed because I say yes and it recognises it and then says command cancelled. Repeat a few times, eventually get the timing right. PTT is now on. Awesome.
8. Push my PTT buttons, check that all behaves as expected. Awesome.
9. Load BMS, fly a mission perfectly. No errors, no weirdness.
10. Quit BMS, Quit VA.
11. Open VA (as administrator). watch it repeatedly load and unload BMS profile, then go back to core. For about 3 seconds, when BMS Profile is loaded, the PTT buttons are recognised, then it goes back round again.
Apologies for my stupidity, but I am very confused!
Regarding Step 7: These are the actions when it asks us to say yes (or no), and I believe I should remove the “(and wait until it completes)” from the speech, since you are not the first person to report this, and I also run into this same issue. When I changed the VAS Simple Confirmation system over to this (it existed before “Wait for spoken response” existed as a VA action), I never changed the speech flow, and so I think when we respond too quickly, it’s still in the ‘Say’ action, and not yet proceeded to the ‘Wait for spoken response’ action. It’s going on the list, there are so many simple confirmation prompts throughout AVCS CORE and AVCS4 BMS that I wouldn’t expect anyone to do this manually (but you can if you are impatient for my next release).
The alternative workaround is to wait a few beats after it asks ‘are you sure’ before responding in the affirmative.
Begin Boolean Compare : [AVCS_RadioButtons_ON] Equals False Say, '{TXT:AVCS_TTS_VAS_AreYouSure}' (and wait until it completes) Wait for spoken response: '{TXT:AVCS_VAS_CONFIRM}' Begin Text Compare : [AVCS_VAS_CONFIRMED] Contains [~avcs_temp_response]
Regarding Step 10: How is it that you are opening VA as Administrator? Are you right clicking on the EXE/shortcut and selecting ‘Run as Administrator’, or are you changing the VoiceAttack Options > Advanced Tab where you can select this as the launch option for the program? It matters, but I cannot recall the details at present. Pfeil explained it awhile ago, and it’s faded from memory.
Before Step 10, how were you launching VA? Did the options menu have ‘Run VA as Administrator’ checked or not? AFAIK, the only best method is to use the VA Option for this, and not to set the .exe properties as ‘Run as Administrator’ or to launch by right-clicking the .exe/shortcut and selecting ‘Run as Administrator’.
-
Regarding Step 7: These are the actions when it asks us to say yes (or no), and I believe I should remove the “(and wait until it completes)” from the speech, since you are not the first person to report this, and I also run into this same issue. When I changed the VAS Simple Confirmation system over to this (it existed before “Wait for spoken response” existed as a VA action), I never changed the speech flow, and so I think when we respond too quickly, it’s still in the ‘Say’ action, and not yet proceeded to the ‘Wait for spoken response’ action. It’s going on the list, there are so many simple confirmation prompts throughout AVCS CORE and AVCS4 BMS that I wouldn’t expect anyone to do this manually (but you can if you are impatient for my next release).
The alternative workaround is to wait a few beats after it asks ‘are you sure’ before responding in the affirmative.
Begin Boolean Compare : [AVCS_RadioButtons_ON] Equals False Say, '{TXT:AVCS_TTS_VAS_AreYouSure}' (and wait until it completes) Wait for spoken response: '{TXT:AVCS_VAS_CONFIRM}' Begin Text Compare : [AVCS_VAS_CONFIRMED] Contains [~avcs_temp_response]
Regarding Step 10: How is it that you are opening VA as Administrator? Are you right clicking on the EXE/shortcut and selecting ‘Run as Administrator’, or are you changing the VoiceAttack Options > Advanced Tab where you can select this as the launch option for the program? It matters, but I cannot recall the details at present. Pfeil explained it awhile ago, and it’s faded from memory.
Before Step 10, how were you launching VA? Did the options menu have ‘Run VA as Administrator’ checked or not? AFAIK, the only best method is to use the VA Option for this, and not to set the .exe properties as ‘Run as Administrator’ or to launch by right-clicking the .exe/shortcut and selecting ‘Run as Administrator’.
Thanks for all your help. I’m using the VA option to launch as Admin.
Sent from my iPhone using Tapatalk
-
After another complete clean up and reinstall, I seem to have got it to a state where it loads correctly, no looping.
And, more importantly, no strange inputs!
I wish I knew what was different but sadly I don’t.
Sent from my iPhone using Tapatalk
-
Are you still with us Semler?
-
If you need support on this, your best channel is probably on the VG discord - there’s a voice attack Avcs channel.
What’s up?
Sent from my iPhone using Tapatalk
-
Are you still with us Semler?
I’m still here, I’ve just been very busy. All of March and into a few weeks of April, I was designing a ‘wiki page’ system for the VG website. It was assumed to be a 2-3 week project, ended up turning into 6 weeks of hell. But VG now has a wiki for all sorts of server info, players guides, and of course for my own AVCS profiles as well. The systems are done, the pages are not. All of 2021 so far has been devoted to overhauling the VG website, restructuring membership and group advancement systems, and developing new website systems for our members.
I intend to dive back into my AVCS projects asap - just wrapping up some unfinished work and tasks that got put off in the first quarter of this year. I hope to have some progress to announce within the next few weeks.
If you need help, like rubbra wrote, find the AVCS support channel in the VG Discord: https://veterans-gaming.com/discord/
-
Thanks Semler and rubbra. Had a look on Discord, but my issues are trivial and not so technical I imagine. A few of my commands don’t work( “out the box”), but the rest are great! This App is much appreciated.
-
Thanks Semler and rubbra. Had a look on Discord, but my issues are trivial and not so technical I imagine. A few of my commands don’t work( “out the box”), but the rest are great! This App is much appreciated.
It’s worth spending time making sure your audio is nice and clear without any echo. This made a huge difference in recognisability for me, as well as doing the speech training.
I also find that, if I use phrases before the actual command (wildcards), then it helps to leave a very slight gap before the command. Eg. Goblet4… ready for departure.
Sent from my iPhone using Tapatalk