Having trouble finding a setting for the trim control on your Honeycomb Bravo Lite? I spent weeks trying to figure it out. There are a couple third-party add-on options that can potentially solve the problem but I found them challenging at times and had to remember to run them each time, etc.
I finally found a simpler solution. And it is a setting within MSFS 2024 itself. No third party software. I generally fly GA aircraft, but this should work with any aircraft. It may even work with the Bravo (full, not the Lite). Give it a try as it is easy to do and no harm/no foul.
In the game, go to Settings → Controls. Make sure the aircraft you want is selected in the upper left above the Device List. Select your BRAVO LITE in the Device List to the left. Next scroll down through the Categories until you find your aircraft (Cessna 172 Skyhawk as an example). Click on that Category. Select vHandling. Select ELEVATOR TRIM WHEEL DECREASE (Specific - Digital) and roll your trim wheel UP (NOSE DOWN) and it should map to ‘13’. Now select ELEVATOR TRIM WHEEL INCREASE (Specific - Digital) and roll your trim wheel DOWN (NOSE UP) and it should map to ‘14’. Now here is the kicker where the magic happens. On each of those two settings you mapped, click on the gear icon to the right. Select ‘Device Input value override’ (make sure it is checked) and in ‘Input value’ put in your multiplier (start with 3.00-4.00 and play around until it feels right for you). Remember to do this for BOTH of the input mappings (button 13 and 14).
The important parts of this are that the ‘digital’ mapping using Category → [Aircraft] as above is selected and NOT the ‘analog’ mapping (using Category → Flight Control Surfaces → Control Trimming Surfaces → ELEVATOR TRIM DOWN/UP). The other key is to use the value override to set up the multiplier. One note - if at some point in flight it quits working, hit ESC to bring up the End Flight/Settings/etc. menu and hit ESC again to return to the flight. Sometimes MSFS 2024 drops the connection to the control and that sequence just ‘remembers it’ again. Not a regular issue, but a known bug in the queuing system.
Hope someone finds this helpful and easier to solve than my journey! Stay safe up there!