Other Moza equipment profiles

1 reply 196 views started 1d ago
#1

A potential feature that I fully expect is out of scope, but may be more possible with the recent partnership with Moza. Would it be possible to bring over profiles for other Moza equipment, like rudder pedals and or throttles for instance, and even change them.

My goal for suggesting this, is the streamlining of how a user access, edits and controls their controllers. I currently run the AB6 (with MHG stick), and the MTQ throttle. Both the AB6 and MTQ have features which can have their button/Axis behaviours changed via Moza Cockpit per profile. If I am running FFB Bridge and want to change aircraft that require different throttle profiles, I have to exit FFB Bridge, start Moza cockpit, change the profile, close Moza Cockpit, restart FFB Bridge. For clarity I am not meaning different bindings, rather, Moza cockpit can change how some of the physical controls behave, either like a button, axis or a hybrid. This can become tedious when assigning button mappings, changing button settings in either the sim or something like Axis and Ohs.

The direct example on the AB6 force feedback base is the two sliders. In Moza Cockpit these two sliders can be set as a three position switch (bottom, middle, top), a regular axis, or a mix of the two. And as an example, all axis on the MTQ throttle can have their behaviours changed, where detents are, whether buttons activate as detents, if the full run of the axis is used etc. Useful when changing between helis, piston, turboprop, and other aircraft. It would be awesome to not have to juggle two pieces of software, especially when they both are built to automatically change profiles based on the loaded aircraft.

I understand if its out scope, it certainly isn't a deal breaker for use, just seems like a good idea to me. It would almost nullify the need for Moza Cockpit, aside from firmware updates. So, you don't know if you don't ask.

Rapport
#2
In reply to TheLimbix's post

The FFB-Bridge overall philosophy is simple. Be a vendor-neutral, simmer-first place for force-feedback devices. As a user, you should be able to use any FF device from any manufacturer, across any OS, and have a good experience.

However, the manufacturer will always have a better app to do deep stuff in their hardware. Trying to take over this for every manufacturer is not really feasible because I'm just one guy, trying to keep up with so much will drive me batty :)

So my answer is - if a feature fits in the overall philosophy of FFB-Bridge, and it's technically and legally possible, I will consider it.

There's of course a much larger decision matrix I go through before I add a feature. Stuff like - Does this make sense cross-sim, and cross-platform? Will it benefit a large number of users? Does it enable interesting use cases? Is it possible to maintain the feature going forward? Is it even fun? And so on. Lots of things I think about.

Adding features is easy, but making a cohesive program that delights users.. that requires careful thought and editorial judgement. Otherwise you end up with a mess of features that don't hang together in a rational manner.

So I'm not saying yes or no to your request, and I do very much appreciate your bringing it up. I just wanted to lay out a bit of the thought process that I go through, and the direction I'm trying to take FFB-Bridge in.

Hope that helps!

Rapport