Search results for query: *

That's a major rewrite... not so much in terms of actually doing the scaling (that will be a single line of code), but more like how to put that into the UI in a user-friendly way. In saying that, I just modded a CUA and wished I could move something around, so maybe at some point...

Nope, the 8 Channels should all be independent of each other. There is no information exchanged between them in code.

Only through AnimationPatterns, but not directly, e.g., by changing X/Y/Z.

HAL9001 updated BeatIt with a new update entry: v1.3 (var 5): Turn me on, Turn me off Read the rest of this update entry...

Oh, true, good idea... I'll see. Just finished the Band Enabled flags and will upload new var. I also realised that I never exposed the frequency/bandwidth parameters.

Weird indeed. Might be a Unity bug - not necessarily VaM. No pressure ;-) Good suggestions, and the disable button is very easy to do. I was also wondering about trigger events flying all over a scene and have some of my plugins to only fire when the delta of the current vs. a previously fired...

HAL9001 updated LogicBricks2 with a new update entry: v10: Bugfixes and relative/absolute PerlinNoiseMovement Read the rest of this update entry...

Good idea... Will have a look into it.

HAL9001 updated LogicBricks2 with a new update entry: v9: (BREAKING CHANGE) ValueMap Mapping Curve added / Overall naming unifications Read the rest of this update entry...

Agree, that's part of a ValueMap extension I had in mind anyway: A curve applied to the unified value: Exponent, Sinusoidal, Log/Pow because I need that just now for a scene of mine where the heartbeat is supposed to grow louder just shortly before the orgasm... perfect application of an...

MacGrubers set has "ValueRandom" to get a random number between 0 and 1 on a trigger. You could then use ValueMap to convert to any other range between 0 and 1. Outside of 0/1 is always tricky as the VaM event system doesn't really like that.

HAL9001 updated LogicBricks2 with a new update entry: v7: (BREAKING CHANGE) Renamed BinaryOperator / Added Float/BoolSelector Read the rest of this update entry...

That sounds more like a subscene thing in VaM to me. beyond my control.

Hmmm, that idea of stating another atom as base, not the parent is something I did in another (soon to come) Plugin, so I can copy that code across at some point. The xMin/xMax can easily be addressed by offsetting your actual center to (xMin+xMax)/2. Unless you want dynamic control on each of...

HAL9001 updated LogicBricks2 with a new update entry: v7: (BREAKING CHANGE) FloatOperation Multiplication and UI_TransformSync plugin added Read the rest of this update entry...

Multiply: Can do, easy, just might backfire if somebody has used range extension on the inputs and the result is outside of [0...1] Multiplexer: I was thinking about that already. At the moment, there's some kind of that in the BooleanOperator for 2 channels - I'll also add that to the...

That's exactly the way to do it :) (and that's actually why I wrote that plugin in the first place). Would you be OK if I link to this tutorial in the plugin page description as an example?

Got the main code working. Need to sleep now. Might push a new var tomorrow.

I'll give it a thought. Either extending UI_Sync (which feels wrong), or making a variant of it.

In principle yes, but that would need a custom script. Thinking about implementation details, I can imagine, that's a bit more on the tricky side to make it generic and configurable: Getting an atom's transform (pos/rot) is easy, turning numbers into text, also easy. Sending that text to UI...