Trim not functional (AY210 / MSFS / C172)

Agreed, something is a bit off. I just tested again, and am working on fixing this.

I have made many changes and improvements to the trim in Beta2. Test it out and provide your feedback, please.

https://ffb-bridge.com/beta

1.5.1-beta.2

This beta includes substantial work on MOZA AY210 trim handling, with particular attention to the Cessna 172 G1000 in MSFS 2024.

The aim is to make trimming feel more natural: progressively relieving the pressure needed to hold the yoke while reducing unwanted aircraft pitch changes when your hand position stays steady.

What changed

• Improved AY210 trim input compensation while keeping spring resistance and other force effects active.

• Corrected spring-centre handling and the delivery of small trim adjustments.
  

• Added aircraft-specific compensation for the MSFS 2024 C172 G1000 Passengers variant, including compensation for changes in control response with airspeed.
  

• Expanded support diagnostics to help investigate trim behaviour.
  

• Improved update-check errors: connection failures, certificate problems and server challenges now provide useful details instead of a generic internet error.
  

The aircraft-specific compensation currently targets that C172 variant. Other aircraft receive the shared AY210 changes but do not receive the C172 calibration. A quick X-Plane C172 check found no regression.

Please help test

• Load the C172 G1000 in MSFS 2024 and establish steady flight with autopilot off, using your usual FFB settings.

• While holding the yoke reasonably steady, apply a few small nose-up trim adjustments. Stop trimming for several seconds, then try small nose-down adjustments. Fly normally whenever corrections are needed.
  

• Notice whether the holding pressure changes progressively and whether the nose moves as soon as trim changes, before you move the yoke.
  

• Pause and immediately export a support bundle from Support → Diagnostics, so the recent trace is included.
  

Send the bundle with your aircraft, simulator version, hardware and trim-control method, plus a short description of what you felt and what the aircraft did.

Feedback on improvements, remaining problems and behaviour in other aircraft is welcome.

Hi, and thanks for the quick turnaround. I jumped right in to test it.

My test routine is based on what I used to practice during my real-world flight training:

• Established in level flight at normal cruise speed (2400 rpm)
• Power reduced to transition to slow flight (2100 rpm)
• Altitude maintained by progressively raising the nose as airspeed decreases, which means noticeable back pressure on the stick
• Once airspeed has stabilized and the slow-flight attitude is established, trim nose-up to cancel out the stick force (the stick stays still while the trim is adjusted nose-up until no force is needed to hold the attitude)
• Power increased to get back to cruise speed, with the reverse sequence (progressively lowering the nose until cruise speed is reached, then trimming out the nose-down force without the stick moving)

Setup:

• MSFS 2024
• Default C172 G1000
• Calm weather
• Default FFB-Bridge settings for the C172 G1000
• Recommended Hardware settings (35% / 50%)

And... the test passed quite well :-) The trim compensation isn't always 100% exact (sometimes you need to nudge the stick a tiny bit), but we're talking about a hair's width here, and that's already really, really good!

A few remarks along the way since 1.5.0:

• I couldn't keep the FFB profile I was using before (a modified C172) because I was getting erratic behavior and couldn't figure out which setting was causing it.
• I had to lower the effects slider in the Hardware section to 50%. In 1.5.0 I'd had to push it to 90% for the effects to be noticeable at all, because they were overly subtle in that version.
• Even so, taxi effects feel very (too?) strong in 1.5.1. I haven't had time to figure out which setting is responsible, whether it's rumble, shimmy, or something else.
• I find the spring effect in the default 172 profile too strong. But I was pleasantly surprised to find that I could reduce it without it seeming to cause any trim issues. To be honest, I don't know exactly what it's like in real life, since I've never flown this exact model.

Anyway, great work. I'm really glad to have my trim back :)

If needed I'm happy to help with fine-tuning all this. In particular, I fly Black Square's Commander 144 a lot (excellent aircraft). I haven't tested it yet, but I imagine the trim will need to be calibrated differently. Would be glad to contribute a profile for it eventually.

And it would be really great if FFB-Bridge were "open" enough in this particular area to allow fine-tuning for each aircraft. I think that's the point of this feature request: https://ffb-bridge.com/community/t/108-variable-force-curve-based-on-trim-position?page=1#post-5432. See also this post about the solution VPForce offers for this: https://forums.flightsimulator.com/t/list-of-force-feedback-hardware/648622/39

PS: I saved a support bundle as requested. Let me know if it would be useful for me to send it over.

Best

Thanks, good to know it’s working better. Yes, do send me the support bundle, it will help calibrate that last little bit.

I’m working on building some kind of calibration wizard/test that will be user accessible, and will help dial in that trim on any aircraft.

Okay, done (FB-WEB-GEN-008H)

1.5.1-beta3 is out

**Expanded AY210 trim support in MSFS 2024. ** Aircraft-specific trim compensation now covers 48 default aircraft families and 101 variants. FFB-Bridge automatically applies the matching compensation when a supported aircraft loads.

**Improved trim in X-Plane 12.2 and later across supported FFB hardware. ** On aircraft using X-Plane's standard trim system, trimming relieves pressure without adding an unwanted control input while you hold the stick or yoke still. This benefits both modern bases and older devices such as the SideWinder.

I have manually tested a few (Cessna 172, Corvallis, DA40NG, Extra, P51D) of the 48, but not each and every one. It seems to work OK (MSFS animation issue remains, but that's just visual and nothing I can do about that anyway).

Could you try a few planes and tell me your thoughts? And with XP as well (12.2+ needed)

Absolutely, will do this weekend!

XP 12.4.3 b2

M1 MacBook Pro 16GB

AY210 / MFY

FFB-Bridge 1.5.1 b3

Hi, and thanks for this great update!

I've been able to test it with the default C152 and DR400, and it works equally well.

Looking forward to seeing how we'll be able to configure this for other aircrafts beside default ones :)

Thanks, and I'll just write here what I emailed you so others can get the context as well.

" Thanks for your help on this. Regarding adding more planes - I'm still working through this. I'd built a wizard, but it's really not working well so I pulled it from the build. The issue is that it was really hard (basically impossible) for me to feel the subtle changes and accurately dial stuff in.

So, instead, I was able to get the aircraft config data from the sim, and use that to build this trim compensation. It seems a better approach because it's deterministic and I can build separate testing tools (I have CLI tools that show the center and force moving, and feel the compensation.).

Wait for a little bit, I will be trying various things on my end. I build lots of things that are stupid ideas that you'll never see :). You only see the stuff I consider "acceptable". I'm not there yet for the custom trim.

"