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:
Back
Top Bottom