Spad.Next definitely fixed it for me, with some great help here on the forum. But Asobo needs to fix this ASAP.
1 Like
Thing is though – how can Asobo fix it? If the speed of rotation is realistic, the precision is horrible and you can’t dial in level flight, and people will complain it’s too fast. If the precision is made good enough, it takes a long time to dial in any specific value and people will complain it’s too slow.
I’ve tried setting my spad.next config to exactly match the actual rotation of the Cessna 172 or Cirrus SR-22’s trim wheel, and it’s awful to use. Can’t get level.
Add to this that the current config mixes up the trim buttons with the wheel.
At a minimum, separate “button” and “wheel” bindings might help? Ah well. 
I’m not looking for exact real life. (be nice but) I don’t mind a compromise between precision vs gross adjustments.
Maybe a slider for the user to set it? Either way these folks we give $$$$ too should have never let this be an issue. It has always worked good enough before in the sims I have used. I just want that good…
Not a new feature!!
1 Like
From what I can tell the issue comes down to the design of the Bravo Throttle. If I grab the top of the wheel (12 o’clock) and move it slowly down to “bottom” (~4 or 5 o’clock) the digital encoder for the trim wheel only puts out around a dozen “ticks” throughout that entire motion. That is crazy-poor resolution! The result is what people have said: choose between precision or speed. I don’t know if the encoder itself really has that bad of resolution or if the Honeycomb driver is limiting it for some reason, but until the output resolution of the encoder is improved there isn’t really much Asobo can do to help.
There is one idea from waltersbg on YouTube (search “Fix Digital Trim Wheel”). However, I tried it and it was finicky (especially in VR) but more importantly the freeware software that it requires seemed to be doing some squirrely things to my system (like making my mouse act strange) so I quickly uninstalled it.
Well, just to reiterate, Spad.Next absolutely fixed the trim wheel issue for me. All small prop and jets TW respond now. It’s odd, if Spad.Next can inject some code to make the TW work, you would think it would be an easy fix for Asobo / Honeycomb?
Any chance you might be able to share the changes made in spad.next for the bravo trim wheel to work better?
Does anybody know if the trim wheel specs are listed in some honeycomb brochure or something? Would be interesting to know what the official specs are…
If you message @Sim4Good he may share with you the Spad.Next / Honeycomb Bravo settings. What he sent me worked very well. I don’t want to re-post without his permission.
Thanks, I’ll ping him in this thread since I can’t message it seems due to my account still being newer.
@Sim4good, is there any chance you’d be able to share your spad.next settings for the honeycomb bravo trim wheel? If not, no worries.
Sure. Using Trim Percent in SPAD was much better than MSFS but still giving me some issues I found another event in SPAD using Trim Position (in Radians) and using that for trim completely fixed all trim issues I was having with MSFS and the Trim Percent event.
I commented about this in the SPAD discord and Les O’Reilly, who is a guru about SPAD, was kind enough to make a youtube video on his channel confirming and explaining this. I use 0.02 radians as my value when setting up the Trim Position even in SPAD and you can choose a higher or lower number if necessary to set the speed and resolution of the trim. Most planes I use 0.02 with one plane set using 0.01. Perfect trim control on the bravo trim wheel. I also use the same settings for the trim buttons on the Alpha. It eliminates that initial lag that you get when using Alpha trim buttons through MSFS set up and feels a lot more responsive.
6 Likes
Thanks, really appreciate that. I’ll be giving that a shot tonight.
I can confirm I have tried that and it absolutely does “fix” the trim problem for me - it is still a shame however that you need to buy additional software and configure it yourself to get it work in an acceptable manner, especially when this has been “fixed” before in an update an then “broken” again…
2 Likes
The installation of Spad.next with the trim position set in Radians resulted in a very smooth and accurate Honeycomb Bravo trim wheel action here also.
1 Like
The thing is, SPAD improves so many things. I find it invaluable.
It is somewhat difficult to master, but the more I use it the better I get at programming my bindings. Variables, conditionals, scripts - all contribute to some pretty sophisticated control options. Data Monitor and Event Viewer (or is it Data Viewer and Event Monitor? I get those terms mixed up sometimes…) are very useful as well.
The automatic profile switching, while something that might be coming in FS2024, is also a fantastic tool.
FTR, I use Elevator Trim Position. It’s in radians, so I increment/ decrement buttons 22/ 23 by around 0.02 as well. Pretty smooth…pretty precise.