by Steve Waite » Mon Jan 18, 2021 9:25 am
...Jogging an axis before flying is something I've done since first using these simulators with controllers.
For example, I have a throttle quadrant and yoke. If I have not already positioned the levers before starting the simulator, the first touch of the yoke causes the engines to suddenly assume the current throttle quadrant positions which disturbs the aircraft.
So to put it another way - if we have any joysticks or other controllers connected to FSX/P3D, the way the simulator works is to send all the current axis positions when we first press a button or move an axis after running the simulator up. This is how the simulator works with controllers.
Since Ideal Flight will be using the movement of the throttle as a signal to disengage the auto-throttle, if we have not yet touched a controller, that first touch will send the current throttle position through the system and Ideal Flight will see it as an input and will naturally disengage auto-throttle.
Let's say I start the simulator and get on with Ideal Flight doing its auto-throttle. At some point I jog a controller axis or press a button for the first time, this sends the current throttle axis through the system and Ideal Flight responds by disengaging auto-throttle.
What would be handy would be some way of knowing that this is merely the first time a controller has been used. If I make Ideal Flight ignore the first throttle movement and not respond then how would it know if this was indeed a legitimate movement of the throttle axis meant to disengage the auto-throttle.
software architect at codelegend.com
equipment: i9-9980Xe 64GB 2xRTX2080ti NVLink 2TB M.2 NVMe,
i9-9900X 64GB RTX2080ti 2TB M.2 NVMe, i7-3960X 32GB GTX680 4TB RAID10,
NAS @7TB RAID10 (16TB)