I've assigned the trim wheel axis in MSFS to one of my CH Products throttle levers to see how it works.  When flying manually it works great. A lot better than using discrete buttons.  But it doesn't play well with the planes' autopilots.  The autopilots adjusts the trim and this seems to flight with the position (and input) from the assigned lever position.   This causes the graphical trim wheel in the cockpit to go beserk and problems when disengaging the autopilot (the trim wants to go back to the lever position).    Does the Bravo Throttle Trim wheel have the same problems?

The trim wheel on the HC Bravo is using buttons, so no problem there.

Okay, thanks.  But does this mean that I will have the same delay that I have with using actual buttons?.  The problem is with many of the planes to make small changes in trim I can't just tap the button.  I have to hold it down for a second or two before the trim reacts.  In most cases, this means unless my timing is perfect I will over shoot where I want the trim to be so I have to try to correct and then it gets into a back and forth situation.  Using the trim axis is so much smoother.  So if the Bravo doesn't provide the smoothness of using the trim axis then I'll probably pass on it.   Thanks

Edited January 28, 20224 yr by CajunRon

3 hours ago, CajunRon said:

Okay, thanks.  But does this mean that I will have the same delay that I have with using actual buttons?.  The problem is with many of the planes to make small changes in trim I can't just tap the button.  I have to hold it down for a second or two before the trim reacts.  In most cases, this means unless my timing is perfect I will over shoot where I want the trim to be so I have to try to correct and then it gets into a back and forth situation.  Using the trim axis is so much smoother.  So if the Bravo doesn't provide the smoothness of using the trim axis then I'll probably pass on it.   Thanks

No (but...)

You won't be using the button repeat functionality with an encoder wheel, so the delay is not a factor. You are sending instead a string of very short button presses. On the other hand, this means your trimming will be very slow because each trim movement is tiny. The sim initially had acceleration in the trim controls, which means if you called them quickly enough in succession the trim would speed up. I'm not sure if that's still there (there were issues with acceleration). The solution I use for my trim wheel (also an encoder) is to send five seperate trim commands for every pulse (button press) from the trim wheel. Unfortunately you won't be able to do this from MSFS, you will need a third-party tool such as SPAD.neXt or FSUIPC*.

(*There is also this utility, which is getting good reports, although I have not tried it.)

Edited January 28, 20224 yr by MarkDH