• Hi Guest!

    Please be aware that we have released a critical security patch for VaM. We strongly recommend updating to version 1.22.0.7 using the VaM_Updater found in your installation folder.

    Details about the security patch can be found here.
LogicBricks2

Plugins LogicBricks2

HAL9001 updated LogicBricks2 with a new update entry:

v9: (BREAKING CHANGE) ValueMap Mapping Curve added / Overall naming unifications

THIS UPDATE COULD BREAK SCENES THAT HAVE USED PerlinNoiseValue, ValueMapRelay, ValueDelay, HysteresisThreshold.

Ok, now we should finally be done with those breaking changes. I am sorry, and I have to take my own medicine and edit several scenes by search/replace, too, so I hear your pain...
  1. Again, for consistency purposes I changed "Value" to "Input" or "Output" in the above mentioned plugins, so that all bricks now have a consistent naming...

Read the rest of this update entry...
 
I've been using it for a while, and it feels very, very good, but I have a new little problem, when using PerlinNoiseMovent, set the three parameters of Delta pos x/y/z, the atom moves in the corresponding direction of the world's XYZ, not in the direction of the parent atom, nor in the direction of the subscene containing it, when the parent atom or the whole subscene is not in a fixed direction, it is difficult to predict whether the movement direction of the atom meets your needs, Can it be changed to the direction of the parent atom, because he is serving the mother atom after all.
 
I've been using it for a while, and it feels very, very good, but I have a new little problem, when using PerlinNoiseMovent, set the three parameters of Delta pos x/y/z, the atom moves in the corresponding direction of the world's XYZ, not in the direction of the parent atom, nor in the direction of the subscene containing it, when the parent atom or the whole subscene is not in a fixed direction, it is difficult to predict whether the movement direction of the atom meets your needs, Can it be changed to the direction of the parent atom, because he is serving the mother atom after all.
Good idea... Will have a look into it.
 
HAL9001 updated LogicBricks2 with a new update entry:

v10: Bugfixes and relative/absolute PerlinNoiseMovement

  • Some bugfixes around plugins that would not honour the "disabled" flag (e.g., ValueDelay)
  • Bugfix in Threshold plugin when starting with values on the "wrong end" of the threshold
  • Some code cosmetics to variable names
  • As requested by @3348302775, added relative movement option to PerlinNoiseMovement (default setting is absolute so not to break any existing scenes... for a change ;-) )

Read the rest of this update entry...
 
Be careful with this plugin. I was messing around with the value map function and I guess I made some sort of infinity loop which caused VaM to crash and lose a bunch of work.
 
Last edited:
Be careful with this plugin. I was messing around with the value map function and I guess I made some sort of infinity loop which caused VaM to crash and lose a bunch of work.
Oops, sorry 'bout that, but I guess that could happen with any plugin that would send information back to itself ;-)
 
bool operator doesnt work man. at least, partially.

the AND operator doesnt work unless all 8 inputs are true, regardless of how many you pick on the slider. the output will not activate unless all 8 are true. is that how it's intended???

edit: I also thought you'd be able to pick which inputs. so like, input 1 AND 3 and true > some output trigger
output 1 AND 5 are true > a different output trigger

but that's not the case, there's only 1 output.

same thing with the other bool selector. I thought you'd be able to assign a different output depending on the input bool, but that's not true. there's only 1 output result.

This doesn't make it like a switch statement like you say in your description at all. a switch statement is like

first thing is true? -> do this, else
second thing is true? > do something different, else
third thing is true? > do yet some other thing, else.
etc...

but your bool selector doesn't have different results, it's just a single trigger result with 8 different input bools that can trigger it....
 
Last edited:
bool operator doesnt work man. at least, partially.

the AND operator doesnt work unless all 8 inputs are true, regardless of how many you pick on the slider. the output will not activate unless all 8 are true. is that how it's intended???

edit: I also thought you'd be able to pick which inputs. so like, input 1 AND 3 and true > some output trigger
output 1 AND 5 are true > a different output trigger

but that's not the case, there's only 1 output.
It woks exactly as intended. I't s an 8-input AND/XOR/OR. Yes, if you only use 2 inputs, the other 6 have to be set to TRUE for an AND, respectively to FALSE for an OR. That's how the boolean operator is defined. If you need several outputs, you need to add use one plugin for every output.
 
Last edited:
I love bidir sequence machine, but if I had one request I wish it had the ability to retrigger the current state.

Maybe it does and I just haven't found it? 🤞

I was doing a quick PrevState, NextState pair that accomplished what I needed but sometimes events don't like to be stacked like that. I saw this when switching backgrounds and depending on the load times, sometimes the PrevState triggers may win vs the desired NextState (i.e. the original current state).

The workaround I came up with is to insert dummy states between the real ones and then do the PrevState, NextState pair. It works but it means I then have to have special "NextState" and "PrevState" triggers that jump 2 states (to get past the dummy). Not ideal.
 
I have another idea for you. an OnMinMax plugin.
I have an oscillating variable with no fixed min or max, but I would like to call a trigger when it hits a minimum/maximum value.
 
I have another idea for you. an OnMinMax plugin.
I have an oscillating variable with no fixed min or max, but I would like to call a trigger when it hits a minimum/maximum value.
Er, won't the HystheresisThreshold be able to do that...?
 
Er, won't the HystheresisThreshold be able to do that...?
I did try.
I used a ValueDelay with Decrease of 0, and Increase of 4. It gives a 'good enough' Min value.
I use that to set the threshold of a HysteresisThreshold with 0 hysteresis, scaling between 0.1 and 1 (so it is always just above the last minimum).
This works okay when the minimum is roughly the same or lower than the last minimum.

But the min/max values of my oscilating variable can fluctuate wildly. On one cycle it can be 0.1 - 0.9, next cycle is 0.5 - 0.9.
Meaning the above attempt won't catch this minimum.

(EDIT)
The input is coming from BeatIIt plugin, so I have no way of knowing the value ahead of time.
I am wanting translate an input [0..1] to output [0..½..1] at half frequency where 0 on the input is ½ on the output, alternating below/above the ½ point on each min/max of the input. (i.e an up-down syncing with a side-side motion)
 
Last edited:
The input is coming from BeatIIt plugin, so I have no way of knowing the value ahead of time.
I am wanting translate an input [0..1] to output [0..½..1] at half frequency where 0 on the input is ½ on the output, alternating below/above the ½ point on each min/max of the input. (i.e an up-down syncing with a side-side motion)
Hmmm, that is on the more complicated end of the spectrum indeed. A custom plugin would probably be easier, but I don't have the time for that. Sorry.
 
any chance in adding an add and divide function to floatoperator?
While this sounds intuitive, it's not as straightforward as the value range of inputs needs to be between 0 and 1, and adding or dividing by <1 would exceed that.
Also, Average is effectively (Input1+Input2)/2, so you have a sum there.
 
Last edited:
Back
Top Bottom