Hey the A2A profiles had a regression. Try 1.6.1 and tell me how that feels with the Comanche and the Aerostar.
The overall feeling got certainly better in 1.6.1.
And I found out what’s wrong with the trim now. It only moves the spring offset of the stick, it doesn’t compensate for it by offsetting the elevator center in the sim. I’ve seen there’s a possibility to make the compensation through FFB-Bridge by unsetting the axes in the sim. It only works in 2024 and I’m still on 2020. Shame.
I have a suggestion for you - if you take over the axes in the app, then the basic tuning should also be available there. Like center and extremes’ deadzones and sensitivity.
What joystick are you using? Moza bases do this automatically (I can talk to their firmware). If it’s not working with a Moza base, it’s a bug.
And yeah, 2020 is starting to get a bit long in the tooth, so all development is more focused on 2024 and forward. There’s only so much time in the day for testing, and while I do try and ensure 2020 works OK, doing all the custom testing for all the planes that require manual changes to things (most quality third party) would just take too long for a diminishing population.
Still, I’ll look into making things a bit better for this plane in 2020.
Yeah, I understand, it’s extremely time consuming. I’m thinking to get into 2024 just because it’s gets updates and 2020 doesn’t. May be worth it now while it’s on sale.
I use a Sidewinder FFB2, so there’s no firmware compensation. I figured out how to do it though. It’s a bit finicky but it works fine with the Comanche. It’s a very enjoyable experience now.
I found a funny bug with a Comanche (not sure if other planes also have it). When I shut the engine down by pulling the mixture lever, engine rumble effect stays on even after the RPM become 0. It only goes away after I turn off the magnetos. 
If you’re using a Sidewinder, you can unbind the axis in MSFS 2024, and then FFB-Bridge can control the axis 100%, and then trim and AP follow work perfectly.
Bought 2024. After activating axis control in the FFB-Bridge it says “not available for this aircraft” when I select Comanche. It does work great with the standard planes though. Anyway, as I said, I already have my workaround that works with any plane including Comanche, so it’s not a big issue for me. The feeling is amazing overall (as amazing as a 25 years old stick can deliver, of course 
), and I’m still discovering the tuning possibilities.
Thanks for the replies. I’ll keep sending bug reports through the form if I find any.
This product has revolutionized (simulated) flying for me, rather than spending most of my time in Airliners, on Autopilot, I have been spending the last week or two hand flying vintage aircraft on 1-2 hour flights. It started off really good three weeks ago, and doubled in awesomeness when the 1300 airplane profiles were added.
A couple of problems I have noticed in the latest version versus the prior ones.
First, sometimes, when I start up a flight, FFB-Bridge will note my AY210 is disarmed, there is no ARM button available to press. Both the yoke and flightsim are on, and the plane I want to fly is loaded.
Second, the Sim crashes occasionally. I have been lucky enough that MSFS24 has been very stable for me since the first couple of weeks after introduction. I now have a CTD roughly every 3-4 flights.
anyone else noticing this?
Ah yes, sorry, I should have mentioned that - this feature works for the planes that have the trim compensation tables built in, and that’s all the first party planes.
That’s not to say it can’t be made to work for A2A, I’ll look into it. I am going through the profiles for improvements, things will continue to get better.
Thanks for the nice words about FFB-Bridge, glad that you like it.
For your issues:
-
When this happens next, immediately hit the “Report an Issue” button, fill out the form with your info, and submit. This will send me the logs with the exact state of the program, making it easy to find the issue.
-
This one is new to me - no one has yet complained about MSFS crashing. I also spend hours with FFB-Bridge every day and have for months and it has never crashed MSFS. FFB-Bridge doesn’t really interact with MSFS (it’s a passive reader), so the odds of it crashing MSFS are low. Non-zero, but quite low.
Same thing to do: Next time it happens (MSFS crashes), immediately hit the “report an issue” and tell me it crashed in the notes. I’ll then be able to tell you whether it was FFB-Bridge that caused it.