.99 strain goes to .00 in deadzone

[crackhex]

Rather self explanatory, but when doing a .99 strain when the joystick wants to be within the radius (x, -1) to (x, -7) I believe, the joystick will land in a dead-zone, which sets it equal to (x,0) internally in the game, leading to a .00 instead of a .99.

[FramePerfection]

I've experienced this, too (although a perfect 32.00 strain would be cool to have, but in reality it goes to 31.<xx> where <xx> is low ¯\(ツ)/¯ ).
The question is what we should expect in this situation, because achieving a .99 value may just not be possible in those situations.
There are, surprisingly, multiple options to consider for this problem:

• We could accept that a .99 value is not viable and disallow any inputs in the range (-7; 7) for both x- and y-axis
• The script could attempt a lower magnitude in the deadzone to achieve the .99 anyways
• The script could attempt to change the camera on the frame in question to achieve a .99 value. Iirc this is possible most of the time, but it would conflate the logic for what's the best joystick for this camera angle to achieve movement x with the reverse, namely what's the best camera angle for this joystick angle to achieve movement x

[crackhex]

I think the best option would be to let it choose the best angle that can be chosen being near .99, while not overshooting and overflowing back to 0.

[ap00001111]

This can also happen outside of deadzones.