Unfortunately, this is still an issue.

That's not what this ticket is referring to.

As far as I can tell it was a failed attempt to allow for slight variations in collective settings during cruise flight in AFM.

All it does is not allow you to manipulate the collective fast enough for landing and hovering.

But what do I know? I only fly these things in real life...

Thank you for replying oukej, I appreciate you confirming what we all knew. It seems rather silly to cater to a specific type of controller while simultaneously screwing everyone up (No onecan have a control setup for SFM and AFM on the same profile now) but you know your demographic better than us.

I do wish you would make the AFM collective speed uniform across the board for the non-analog input though

That is a very bizarre change... This work around fixes the symptoms but this should still be addressed by the devs. Thanks for this find Jay

I will add that I've tested an xbox one controller and saitek prox52

See my related (duplicate) issue for another explanation of the issue and suggested fixes