3.7 version "action settings" is not working

WARNING: You currently have Javascript disabled!
This website will not function correctly without Javascript enabled.

chronoco

3 discussion posts

I unchecked the "Ignore commands during Text to Speech" but still my commands are ignored during TTS. Also changing default voice is not working too.
It is fine in 3.6 version.

Aug 16, 2020 (modified Aug 18, 2020) • #1

The default voice setting seems to be working for me when I test it here. Where is the TTS being used? If it's in a Macro, is the TTS action itself set to use the default voice?

Regarding the "Ignore commands during Text to Speech" setting, are you trying to issue new commands while a TTS read-out is still playing? Or are you wanting the TTS read-out to trigger the macros?

Aug 19, 2020 • #2

chronoco

3 discussion posts

More details here

My first script "Emergency"

Code
Copy
Select All

using System;
using System.Drawing;

public static class VoiceBotScript
{
    public static void Run(IntPtr windowHandle)
    {
        // Initial State
        
        if(BFS.ScriptSettings.ReadValueBool("Protocol")==false)
        {
            BFS.ScriptSettings.WriteValueBool("Cancel",false);
            BFS.ScriptSettings.WriteValueBool("Protocol",true);
            BFS.ScriptSettings.WriteValueInt("State Order",1);
            BFS.ScriptSettings.WriteValueBool("Emergency Mode",true);
            //--------------------------------------------------------------
            
            while (true)
            {
                if(BFS.ScriptSettings.ReadValueInt("State Order")==1)
                {
                    BFS.Speech.TextToSpeech( "Danger" );                  
                    BFS.VoiceBotActions.Delay(500);

                    if ((BFS.ScriptSettings.ReadValueBool("Cancel")==true) )
                    {
                        BFS.ScriptSettings.WriteValueBool("Cancel",false);
                        BFS.ScriptSettings.WriteValueInt("State Order",0);
                        BFS.ScriptSettings.WriteValueBool("Emergency Mode",false);
                        BFS.ScriptSettings.WriteValueBool("Protocol",false);
                        break;  
                    }
                }
                else if(BFS.ScriptSettings.ReadValueInt("State Order")==0) 
                    {
                        BFS.ScriptSettings.WriteValueBool("Cancel",false);
                        BFS.ScriptSettings.WriteValueInt("State Order",0);
                        BFS.ScriptSettings.WriteValueBool("Emergency Mode",false);
                        BFS.ScriptSettings.WriteValueBool("Protocol",false);
                        break;    
                    } 
                //break;
            }
        }
        else
        {
            BFS.Speech.TextToSpeech( "Another protocol activating" );
        }
    }
}

And my second script "Cancel protocol"

Code
Copy
Select All

using System;
using System.Drawing;

public static class VoiceBotScript
{
    public static void Run(IntPtr windowHandle)
    {
        // your code goes here
        BFS.ScriptSettings.WriteValueBool("Cancel",true);
    }
}

3.6 version

1. Command "Emergency"
2. TTS says "Danger Danger Danger ...."
3. Command "Cancel" (anytime)
4. "Emergency" command Stops

(So yes, I'm trying to issue new commands while a TTS read-out is still playing)

3.7 version

1. Command "Emergency"
2. TTS says "Danger Danger Danger ...."
3. Command "Cancel"
4. My "Cancel" Command ignored

if I delete "BFS.Speech.TextToSpeech( "Danger" );" my "Cancel" command works properly.
That is why I thought "Ignore commands during Text to Speech" setting is not working.
Also the default voice changing is not applied to "BFS.Speech.TextToSpeech"

FYI
I use steam version Software and updated to 3.7 from 3.6
I installed voicebot on D drive not C drive(OS)
I tried both "BFS.General.ThreadWait" and "BFS.VoiceBotActions.Delay" after " BFS.Speech.TextToSpeech"

Aug 20, 2020 (modified Aug 20, 2020) • #3

Thanks! I was able to reproduce both of those issues here and have added them to our list to fix up for the next version

Aug 22, 2020 • #4

We've just released a new VoiceBot version and both of these issues should be all fixed up. Please let us know if you run into any trouble after updating.

Thanks!

Aug 28, 2020 (modified Aug 28, 2020) • #5