There’s also a new topic with an AutoHotkey script for the Bravo Trim wheel that might be a little simpler than the vJoy/Gremlin workaround … but it may not work as well, either. YMMV.
For me, the Honeycomb trim wheel is just unusable at this time for the classic C172 and DR 400.
For the C172 classic, I still have the click sound whenever I rotate the wheel.
I’ve not tested with other planes…
Hopefully, there’ll be a fix in SU7!
Yeah I find it’s perfect in the JF Aarows and the C152 mod but some plane if you just move it a little bit it moves the trim too much making it impossible to trim the plane for level flight
I have been using the Desktop Aviator Trim Wheels in MFSF. They are both different though. Their 2705 (the larger one) is an analog trim wheel (axis up and axis down), while the 2890 (smaller one) is a digital trim wheel (no axis). Each of these wheels function very differently from each other in the sim. The axis wheel will go through the entire trim range with one full rotation of the wheel (the wheel is not continuously rotatable… it can only rotate 360 degrees). The digital wheel is continuously rotatable in each direction, but is read as a series of inputs. Before SU5, it was incredibly slow. It would take 70 full rotations to go from takeoff trim to full trim up (or down). This is obviously completely unusable. SU5 fixed this issue, and it was great. With SU6, it is now back to how it was before SU5, and is completely unusable again. I believe that the honeycomb is digital as well, and has the exact same issues as the digital Desktop Aviator wheel.
These inputs work differently in different planes though. After SU5, my digital wheel worked great in the 172, while the analog wheel would go full trim up (or down) with the tiniest turn of the wheel. The Just Flight Warrior II though would work just fine with the analog wheel, but take forever with the digital wheel (as it is now after SU6). I haven’t flown the Warrior yet after SU6, but I’ll see if there are any differences when I get the chance.
the long term solution is to have different sensitivity settings per device or even better , per device and per each aircraft .
It looks like moving the trim wheel now coincides with the trim on the yoke. I hear the clicking too on my Honeycomb Bravo. When I move the trim wheel, I can see the animation on the yoke trim buttons moving.
Ah, this would be why I’m not as concerned about it. I primarily fly the JF Arrow Turbo.
1 Like
I flew the ovation this evening and couldn’t trim level flight!
I remember the c152 mod was the same a while back; I mentioned it to he developer and with in 12 hours he fixed it so it’s obviously something a planes developer needs to address
Gotta say that once you’ve flowen the JF Arrows the other GA planes feel lifeless; hard to go back to anything else!
The JF Warrior II is my main plane now. All of Microsofts planes feel like cheap toys in comparison.
1 Like
the fsuipc solution mentoned here works for me :
basically every button press of the trim wheel gets multiplied 5x , it does require payed FSUIPC though
Hello,
I have moved your topic to the Peripherals category. This is where anything regarding Honeycomb products should be discussed.
My Honeycomb Bravo trim wheel seems to work with small GA prop planes like the Cirrus, Cessna etc. But anything larger than that and it almost has no effect on trim when rotated.
Is this a Honeycomb issue or a MSFS issue?
For me it works the same as before SU6, at least in the Blackbox Islander
It certainly isn’t a HoneyComb issue, as it always sends the same number of “button pressed” events per rotated distance. There are no native drivers for it, so there’s nothing it can do wrong or different.
It all comes down to how the sim interprets each pulse, both in terms of how much trim each pulse induces and whether there is some kind of acceleration involved with many pulses in quick succession. And probably on a per plane basis.
I’ve been using SPAD.neXt the last couple of days, which gives me several ways to modify what is sent to the sim. Haven’t come around to fine tuning it, yet.
1 Like
Agree, doubling the button press entries doesn’t help much if at all.
As an experiment, I assigned the left blue (prop) control of my honeycomb bravo to
the rudder trim axis. (As shown below) I then decreased the sensitivity. In my opinion, I now have proper elevator trim function which in real life in my favorite carbon cub is an analog function, not a digital button press function. Wish I could hack the honeycomb trim wheel to be an axis control.
I also have this same issue with my Bravo trim wheel. Funny as this is the only update that has impacted my trim wheel.
Don’t be surprised if your plane tries to kill you when you disable the A/P. 
The trim setting will revert to whatever the axis tells it to, which may be very different from what the A/P has set it to. I suppose that with a little practice you can guestimate reasonably well where the lever must be before you disengage the A/P, but you’ll likely have to re-trim, which is annoying and not very realistic.
I think Honeycomb’s design decision for the trim wheel was the right one. There just needs to a way to adjust the sim’s interpretation of the pulses. It may take a long time before Asobo get around to this, so I’ve decided to try SPAD.neXt for that.
It used to be like this for a long time before it was fixed in one of the more recent updates, but that fix caused a justified uproar among those using trim switches because they began to work much too efficiently when constantly pressed. After SU6 it has been reported that switches work better again, so apparently, the same underlying program code is in play here.
1 Like
Of the many frustrations I have with MSFS at the present, I am not having any trouble with the Bravo Quadrant trim wheel. I didn’t need to remap it, it was fine as is. Now the reversers with the jetliner handles, that’s clunky imo.