Issue with {CMD} when using VA 'start listening/stop listening'

[Zaal]

Greetings, all;

I've run into an interesting issue I think may be a bug.

From the documentation, the {CMD} token should return the name of the currently executing command.

I have a very simple command (in code tags below) that when run with the voice command 'no timing' will return the expected 'no timing' in the log but if I run it again, it returns '[no;] timing'. After bringing this up in the discord, it was suggested that this isn't expected behavior.

Attached also is a copy of the log from VA with me activating the command six times: initial three are 'timing' and the second three are 'no timing'. As you can see, the VA software is getting strange results and we figured it might have something to do with how I'm starting and stopping listening.

I'm using version 1.15 of the software.

Let me know if there's anything else I can provide to assist .

Code: [Select]

When I say: [no;] timing

Start VoiceAttack listening
Write [Red] 'Command is {CMD}' to log
Begin Text Compare : [{CMDSEGMENT:0}] Equals 'no'
    Say, 'Two segments'
    Stop VoiceAttack listening
Else
    Say, 'One Segment'  (and wait until it completes)
End Condition


[Gary]

I was able to reproduce this issue and the fix will be in the next release.

Thank you for the heads up!