wheelchock2 Posted August 24, 2020 at 02:05 AM Report Share Posted August 24, 2020 at 02:05 AM request vector to tanker for BMS profile actually changes my view rather than selecting the comms window commands for vector to tanker. Profile: AVCS4 BMS - Immersive Voice Control RadiosIssue: Command(s) pressing wrong keys in gameProfile Version: 1.3.91VoiceAttack Version: 1.8.6 Steps to reproduce: vector to tanker || AI COMMS 2 - AWACS - Vector Page vector to tanker || AI COMMS 2 - AWACS - Vector Page Expected Behavior: default functional operation Observed Behavior: (see attached error log file, if available) Personal Testing: (AVCS Automated Debug and Reporting used) Comments:AVCS CORE Version: 0.91.1 F_CORE_MAIN Version: 0.91.1Session Command Count:96 RAM(total):17108287488 RAM(available):12607397888LastCMD:request vector to tanker PreviousCMD:request factor to tankerPlayback:Speakers (Realtek High Definition Audio) Playback(comms):Speakers (Realtek High Definition Audio)Playback Volume:30 Playback Mute:0Microphone:Microphone (Realtek High Definition Audio) Microphone(comms):Microphone (Realtek High Definition Audio)Microphone Volume:100 Microphone Mute:0Speech Device Volume:100 Speech Device Mute:0JOYSTICK1:1 JOYSTICK2:0 JOYSTICK3:0 JOYSTICK4:0GAMEPAD1:0 GAMEPAD2:0 GAMEPAD3:0 GAMEPAD4:0AVCS CORE Profile: AVCS CORE (v0.91b) AVCS Profiles List: AVCS_PROFILE_AVCSCORE90=AVCS CORE (0.90b) AVCS_PROFILE_AVCSCORE91=AVCS CORE (v0.91b) AVCS_PROFILE_AVCSBMS91=AVCS4 Falcon BMS Radios (v1.3.91b) 220027652 CID:0 -DEBUG-##- || INFO: ==========================NEW REPORT========================== 220041163 CID:2518 -DEBUG-000- || IS:1 || ACT:Spoken || CMD:vector to tanker 220041194 CID:2518 -DEBUG-000- || RID:1872 || CAT:AI COMMS 2 - AWACS - Vector Page 220046091 CID:3134 -DEBUG-000- || IS:1 || ACT:Spoken || CMD:vector to tanker 220046091 CID:3134 -DEBUG-000- || IS:1 || ACT:Spoken || CMD:vector to tanker 220046122 CID:3134 -DEBUG-000- || RID:1872 || CAT:AI COMMS 2 - AWACS - Vector Page 220050726 CID:3134 -DEBUG-04- || INFO: LOOP page = 2 - Keyboard Key has been pressed == Q 220051153 CID:3134 -DEBUG-04- || INFO: LOOP page = 1 - Keyboard Key has been pressed == Q 220051484 CID:3134 -DEBUG-05- || INFO: Command complete - ~avcs_prefix_target = AWACS || Current TimeKeyIsHeldDown = 0.05 || Current TimeBetweenKeys = 0.05 220051531 CID:3134 -DEBUG-05b- || INFO: Final Keyboard Key has been pressed == 4 220235144 CID:0 -DEBUG-##- || INFO: ==========================NEW REPORT========================== 220248421 CID:3009 -DEBUG-000- || IS:1 || ACT:Spoken || CMD:vector to tanker 220248452 CID:3009 -DEBUG-000- || RID:2106 || CAT:AI COMMS 2 - AWACS - Vector Page 220253284 CID:1870 -DEBUG-000- || IS:1 || ACT:Spoken || CMD:vector to tanker 220253284 CID:1870 -DEBUG-000- || IS:1 || ACT:Spoken || CMD:vector to tanker 220253315 CID:1870 -DEBUG-000- || RID:2106 || CAT:AI COMMS 2 - AWACS - Vector Page 220257909 CID:1870 -DEBUG-04- || INFO: LOOP page = 2 - Keyboard Key has been pressed == Q 220258328 CID:1870 -DEBUG-04- || INFO: LOOP page = 1 - Keyboard Key has been pressed == Q 220258670 CID:1870 -DEBUG-05- || INFO: Command complete - ~avcs_prefix_target = AWACS || Current TimeKeyIsHeldDown = 0.05 || Current TimeBetweenKeys = 0.05 220258717 CID:1870 -DEBUG-05b- || INFO: Final Keyboard Key has been pressed == 4 Severity / Status: Non-issue View full bug report Link to comment Share on other sites More sharing options...
=VG= SemlerPDX Posted August 24, 2020 at 08:09 AM Report Share Posted August 24, 2020 at 08:09 AM This is a head scratcher for sure... Just tried the command myself and it pressed the Q key twice and then the 4 key. It would be more understandable if all keys didn't go through, but the fact that you said it changed your view means the 4 key DID get through to BMS, but not the two Q keys. For troubleshooting, please try other commands that would use the same menu (AWACS / Q key menus) and see if any others on page 2 (or others) are having the same issue. Past that, I would suggest adjusting the time keys are held down and the time between keys through the menu. (say, "Change Keypress Timings" to open the menu while BMS profile is active and initialized) The default is 0.05 iirc and it may be too fast for your game to catch -- I'd suggest bringing that up to 0.07 or 0.08 for testing, for both settings. I'll message you in Discord with this info, too. I think it's just happening too fast. If it's not that, it might be the way VoiceAttack is targeting the application to send keys. The profile is distributed with "Active Window" set as default, but you could also try targeting the Falcon BMS.exe directly through the profile options menu in VoiceAttack, near the top left of the editor near the profile name). Let me know if any of that works, and if not we'll see what else we can come up with to try. Link to comment Share on other sites More sharing options...
=VG= SemlerPDX Posted August 24, 2020 at 08:09 AM Report Share Posted August 24, 2020 at 08:09 AM Changed Severity / Status to Moderate Changed Issue to Command(s) not pressing any keys in game Changed Profile Version to 1.3.91 Changed VoiceAttack Version to 1.8.6 Link to comment Share on other sites More sharing options...
=VG= SemlerPDX Posted August 25, 2020 at 02:03 AM Report Share Posted August 25, 2020 at 02:03 AM Changed Severity / Status to Non-issue Link to comment Share on other sites More sharing options...
=VG= SemlerPDX Posted August 25, 2020 at 02:08 AM Report Share Posted August 25, 2020 at 02:08 AM (from discord) Quote wheelchock wrote ... 'had to copy the COMMS section from the default Full key file to my profile. Something was hosed up but its ok now" So the issue was in his bms keyfile after all. Status changed to non-issue. *It was noted that there is excessively long initialization time, possibly on older CPU's? ...NOTE: These first rounds of BETA Tests are for functionality alone. I have always planned to optimize the speed and efficiency of the initialization procedure, and know several places where it can and will be improved. After 8 months, I needed to get this into the public space so that bugs and other issues could be addressed while I continue work on optimization, performance, and polish. Thanks to everyone for helping out with testing and being patient with these early iterations. Cheers! Link to comment Share on other sites More sharing options...
Recommended Posts