[ANSWERED] input-output user actor triggers at entering scene

[Gaspar]

Hi.

Using the "well known" user actor of just one input and one output I've noticed that it sends out a trigger whenever I enter the scene.
I guess this is probably not meant to be this way.

[Gaspar]

additional info. It also triggers having just an "user output" inside the "user actor". So its the "user output" who triggers everytime you enter a scene.

[DusX]

@gaspar said:

t also triggers having just an "user output" inside the "user actor"

 What data type do you have the output set to?

[Woland]

@gaspar

It'll definitely trigger if you set the User Output actor inside the User Actor to initialize as blank or at a certain value (depending on data type), but in that case it's just pushing the data that you told it to initialize with.

[dbini]

@gaspar
are any of the inputs initialised? Either inside the User Actor, or on the outside?

[Gaspar]

@dbini @DusX @Woland 

Thanks for coming back to me...

The I/O user actor was basically meant to send triggers, but not necessarily when entering the scene.

The input and outputs were not initialised, although I tried to initialise them to zero after seeing this weird behaviour.

From your answers I assume it does not happen on your system.

I even created a blank patch from scratch with a first blank scene and a second scene with only the I/O user actor and a trigger value to check if it is triggered when entering the scene... and YES IT IS.

And this happens also on my second installation of ISADORA on the same computer but DUAL BOOT for just gigs... no internet, no antivirus, etc.

[dbini]

@gaspar

with this setup, i get the same results as you, even with nothing initialised, the trigger is sent when entering the scene

[DusX]

@gaspar

OK, I have found the cause here. You are passing a value thru the user actor. It assumes there is some processing internally so the value is processed. 

If you instead turn the input and outputs to trigger types the trigger is not passed.

[Woland]

@gaspar

Another staple User Actor, especially for cases like this, is what I call a "Delay Gate"; a User Actor with a Gate that initializes off, then turns on shortly after. I use these all over the place to 'eat' unwanted triggers that generate upon entering a Scene because sometimes they're unavoidable (and sometimes it's just faster for me to throw one of these inline to eat a trigger that I don't want because it's faster than spending the time to examine everything upstream to determine where the trigger is coming from). For example, I use Delay Gates with Comparator actors and Text Comparator actors when I have their 'compare' mode set to 'Always' because you'll always get a true or false trigger out of those actors when you enter a Scene in that mode.

delay-gate-user-actors.zip

These are not entirely relevant, but here's a couple other groups of simple User Actor 'tools' that I find myself using quite often:

thru-user-actors.zip 

mutator-user-actors.zip

deadman-x27-s-user-actors.zip