Understanding Sequence of Behaviours: In Search of Speed!
-
@iTap-Development And... just in case you or anyone else is wondering, this is about speed.
Which provides access fastest and sets fastest?
I had (it seems wrongly) assumed that "Value Behaviours" were kind of like constants, which offer a lot of performance advantages in other languages/environments, not just for the compiler, but also for the OS and the hardware.
It seems they're nothing like that kind of idea... and more like a function parameter without a function.
-
@Deeeds said in Understanding Sequence of Behaviours: In Search of Speed!:
In other words, like many of my posts, I'm trying to use subterfuge to help the founders stop floundering in their complete failure to document, guide and instruct on the matters of their own engine/tool.
Really?
-
@Deeeds okay, how would you set the multiply input with the 10, 20, and 30? Maybe I could give you an example.
-
@GameCRAZY Yes. Really.
Have a re-read of the ones that seem obviously odd. They'll make more sense from this perspective.
-
@iTap-Development Yes, try for an example where the differences between a Value Behaviour and a Box Container are essential to their use. In other words, a situation where they're not interchangeable.
-
@Deeeds not perfect but maybe it will help.
-
@iTap-Development Can you describe what's going on here? And why it's being done?
And ....
why it's in need of Value Behaviours in their use cases?
Why they can't be Box Containers?
Why the Box Container can't be a Value Behaviour in this scenario?
-
@Deeeds ugh. How would you use JUST value behaviors?
-
Yes, try for an example where the differences between a Value Behaviour and a Box Container are essential to their use. In other words, a situation where they're not interchangeable.
-
@iTap-Development Here's @Jack8680 quite good description, starting with Value Behaviour:
It's not a pointer, so if you reference the value elsewhere it will have the value of the input when the value behaviour is activated.
It is different to a box container because a box container is a pointer when you drag a behaviour output in, so referencing a box container will reference the value of what is selected in the box container.
You can't use set input field on a box container that has a behaviour output selected as its value, so there's no reason to use them this way as you can just reference the behaviour output directly.
Using set input field on a box container that isn't a reference to another behaviour output acts the same as using a value behaviour, but it can be set from multiple places.
-
@Deeeds I know what they are.
You were wondering how they were useful, I tried to give an example......I guess I failed. Oh well, I like them! -
@iTap-Development In the screenshot you've shown, I don't see a need for ANY of the Value Behaviours.
I could be missing something, but it seems like you could connect the if statements to the activities required (get rotational velocity, get position and whatever started touching is doing..., etc)
Further, how is the "multiply values" activated?
I don't really understand how that's a demonstration of anything.
-
@iTap-Development said in Understanding Sequence of Behaviours: In Search of Speed!:
@Deeeds I know what they are.
You were wondering how they were useful, I tried to give an example......I guess I failed. Oh well, I like them!I was talking about box containers.
Yeah sorry, not a complete example. I thought it would be enough.
But the point was that box containers make it easy to have unrelated outputs put into the multiply input. -
@iTap-Development said in Understanding Sequence of Behaviours: In Search of Speed!:
I was talking about box containers.
Yeah sorry, not a complete example. I thought it would be enough.
But the point was that box containers make it easy to have unrelated outputs put into the multiply input.Perhaps I'm very dense.
I don't see how your example demonstrates that.
