 |
Also there is an AFIdle callback in BMS-Blank and BMS-Full key files, that appears to not work. Not sure about AFABOn and AFABFull. They seem to sometimes work, sometimes not.. eg. maybe only when throttle axis is mapped to keyboard or mousewheel? |
|
|
Edit: AFIdle does sometimes work, just not reliably .. similarly to AFABOn/Full |
|
|
I've been experimenting with different approaches, eg. mapping my 4th/5th mousebuttons to keypresses to manipulate AFThrottleDown/Up. I can send these keypresses programmatically (using Win32 SendInput API) to sometimes achieve smaller inputs. But it's not controllable or deterministic .. if the keypresses are shorter than 1 frametime, they sometimes get missed. And the shortest reliable keypress duration (~20ms) is enough to move the throttle +/- 1,000 lbs/hr. That's better than I can do by hand, but still too coarse to be useful. Taking a look at the import table of FalconBMS.exe I see it is calling GetAsyncKeyState, as I suspected -- which means short keypress durations of ~5ms get missed a great deal of the time. I think this has been happening to me, with other keys.. I'll make a note to press keys firmly for at least a full frame. lol But in meantime .. whatever multiplier you're applying to the keypress duration, to move the throttle, needs to be greatly reduced. |
- Anonymous
