VA seems to "lose" the ability to read CMDSEGMENT:1

[Zaal]

But only on certain dynamic sections.

Prefix/Suffix group is "fire missions", command prefix is "fire mission", command suffix is [precision strike; gas strike].

I try to read the CMDSEGMENTs using a 'say' command. CMDSEGMENT:0 is spoken as "fire mission", CMDSEGMENT:1 (which should be precision strike or gas strike) is unset followed by a call to CMD that does read out the full command "fire mission precision strike" for example.

Now comes the freaky part: if I change the suffix to [test;testing], the CMDSEGEMENT:1 correctly picks up the test or testing and speaks it out to me correctly.

I can't think of why this is happening and would appreciate any guidance the community can provide. Thanks!

[Gary]

Hi, Zaal

Can you provide exactly what is in your 'When I say' box for that command?

[Gary]

I guess where I'm going is I'm wanting to make sure you don't have one command that is a prefix and a second, separate  command that is a suffix, as CMDSEGMENT does not work (or at least not tested) in that scenario.  You would need to have one command with the spoken phrase ('When I say') of 'fire mission[precision strike;gas strike]'  (no quotes).

[Zaal]

Gary, you just fixed the problem with your second post. I feel like I should have known this but......

I had some 'beta' functions in a category that I thought would keep them out of the way. I'm POSITIVE at this point that those were actually picking up the commands when I didn't want them to. Thought I had the muted but it wasn't until I read your post and completely deleted the offending commands did everything turn back to normal.

Thank you very much for your attention. Sorry for bothering you.

[Gary]

No problem at all bud - keep rockin'