• Hi Guest!

    We are extremely excited to announce the release of our first Beta for VaM2, the next generation of Virt-A-Mate which is currently in development.
    To participate in the Beta, a subscription to the Entertainer or Creator Tier is required. Once subscribed, download instructions can be found here.

    Click here for information and guides regarding the VaM2 beta. Join our Discord server for more announcements and community discussion about VaM2.
LogicBricks2

Plugins + Scripts LogicBricks2

Download [0.18 MB]
HAL9001 updated LogicBricks2 with a new update entry:

v13: Features added + UI/Code overhaul

Features added:
  1. New LogicBrick ParameterMonitor. Monitor a parameter value for change and act accordingly. You can see it in action e.g., when changing the operator for FloatOperation, and the amount of inputs changes.
  2. BoolOperator has a new parameter to set the amount of inputs
  3. FloatOperator has a new parameeter to set the max. amount of inputs
  4. FloatOperarator has new operations (sin/cos/log/pow/division)
  5. PerlinNoise and PerlinNoiseMovement have a Seed Parameter, and...

Read the rest of this update entry...
 
I wanted to use ValueMapRelay for setting up DepthOfField values of post effects because it's own one not really helpful.
I used VUML to get distance from focus point object to camera and put this value in DepthOfField plugin. FocusDistance no need to remap.
I tried to use ValueMapRelay to calculate Aperture and FocalLength values depending of distance to focus point.

BUT! ValueMapRelay Input value is clamped in [0...1]. InputFrom and InputTo messing up output values but not helping with Input range. Extrapolate checkbox does not work for this.
In other case, i should use OutputActions to setup Aperture and this trigger too has input value [0...1] and (Start) Aperture, (End) Aperture remapping values.
It makes setup very complex and hard to understand.

I just wanted to put distance, linear interpolate it from range1 to range2. Maybe removing clamping for input value would be enough, but can't say for sure.
The FloatOperator just got new operation added and the [0...1] limits removed.
 
Thanks for the reply Hal,

I ended up finding a solution for the thing I was trying to do. I didn't consider feeding one perlin value into another generator, I'll keep that in mind.

Hope all is well otherwise, I totally get the life/modding interference issue. Regardless, thanks for the contributions you've already made.

Thanks!
I had some time to push out the changes I'd been working on very slowly for months. Among them a Seed parameter for PerlinNoise/Movement.
 
Back
Top Bottom