By "not working" I meant ... the app is running but there is no movement anymore on my AB9.. even in the Flight Check. But It says the AB9 is connected.
And also, set the damper in the Moza cockpit to 10-15%. 0 causes issues with oscillating sticks - though the next version will have safety clamps built around that.
New version is out. Lots of changes around safety, and hopefully the bugs with Logitech and Sidewinder are fixed as well.
One big change for Moza users. The app now automatically scales forces for stronger bases. Sidewinder and Logitech are 100%, Moza/Brunner will be automatically scaled down to 35%
Unknown sticks will go lower still, to 20%. This is to deal with things like the Rhino or upcoming strong bases from other manufacturers.
Go to Hardware -> Effects, and you can change this to suit yourself. There is a checkbox that ensures you don't randomly enable 100%. Once you acknowledge that you intend to do this, the slider unlocks and you can go all the way to 100% of whatever the base you're using can do.
Note - this does NOT override Moza Cockpit; If you are already scaling forces there (70% is a common default), this becomes the max force that FFB-Bridge can hit. It cannot override the stick's own firmware (which is set by Moza Cockpit).
I would recommend setting it to 100% in Moza Cockpit. Then, inside FFB-Bridge, you have the whole range available to you and it makes it easier.
WOW, first flight tests felt amazing. Now, the forces are softer, even "elegant" by default. Thanks! A few observations: -I think the default profiles need to be reviewed now. I had to increase "Master Gain" to 100% to every one of them to feel the forces according to my own preferences on AB6 base. For both aircraft and Helos. Maybe the individual forces, effect gains, trim, stick feel, etc, will need an update on the default profiles? I don't really know how you make/balance/set every default profile, so I ask. :-) -Is still needed to set MOZA´s damper slider to 10-15% ? I understood from previous posts that this new beta will make unnecessary increasing that setting. -Can you add a jet default profile, like for F/A-18 ?
Thanks a lot for your continuous (and really fast) work.
Yes, set the Moza Cockpit Damper to 10-15%. It does not affect the FFB-Bridge forces and adds an additional layer of safety to the stick.
Regarding the profiles - yes, once the release stabilizes and people don't report bugs, I'll move to profiles as well as the UI. The UI is becoming a bit overloaded with all the features and effects and tuning options, and needs some cleanup and simplification.
If most of the bugs are squashed, I hope to release 1.3 stable next week.
Tested latest build in sim and everything pretty much working well with my ms sidewinder ffb2, except every now and then some effects stop working when restarting flight or sometime the whole app shuts down.
Great - yes, the app crashing is a real bug and fixed in the next version, as is the effects not working. Thats' likely the safety stop being too aggressive. It has been tuned.
So all the helicopter related settings and effects are working well? Anything missing?
yes pretty much all good. Still not crazy about damping It does'nt feel linear throughout stick travel. I would prefer abit of friction effect as thats I remember from my rl flying.
Thanks, I'll look at this for the next beta release. Let me know how beta 18 does, especially around the Safety Stop trigger. Is it still too aggressive?
New version (1.3.--beta.19) with Stick Friction out shortly. Let me know if this is good. There's a new section in Tuning, and a new test in the Flight Check page as well.
Now, I will be turning my attention to cleaning the app up - Tuning and some other pages are becoming rather large and unwieldy. Needs some ui/ux cycles.
Keep sending feedback and I'll make bugfixes, but at this point 1.3 is pretty much feature complete.
There is one more thing which might need (or could take advantage when improved) a solution.
FTR works great and I love it. Problem is, that the changed position of the cyclic impacts the autopilot, because AP has to steer "against" (trim) the input coming from the cyclic, because FTR does not shift the "null zone", but holds the cyclic input in position.. so it works exactly as we want it.
But when using "terrain follow" ( autopilot low level flight based on radio altimeter ) it can break the function depending how far I moved the cyclic away from the physical null-center. So if AP is engaged it could make sense to animate the cyclic slowly back to 0/0, like it would be a normal spring-loaded joystick.
The ability to disengage FTR by a button is nice, but it's not possible to do this from the aircraft plugin, because I cannot "press" the learned joystick button per software.
Maybe the "follow autopilot" option could be modified accordingly or is there anything else you could think of how to fix that ?
The ability to disengage FTR by a button is nice, but it's not possible to do this from the aircraft plugin, because I cannot "press" the learned joystick button per software.
Interesting. So, if your addon was able to communicate with FFB-Bridge, say I exposed the controls for FTR enable/disable via an API, it would solve this? You'd have to do some work on your software, but it should be simple enough to make that call.
It's not a bad idea to build hooks for better integration with addon makers. I don't think it makes sense for FFB-Bridge to try and detect the addon and then try and customize behaviour for each.. that won't scale. But if I publish an API, addon makers can consume it for better integraion.
Do me a favour please? As an addon maker, tell me your wishlist for automated ops with FFB-Bridge. What features would be most useful if you could call them from your addon?
I will think it through. I don't think I will expose the force controls directly (safety reasons), but I could expose a few things that are non-safety related.
I see the charm not having to install and maintain a SIM plugin just to communicate with ffb-bridge, if not needed. So I wonder if we can get an API without it.
Right now you're reading flight data (i.e. DataRefs from X-Plane) from the SIM through a different mechanism (I assume the UDP or REST API) and I'm not sure if this can be expanded as needed. So you can "see" if the autopilot is engaged, which airspeed we're gong, altitude, vertical speed....etc.
In X-Plane the aircraft plug-in can create new DataRefs (variables used by the simulator) and store all kind of information in it. If your method can read "any" DataRef from the SIM, then I could create a dataref following your requirement, which you can read and do something with it. It could be a command or just plain data like .. um... outside temperature.
If so, it would be easy for me to set this dataref to 1 if FTR should be enabled or 0 if not. Another dataref could be used to "enable cyclic position to 0/0 if AP switches from disengaged to engaged". Just as an example.
I do not have a list of nice-to-have things yet, but I see the more options we get the more ideas are coming up. The ability to directly talking to an open-minded developer is a valuable treasure :)
reg.: MOZA AB6 - Beep Trim is delayed, then jumps instead of moving continuously
Hi!
I am testing FFB-Bridge 1.3.0-beta.19 with MSFS 2024 and a MOZA AB6.
Normal force trim works correctly: Holding FTR releases the cyclic. Releasing FTR sets the current stick position as the new held position. Cyclic damping and friction also work as expected.
The problem is Beep Trim.
Expected behavior:When I hold the Beep Trim hat direction, the force-trim hold point should move slowly and continuously in that direction. The stick should gradually follow the new position.
Actual behavior:When I hold a Beep Trim direction, nothing happens for about 5-7 seconds. Then the stick suddenly moves a large distance in the selected direction, as if the trim inputs had been buffered and applied all at once.
This happens even in Flight Check with the Demo source, so it does not appear to depend on MSFS telemetry or the aircraft.
Current configuration: Device: MOZA AB6 Backend: DirectInput/PID Effect rendering: Hardware Maximum physical strength: 35% Hardware cyclic damper strength: 100%
MOZA Cockpit: DirectInput mode, Spring 0%, Damper about 10%, Inertia 0%, Friction 0%, Overall FFB Intensity 100%
Profile control system: Rotorcraft Trim style: Classic force trim FTR button: assigned and working Beep Trim: assigned to the stick's hat switch
I also tested Raw HID/PID, but with that backend FTR hold and friction no longer worked correctly on my setup, so I reverted to DirectInput/PID.
Could you please check whether Beep Trim has a delayed or buffered update issue on the MOZA AB6 / DirectInput-PID path?
speak about beep trim. Can you make sure there is a way to NOT have it automatically mapped to any keybinds , becuase all my keybinds are already spoken for and used for other stuff. Thanks
speak about beep trim. Can you make sure there is a way to NOT have it automatically mapped to any keybinds , becuase all my keybinds are already spoken for and used for other stuff. Thanks