Set and Get Global Values with triggers

DusX

~~you can treat triggers as boolean. (Which they are).~~

~~1 = trigger~~

~~0 = at rest (no trigger)~~

~~I think a comparator will test a trigger against a value (not at my machine right now)~~

mark

you can treat triggers as boolean. (Which they are).

Well, that's not exactly true. A trigger always sends a '1'... it is the act of transmission that signals the trigger. A trigger will never send a 0. So a comparator won't actually work.

That said, my tests show you can send triggers through the get/set global values actor. This setup works fine:

Best Wishes,
Mark

DusX

Oops. I stand corrected. ☺

dritter

Thank you Mark, the problem I have is that an original pair of Set and Get actors will work, but if these actors are copied and their Set and Get names changed, such as triggertest being changed to triggertest2, the GetGlobal Values actor will not receive. Please see attached.

thank you

Don

getvalues-test.izz

dritter

Mark, I just created a patch that sends triggers using Set and Get Values, but if I save and close the patch, it will not send triggers when it is reopened. This is only happening with triggers, but everything is fine with text and numbers.

all the best,
Don

Skulpture

Try and enter scene trigger actor.

mark

@dritter said:

Mark, I just created a patch that sends triggers using Set and Get Values, but if I save and close the patch, it will not send triggers when it is reopened

Recreated and fixed for the v2.6 release, which is very soon.

Best,
M

mark

@dritter

Keep this important point in mind: while you can use the Set/Get Global Values actors like a Broadcaster/Listener pair, it's not a super good idea to do so. Every time you change even one value (and that includes the new trigger value), every item in the Set Global Values actor is sent to the any Get Global Values actor in the same scene. If you have a really long list of values, that might become computationally expensive.

Best Wishes,
Mark

DusX

@mark

Out of curiosity (for my own work) is sending a longish text string rather than numerous values likely to be less costly?

The text would be the values as json, so the length is related to the number of values.

mark

@dusx said:

Out of curiosity (for my own work) is sending a longish text string rather than numerous values likely to be less costly?

No, it really wouldn't matter. And for most uses it's fine. It's just hooking up something like an Envelope Generator to a Set Global Values with 100 inputs wouldn't be a good idea.

Best,
M

dritter

great, thank you Mark.

all the best,
Don