There are reasons, related to autopilot, to use a digital trim wheel (acts as repeated button presses for nose up and nose down) instead of an analog trim wheel (assigned to an axis). On the other hand, a digital trim wheel can seem very unresponsive in the game if the rate of button presses it generates is not high enough to move the in-game wheel at a reasonable rate. This was apparently made more of a problem, perhaps specifically for Honeycomb Bravo users, in WU4 but has theoretically been addressed somehow in today’s SU4.
The problem is that if the wheel produces button presses at too rapid of a rate, they will be ignored or missed by the sim and it will be hard to make “single click” adjustments to the trim setting. But if the maximum pulse rate produced by the digital trim wheel is too low, you will see slow movement of the wheel in the game no matter how fast you move your physical wheel.
I have found a way around this (mostly) for my DA 2890 digital trim wheel, using freeware vJoy and Joystick Gremlin, allowing fine adjustments when you want and more rapid movement when you need, but how well it works (or whether or not it is needed) depends on how many button presses your digital trim wheel produces per second when you are moving the wheel as rapidly as you can.
You can see how many button presses you get in 10 seconds using the super simple website ShmupSpeed. Here is a video of my doing it with my DA 2890. It only produces about 6 pulses per second maximum (62 in 10 seconds), which means I definitely need to use some apps to speed it up a bit. Then again, this may be just my particular 2890. I’m very curious to see numbers from other users of DIGITAL trim wheels (this test will not measure anything nor does it matter for analog trim wheels). Please run the test if you have a DA 2890 or a Honeycomb Bravo or any other digital trim wheel and report your results.
Per request, I tried the website but neither my Logitech multi-panel nor the Bravo produce a result. I tried to reset, reboot, restart the controllers etc.
I verified they are both producing results via the Controls section in the sim and the Spad.Next interface.
Thank you for trying. I temporarily had mine stop working, but a browser restart fixed it. Dang. I really want to see other’s numbers.
Did you try another browser? Mine was done in Edge. Does your controller show up on this webpage? I’m guessing not, and that’s Why shmup speed won’t work… https://gamepad-tester.com/
The Game Pad Tester does detect the Bravo and responds with the trim wheel. The Tester does not detect the Multi-Panel.
I tried the Shump link on Edge and not response either.
I was forced into the 1.16.2.0 update and decided to run a quick pattern with the TBM and the trim was responding. It did however take several wheel turns to trim down on final.
They made a huge change in turbine performance. Spool time is Lonnnngggg.
I’m not sure what decides if shmup speed works or not. Too bad we couldn’t get data from your bravo and multi panel.
I did the update yesterday and my trim wheel was still slow in the game. I will make a YouTube video of the work-around I came up with using vjoy and joystick gremlin, for those who don’t own fsuipc or spad.next.
It doesn’t look like we’re going to be able to measure the button speed of the Bravo or Logitech digital trim wheels (perhaps because they use button numbers greater than 32 for this).
So, we’ll just have to hope that this solution works for them, as it did for my trim wheel. I hope it works for you!