@Tuuvas believe it or not, BMS did improve this in 4.37 when they added the special new callbacks for game-controllers (the 4-way shift states)
make sure you’re using AFThrottleUp/Down … not AFCoarseThrottleUp/Down
but even the non-coarse callbacks are still too coarse / sensitive… I agree
only real workaround is to do some Gremlin/vJoy scripting to make a fake throttle axis
Edit: the sensitivity of these callbacks is frame-rate dependent … but maybe not in the way one would expect. higher fps => more sensitive
at 60 fps, it takes about 20 clicks to go from idle to max-burner … at 30 fps, it takes about 40 clicks 🤷
Edit2: it’s not really supported, but it’s possible to assign mousewheel to throttle… last I tried this, it was about 80 clicks of resolution between idle and max-burner … that was still not precise enough for AAR but almost … with a deft touch on the speedbrake you could make it happen.
Edit3: just tested again… mousewheel still works, but it’s only about 25 clicks of resolution… less janky, and not sensitive to framerate, like the keybd/button callbacks. but not sensitive enough for AAR