I’m just trying to trace down one bug. The website build is fine for those who want to try it today. New builds with the bug fixed soon.
Crashing? Try this
I created a testing program that runs and generates a report that you can email to me. It’s a command line program that runs through a bunch of tests and creates a zip file with details about the stick. The same files are saved to the desktop as well, including a .html file you can open and read. same contents as the text file and the json file. feel free to read them all, no PII or anything in there.
Send me the full zip - feedback@ffb-dev.com
Moderator Edit: Direct link to file removed.
@StarlessLion50
The direct links to the zip file have been removed from your posts above. As per this section of the Code of Conduct:
“No direct download links (payware or freeware) allowed. Please direct to a 3rd party site.”
I’d suggest referencing a page on your website that has a link to the file.
Regards,
The Volunteer Moderator Team
Yes, apologies!
New Beta Out! Big Changes.
Changelog link below
Download from the home page as per usual. http://ffb-bridge.com
Many thanks for this I will give it a try, do you know if there are any issues with su5 (and yes I know it just got released, but had to ask anyway :-))
Brian
Nope, tested with it today. My app just uses old established simvars, highly unlikely to churn between versions and easy to fix if they do (just changing a name or two, at worst).
Excellent, thanks I’ii try and give constuctive feedback, may be a day or three.
Hello. I downloaded and installed the program last night. Unfortunately, I kept experiencing crashes to the desktop with FFB-Bridge, and it closed on its own.
You can configure it to give a single, short, noticeable jolt in the joystick when extending the flaps, but there doesn’t seem to be a continuous vibration option when the flaps are extended, is there?
Thanks for your nice tool. It could be the better alternative for my XPFORCE FFB app 
Hey,
Is beta 8 crashing for you? Could you send me the session logs and the previous-session.log?
thanks.
Yeah, can tune it.. right now I haven’t done fine tuning. But the effect can be enabled for sure
Works really nice with the cessna 172 and cessna 152 using the profile included.
¿Could we have a base profile for helicopters like EC135 using the MSFF2 as a cyclic?
Thanks a lot for your job.
Hey,
I play to add 3-4 profiles before launch (cessna, bigger single engine, bigger dual engine, airliner). I unfortunately know nothing of helicopters.. never even tried it in the sim. So I can’t tune a profile.
If someone who knows how to do it can craft a helicopter profile, I can include it in an update. Certainly something I’d like to do.
New beta - https://ffb-bridge.com
Beta.9 is out. This is a focused stability release that (finally!) fixes the crash several of you reported on beta.8 and brings hardware-mode FFB back as the default.
What changed
-
Hardware-mode FFB is the default again. Beta.8 forced everyone onto software-blended periodics defensively, because the crash above was harder to hit in blending mode. It was a race condition issue. With the COM race fixed, hardware mode is the better path — lower latency, firmware-generated waveforms, zero CPU-side synthesis. Existing users who were on blending only because beta.8 put them there are migrated to hardware mode once on first launch.
-
If you genuinely prefer software blending, Doctor > Hardware compatibility still has the toggle and your choice will stick. The auto-migration only runs once per build.
As always
If anything misbehaves, hit Send feedback in the app — it bundles the session log + a crash dump (if any) and opens your mail client pre-filled. Replies come back from feedback@ffb-bridge.com.
Thanks for sticking with the beta. If this crash is truly fixed, we are on a clear path to launch. I will then work on polish, adding profiles, things like that.
OK I have tried the app today and have two logs for you, just noticed that I can in future use the app to send them and will do in future. Basically the app keeps crashing (not the sim) so when it runs looks ok but it just stops and if restarted (with the sim running) and is re-armed works for a short time then just disappears again.
I’ll send the files to the feedback address above.
Happy to test anything if that will help.
Brian
Hey,
Sent you a test build, let me know if it works.
OK after trying some of the options - and testing with the simulated function in the app and then turning on the MSFS 2024 sim, suddely all started working and didn’t close itself. Works well but haven’t had time to go much further. I installed it on the same drive as the sim and not in the default location , not sure that is an issue.
Try the build I sent you just now. Check your email.
Yep, got it thanks. Just gave it a quick go and seems to be working OK. Give it another go tomorrow.
Dev update - the app is mostly working well now, with some rare random crashes that I’m tracing down as reports come in. You can help by submitting reports if it happens to you.
I am now turning my attention to production hardening on the code, interface cleanup, UI/UX improvements and so on. No more new features now.. freezing the feature set for 1.0 unless there’s a major reason to make a change.
The focus now is entirely on making sure the code is production ready and the experience is more polished. The app works, but is a bit “heavy” on the interface, some pages have too much text, some need cleanup…. etc.
Keep those feedback reports coming! help me trace down any final bugs.
I see there are a few people that put their email in but didn’t confirm the download, then tried another email and still didn’t download. I will not (cannot, by law) contact you via email until you confirm the link in your inbox - I have double opt-in as standard.
However, if you are a real person trying to download my software, and there’s some bug in my email send causing you not to get the email, I want to know about it. Contact me via PM here if you want me to investigate.
The person I’m referring to has an email that starts with
- al……@gmail
- and the second email they tried was a.k……@aero
If this is you.. contact me via PM on this forum and I’ll investigate