C#•2y ago

clamping how fast a input (as a float) can change.

Let’s say my Input X float changes in a amount of time from -1 to 1 (-1, -0.5, 0, 0.5, 1) so as an example the speed is 12 (Which I calculate by subtracting the current input from last input and dividing that by Time which will result in the Speed of change).

Now the float changes quicker, so from -1 to 1 (-1, 0, 1) so now the speed is 24, right?

But I want a way that if it the input speed from InputX exceeds the example speed of 12, that the InputX speed still changes at the speed of 12.

I tried for days but I have no idea what to do anymore.

canton7•3/6/24, 9:24 PM

Seems easy, unless I'm missing something?

canton7•3/6/24, 9:24 PM

Given the previous value of X and the time, calculate what the new value if X would be if it was travelling at speed 12. If the actual new value of X is larger than this, limit it to that value you calculated

Jimmacle•3/6/24, 9:25 PM

i'm confused what the variables are, why does it sound like is both the input and the output?

canton7•3/6/24, 9:26 PM

(I think it is. In my reading, it's an input to the system, and a rate limit is being applied to that system input)

Jimmacle•3/6/24, 9:27 PM

a less abstract explanation of the problem trying to be solved might help (it would help me at least)

Fabian F.OP•3/6/24, 9:50 PM

Sorry for the late response, my internet fumbled a bit.

JJimmacle a less abstract explanation of the problem trying to be solved might help (it wo...

Fabian F.OP•3/6/24, 9:54 PM

What I am trying to do is that if my Input which can change between -1 and 1 for X and Y on a gamepad, exceeds a set speed, it should still change at that set speed independent of how fast I change the input.
I need this to make the player move in a circular motion, if the input variables X and Y are able to change too quickly, the player is able to spin like a helicopter, this is more so a polish feature than a gameplay feature, it would look nice with the animation system.
I hope I am not being too abstract again!

Fabian F.OP•3/6/24, 9:55 PM

It's basically like my slowly turning the analog stick to move in a circle

canton7•3/6/24, 10:22 PM

I think my first comment answers your question still?

Jimmacle•3/6/24, 10:24 PM

yeah, you'd keep extra state for your "current" value and when the input changes, compare it and limit to a maximum change if needed

Ccanton7 I think my first comment answers your question still?

Fabian F.OP•3/6/24, 10:24 PM

Oh chucks, I accidentally skipped that message and jumped immedietly to jiMMACLE's message.
Though I am quite unsure of how I would do said calculation, that is more so my issue than anything else to be honest.

Jimmacle•3/6/24, 10:26 PM

rough pseudocode

Jimmacle•3/6/24, 10:26 PM

the actual threshold you'd compare to depends on the amount of time between changes

Fabian F.OP•3/6/24, 10:27 PM

Alright, I'll try that out and I'll get back to you!

Jimmacle•3/6/24, 10:28 PM

you're basically just clamping the change between a minimum and maximum value

Jimmacle•3/6/24, 10:29 PM

would be another way to calculate it

Fabian F.OP•3/6/24, 10:36 PM

I might be confused by how was newValue caluclated in the first place?

Jimmacle•3/6/24, 10:36 PM

it's not calculated, that's your input

Fabian F.OP•3/6/24, 10:36 PM

and currentValue might then be?

Jimmacle•3/6/24, 10:37 PM

the output going to your other code

Fabian F.OP•3/6/24, 10:37 PM

Alright!

Jimmacle•3/6/24, 10:38 PM

it accumulates the changes applied by limiting the new input value

Jimmacle•3/6/24, 10:38 PM

then for example, if your current value starts at 0 and you fed it a constant input of 144 it would take 12 iterations for the current value to match the raw input

Jimmacle•3/6/24, 10:39 PM

which sounds like the smoothing you're looking for

Fabian F.OP•3/6/24, 10:41 PM

Oh boy, this really is tough to understand but I suppose that I am starting to get it.

Fabian F.OP•3/6/24, 10:42 PM

I'll see what I can do and I will hop back in here if I have any more questions, for now thank you both!

canton7•3/6/24, 10:45 PM

I mean, you said you're calculating the speed from the change in value and the time.

canton7•3/6/24, 10:46 PM

Calculating what the change in value would be if the speed is 12, given the same change in time, is just the same equation, rearranged slightly

canton7•3/6/24, 10:48 PM

So if you have x1 (previous input), x2 (new input) and t (time), then speed = (x2 - x1) / t. Rearrange for x2 and you get x2 = (speed * t) + x1

canton7•3/6/24, 10:49 PM

So if x2 is larger than (12 * t) + x1, then the speed is faster than 12

canton7•3/6/24, 10:49 PM

Make sense?

canton7•3/6/24, 10:52 PM

(fix to handle x2 being less than x1 of course)