Baron Elevator Trim
-
Hats off to Black Square!. They have utterly transformed the 'vanilla' Asobo BE58 and it is now a delight to use. And here comes the 'however'....
However.... elevator trim still seems to be the implemented using the clunky mechanism to be found in default Asobo aircraft. Using a rocker switch on my yoke, a continual press will result in:
- an immediate and very small increment, followed by,
- approximately a 0.5 second pause, followed by,
- a continual and accelerated application of trim adjustment.
In practice, this means that a small trim adjustment (a single click of the rocker switch) is not enough but continual pressure results in too great a change. This makes hand flying in IMC unnecessarily difficult and frustrating.
I have raised a ticket on this observation and I hope someone at Black Square can resolve the matter.
If I compare how elevator trim is handled in the JustFlight Arrow, you can see that the trim immediately moves, and continues to move, at a constant rate of change. This makes trimming the Arrow a delight. I would love to see this method implemented in the Black Square Baron.
-
Apologies if this is too basic. The processing of external controls occurs outside the airplane code.
Can you specify how you are interfacing your yoke to the sim?
Are you using the in-sim control mappings because in-sim can be wonky.
For better result, there are 3rd-party control mapping programs. I use AAO and the trim button does not have this behavior. You can specify the repeat rate in the button assignment dialog.
A lot of people prefer spad.next instead of AAO.If you are wondering if a control bad behavior is from the interface try to compare with using the mouse.
I have no idea why you have better result with another airplane - perhaps some difference in the control mapping?
-
Apologies if this is too basic. The processing of external controls occurs outside the airplane code.
Can you specify how you are interfacing your yoke to the sim?
Are you using the in-sim control mappings because in-sim can be wonky.
For better result, there are 3rd-party control mapping programs. I use AAO and the trim button does not have this behavior. You can specify the repeat rate in the button assignment dialog.
A lot of people prefer spad.next instead of AAO.If you are wondering if a control bad behavior is from the interface try to compare with using the mouse.
I have no idea why you have better result with another airplane - perhaps some difference in the control mapping?
@jbbz Many thanks for your reply. I was unaware of AAO and, having purchased it, I now enjoy a finer, and linear, response from elevator trim inputs.
I think I was incorrect to state that the Arrow did not suffer from the standard Asobo trim response. I do now think that there is the standard Asobo delay between the initial one-click response and a continual input. However, the animation of the trim wheel movement looks continuous - with no pauses - and that masks the actual behaviour of the trim mechanism.
I've made minimal use of AAO so far, but have transferred 'control' over to AAO for elevator and aileron trims together with rudder axis and it works well.
Thanks for pointing me in this direction.
Regards