Wiggle returning values modified by an amount greater than amplitude setting

[pkroll]

Hi there... either I'm crazy or wiggle is misbehaving by a small margin.

I have a slider control set to an initial value of 50:

On that slider is an expression:

wiggle(1.5,50)

When I preview this in graph editor, the value is dipping below 0 occasionally! I've got a frame reading -0.15 and if I mouse over the graph it actually dips as low -0.45.

Shouldn't an amplitude of 50 on top of a starting value of 50 result in a number than ranges from 0 to 100? The value is also never rising to 100, but I'm willing to chalk that up to not running this out over a long enough duration to see all possible values.

[Dan Ebberts · Accepted solution]

As I recall, wiggle() has always been able to go slightly beyond the specified amplitude (I think I measured it once, but I don't remember how far it can go). You just need to factor in that possibility.

Dan

[pkroll]

Ok cool. That's not bad or anything. I was mostly just curious as to whether I had somehow broken it. Good to know it can do that.

[jeffbottom]

I have just discovered this same issue, kind of defeats the whole purpose of even having a amplitude argument if you have to use additional code to clamp the results !!!

It's a bit more than slightly as well, see the image below, I'd guess as much as 20% at the extremes...

[Phi.Def]

Bah! What a pain in the a*%!

Thanks for the answer. I was so confused.