Thank you for your report! Please find it posted here: AVCS Bug Reporting Forums
Thank you for your report! Please find it posted here: AVCS Bug Reporting Forums Profile Version: 1.3.8 VoiceAttack Version: 1.8.5 Report Bug Report
=VG= SemlerPDX 6,195 Posted May 27, 2020 at 10:52 PM Report reply Share this comment *I know this area of the forums is currently hidden for most members, but if anyone sees this, the above is the very first ACTUAL report made using my voice controlled bug reporting and debugging -- previous reports have be format testing and such, but that's done now and figured I'd debug a current issue with this new system. I need to move the LastCommand and Previous Command up before the choices in voice debugging, but other than that, it's complete. I simply said, 'create a bug report', and my system asked me to run the commands I had problems with, told me to say, 'Save Report', when done... then it opened this website, to a new bug report form, asked me select the text area with the cursor, then say, 'ready' or 'done' to paste the report.The entire post above was created by my system, I didn't do anything except say, 'done', and press "Save" to post the report, which also posts to these forums. Of particular note, the automated debugging system noticed that the save file system may not be functioning correctly, and added a note to the Observed Behavior section of the report. I almost forgot about that, and was delighted to see it! Sometimes I have ideas to implement, far more than ever make it in, and I had thought perhaps this one was not crossed off the list yet. It even handles any Sub-Command failure and will toss up information if any had not executed properly or had thrown any errors during execution. Sometimes I impress even myself! I will now use the above report to find out why my new command "Set my Wingman as Human" doesn't save to file correctly. It works in profile, but once I close VoiceAttack and reload, it's like I never set Wingman to Human. (not yet implemented, this would be a new general command concept irrespective of callsign, sets the words "2" and "Wingman" to be recognized as Human, and therefore NOT press any in-game ai Radio Commands for Wingman if/when these words are recognized by my voice control system) This report is particularly long because it includes debugging of the profile restart and initialization, where I believe the problem lies. After CORE initializes itself, and then it's dependent 'modules' (like voice authorization system), and then if preferred profile is set, it will switch to and initialize that end-game profile ... in this case, AVCS4 BMS - Immersive Voice Control Radios (and it's dependent 'modules', if any) - but it must load the AVCS4 BMS save file before switching to the profile, or rather before arriving at it, or else any customized settings will not be available including commands that the user created by voice control using the Quick Command Creator module (as opposed to traditional command creating/editing).This new debugging and bug reporting system adds quite a bit of content to any command that needs it, unfortunately sometimes even commands that had only one single line, one single action... but it does not at all effect the speed of standard execution (when not debugging or creating a bug report), and that's all that matters. The information gained, and the ease of use for the user (and for me, the developer), far outweighs any negatives from the added bloat to the commands in my many AVCS profiles. Link to comment Share on other sites More sharing options...
=VG= SemlerPDX 6,195 Posted June 10, 2020 at 03:26 AM Report reply Share this comment Changed Severity / Status to Resolved (for upcoming download version) fixed - issue in F_SFS_TO_FILE, in the AVCS_SaveToFile inline function. The way I had used .Contains has issues comparing when the item to change is at the beginning or end of a string, needs to account for those cases if needed. if not(entry(1).Contains(requestVarValue)) changed to: if ((not(entry(1).StartsWith(requestVarValue))) or (not(entry(1).Contains(requestVarValue))) or (not(entry(1).EndsWith(requestVarValue)))) Link to comment Share on other sites More sharing options...
Recommended Comments