CurryKitten
commented
4 years ago I've designed an algorithm that broadly simulates the time it takes to spin the props up form your current throttle position to the desired on. This is scaled dependant on the position of the throttle - so when props are spinning faster it takes less time for them to accelerate further.
Its all a bit finger in the air and estimate it. But having tested it out, especially against the previous version it feels about right. It's still not easy to hold a steady low altitude hover on the very highest throttle multiplier setting, but it's not a lot more possible than it was.
I've noticed (as have others) that the throttle is very sensitive on anything other than the 3s simulation. While it's fine for hooning around and freestyling - it can be quite difficult to hold a steady hover or keep altitude. It makes coming in for a landing or flying through the bando quite difficult.
So either we have to enforce some kind of throttle expo - which seems unnecessary as we don't have to do that IRL. Or we think about what might be different - the only thing I can think of is the time it takes for the props to accelerate or decelerate to their desired RPM. Right now the response is instant - so this might be the source of the over-sensitivity on the throttle. I'll investigate.