Making Input of Butterfly Mixer arbitrary

Hi Jeti Developers

Please make it possible to choose an already assigned function
as the input of the "Butterfly" mixer.

Many people use this mixer as a comfortable universal wing mixer,
doing any flap and chamber with it even with 2 ailerons only.
The live trim of the elevator is awesome when using this mixer.

It would be very much appreciated if the input can not be an
anonymous control element only but an already assigned function also.

This way the function can have a curve as any other function and
can be mixed with an other function prior to work as the input
of the "Butterfly". "Snap Flap" for example could be realised
this way. Simply applying a free mixer Elevator > Flap to the "Flap"
function then working as input for "Butterfly".

Or one could have a function curve at the flap function to make
the movement linear. Or one could simply scale the movement of the
Flap function by the dedicated function curve.

There is already a LUA App in the field as work arround to the current
limitation. This seems dangerous to me and shouldn't be necessary.

Regards
Dieter

Hi,

................................
Jeti answer :

at the moment you can do a butterfly curve via a free mix from Butterfly to flaps or ailerons.
.............................


Regards
PW

PW wrote: Hi,

................................
Jeti answer :

at the moment you can do a butterfly curve via a free mix from Butterfly to flaps or ailerons.
.............................


Regards
PW

Hi

Thanks, but this is not what we want. When using the Butterfly as input of a mixer, only the unscaled current control element of the Butterfly (per current flight mode) is the exported value. This is completely useless resp. is not using the Butterfly features at all. Please read again my proposal.

Regards
Dieter

nichtgedacht wrote:
Thanks, but this is not what we want. When using the Butterfly as input of a mixer, only the unscaled current control element of the Butterfly (per current flight mode) is the exported value. This is completely useless resp. is not using the Butterfly features at all. Please read again my proposal.

Regards
Dieter

@Dieter Sorry you are complete wrong!!

You put the basic values of flaps and ailerons in the Butterfly mixer and only the additional needed values for the
function curve were added per mixer Butterfly to ailleron or Butterfly to flaps!

Hallo Harald,

viele viele Seglerpiloten wünschen sich o.g. Funktionalität, die übrigens stellenweise bei 20 Jahre alten Funken schon Standard war.
Sie nutzen z .Zt. die Butterfly-App, die aber, wie schon oft diskutiert wurde, gewisse Risiken birgt.
Viele machen sich hier die Mühe, Jeti davon zu überzeugen, diese gewünschte Funktionalität irgendwann mal zum Standard zu machen und somit auch den Sender weiter zu entwickeln.

Warum muss man da jetzt immer und immer wieder gegenarbeiten um diese Evolution zu unterbinden???
Ist das ein persönlicher Triumph für Dich oder was treibt Dich da an?
Entschuldige die direkte Frage, aber ich kann es einfach nicht nachvollziehen....

Gruß Ludger

HNAGL wrote:
You put the basic values of flaps and ailerons in the Butterfly mixer and only the additional needed values for the
function curve were added per mixer Butterfly to ailleron or Butterfly to flaps!

Yes, your are right. But this additional "needed values" are derived from an anonymous control element as P4 for example.
There is neither a possibility to have a curve for this master value within the "Butterly" nor to assign a full featured function
to it. This function would naturally have a curve outside the Butterfly as "Aileron", "Elevator" and "Rudder" also do. One could even mix this proposed "Flap" function value with another function.