I also ever wondered about the Factor of the Float Curve node… the docu says:
Factor
Controls the amount of influence the node exerts on the output value.
…so i also assumed it would be the mathematical expression * factor to be able to “scale” the value for example by half ( * 0.5 ) or double it ( * 2.0 )…
( And also wonder why to put this into the node because a Math node with multiply would do this… and also i used exactly this for “scaling” the float curve output… or a Map Range node )
So i had a look at the range… to use some “proper integer values” for the input i choosed the start to end frame 0 and 10 to have 5 in the middle. So now if you also use a the same values for min and max in the Map Range node so that it doesn’t change anything (which could be checked when muting it) you get (with decimal values of 2):
→ the frame number “plus” .00
But (yes) when using the “factor” everthing runs haywire…
Also:
When using an RGB curve then the factor seems to have no influence at all…
(I did this with 3.6 because the computer i watch BA now can’t handle 4.xy )
if Factor = 0: the float curve is ignored completely;
if Factor = 1: the float curve output is used;
if Factor = 0.5, the output value is in the middle between the original input and the full output of the curve.
The Float Curve works in [0, 1] range.
So if you have 10 as input, the result of Float Curve will be 1.
If the Factor is 0.5, the result will be between 10 and 1, which is 5.5
Like others said, the issue is that the float curve operates on 0…1 range. If you want to draw a curve that affects the range 0…10, you need to remap to 0…1 first, and remap to 0…10 after the float curve.
If it is supposed to work only for 0 to 1, why are the soft limits of that field not 0 and 1 but you can enter anything you want, if it doesn’t make sense?
I think/hope the developers had thought about that and gave them soft limits because they make sense…although i don’t understand it.
Just had a look. And no there is more or less standing nothing in the manual about it at all. But the fcurve field itself is clamped with all its values into a 2 dimensional 0…1 area and also the extrapolation doesnt work outside that range. But if for whatever reason someone just wants to add its curves out to whatever input then it might turn out to be benefitial that is unclamped. But honestly I dont see much sense lying in there. So yeah. Could be clamped or the float curve could be expanded to relate to a to be specified value range.
Maybe you just think of the extrapolation in the top drop down box?
That’s probably because you already remapped your values with Map Range to [0, 1], so your Float Curve have no meaningful influence regardless of the factor.
