Plugins + Scripts FloatParamRandomizerEE

boaboa said:

it would be the best but...same problem as the other users here
my problem is when i change the look, or reload the scene i've got to put all the parameters again...i try to save it as sub scene but he don't keep the configuration, i 've got to do something wrong, any tuto?

Click to expand...

Are you using the latest version which includes subscene related fixes?

everlaster said:

Are you using the latest version which includes subscene related fixes?

Click to expand...

yes, of course EE.5

boaboa said:

yes, of course EE.5

Click to expand...

Ok, sounds like a bug then. I'll look into it

ok ,thanks but maybe is me missing something, if you post some "step by step" text for save it as subscene ... we should be sure this way, it's sad because the plugin is amazing !

Having an issue where I have floatparamrandomizer in a subscene and on scene load the Atom that is not part of the subscene is not correctly identified. The data remains but the Atom is wrong, it's seen as being part of the same subscene the floatparam plugin is in. Latest version of the plugin and the atom in question is a person atom, in case that makes a difference in any way.

For myself I can just move it out of the subscene, but it's definitely a recurring bug as every scene load is like that. Every time the scene is saved the Atom receiver gets a new addition of the subscene's name, hopefully that helps track down what code line is doing that.

Thanks

everlaster updated FloatParamRandomizerEE with a new update entry:

v1.0.5

• fix issue with the plugin not changing the value of target float param after loading a scene
• fixed issue where the plugin didn't initialize correctly on a disabled atom
• fix issue where selecting a target parameter would unnecessarily animate a transition from the previous parameter's value to the new parameter's value (or from 0 to parameter's value when selecting the first parameter after initializing)
• receiver popup options are refreshed on opening the popup to prevent...

Click to expand...

Read the rest of this update entry...

everlaster updated FloatParamRandomizerEE with a new update entry:

v1.0.6

Fixed subscene compatibility. Somehow the previous fixes did not work... I must've tested them back then. Anyway, should work now

Click to expand...

Read the rest of this update entry...

Can I use FloatParamRandomizerEE to randomize facial expressions?
I was able to randomize a particular morph (after adding it to favorite)

But what if I want multiple moprhs? If I add multiple FloatParamRandomizerEE one for every morph then all of them are randomized in parallel together

I want one moprh, then another one, etc.

henshin said:

Can I use FloatParamRandomizerEE to randomize facial expressions?
I was able to randomize a particular morph (after adding it to favorite)

But what if I want multiple moprhs? If I add multiple FloatParamRandomizerEE one for every morph then all of them are randomized in parallel together

I want one moprh, then another one, etc.

Click to expand...

If you want to randomize from one morph to the next and blend between them, you could try Expression Randomizer or Silver Expression Tool.

With FloatParamRandomizerEE, randomizing a sequence is not possible since it can only randomize the value of a float parameter. LogicBricks could do it though, e.g. StateMachine or RandomChoice. I'm not sure how to then smoothly blend between the expressions though.

@ParticlePinnacle thanks for the great plugin! I find it makes very good movments that translate really well to an SR6. I like the different stages of the thrust and the way they interact with each other to make sensual movements, but I'm not quite sure how they work. I get surprising results sometimes when I reduce a parameter like Drawback and the stroke gets quicker. Can you explain how the "jelly" function changes the relative timing of the forces? I have spent a lot of time slowly changing jelly and observed that at some point around 0.70 the Drawback changes to affecting the downstroke instead of the up stroke, and further at 1.9 the stroke distance seems to become shorter without changing the Force Amount from it's default of 250, at least in Head mode. Is there a point in the jelly cycle where things come full circle and the forces are timed the same as they are at 0.10? What are the units of the jelly cycle? Is it seconds, degrees, percentage?