Simplified mixer

Heli:
Normal (NORMAL, NORM)
Stunt 1 (STNT-1, ST-1)
Stunt 2 (STNT-2, ST-2)
Hold (HOLD, HOLD)

Airplane:
FMode 0 (FMOD-0, FM-0)
FMode 1 (FMOD-1, FM-1)
FMode 2 (FMOD-2, FM-2)

Glider:
SPEED
CRUISE
THERMAL
LAND
LAUNCH
DIST

Maybe we need Flight Mode Name function?

make sure you have the helistd.ini template file installed. You should also try directly loading this template.

That is a bug from when I changed from 'simple' to 'standard'. I just committed the fix

yes please. you don't need an account to submit bugs (though I think it helps if you want to be notified when they are fixed)

So, happy new year for everybody, here I am again, pretending to work while actually thinking about deviation...

Since the simple GUI didn't let me sleep last night, I was thinking about it a lot.
If you don't mind I will share my thoughts with you.

First it is a huge help to all the novices, who come to deviation, but don't really understand the "advanced" mixer.
However, since they all (but a few, who just bought the DEVO because of deviation ) come from the devention interface, the more it corresponds to the original the easier for them to convert their existing model configs to deviation.

That's why I was against the 9 point curves:

FDR wrote: Besides, I don't get why curves are 9 point?
All the DEVOs (except the 12) have 7 point curves, so if we want to give them a similar and hence familiar interface, why don't you offer a 7 point curve?
I have to admit, that I like quarters better then thirds, but this way existing DEVO users have to recalculate all their curves...

I think, the 9 point curves won't offer too much advantage to those, for whom the advanced mixer is too complicated anyway...

So, if I were you I would:
- make the curves 7 point;
- make D/R assymmetric, and let it go to +-125% (instead of 120%);
- the range of the subtrims differ too (62.5% in 0.5% steps vs 50% in 0.1% steps), but I think it's not that important.

Since it starts to get too long, I will write about all the menu items in detail one by one...

About the model menu page:
I've got idea about the new uniform icons, just need some time (and some more) to draw them...

I would reorder the menu items later to match the setup order (and the color code of the icons, but more about them later), since on the touch screen it is not necessary to start with the most frequently used ones, because all are accessible on one page.
(BTW since the DEVO 10 remembers the last used one, it won't need the most frequent first either...)

I think this thread is not about debating whether the simple GUI is needed or not...

So, I continue in no particular order, just as they come to my mind...

About the switch assignment:
First, it shouldn't allow the same switch to be configured to controversial functions, however it might enable for example the flight mode and the gyro for the same switch. (i.e. currently the throttle hold should be different)
We may leave that to the users, but we want to help them, don't we?

Second:
- flight mode has more options then the original, which is good;
- the gyro has about the same options as the original, so this is good also;
- however the throttle hold has fewer options, because the use of the 3 way switches are not specific enough.

Also, I would like the throttle hold and gyro switch to be on their appropriate page too! (The gyro switch is there in the original fw...)
The purpose of having them together too is to see, are there any contradictions.

Next is the gyro, because it is related to the previous:

If the gyro switch will be there too, it would be nice, if in case of a 2 way switch is selected, the third value could be hidden or disabled.

The range is 0%..+100% mapped to our -100%..+100%, which is good IMO.

Throttle hold is alike:
If the throttle hold switch is configured on that page (too), there is no need for the on/off option: if a switch is selected, then it's on, if not, then off.

EDIT: ...and of course if the switch is none (or off as you please), the value could be hidden or disabled.

Swash type:

I've already asked about that:

FDR wrote: Don't you think that the simplified swash form could be unified with the heli options form?

D/R & Expo:

The main thing here is that the original allows you to set asymmetric values, and that the rate value's range was +-125% in the original.

Other then that I miss the +-100% markings on the graphs, and they xy proportions are off too, since the whole y axis is 240% now (should be 250%), while the x axis is only 200%.

About the curves (both throttle and pitch) in general:

I think the function of the "auto" button should be really automatic, i.e. for every point value change and locing/unlocking it should recalculate the automatoc points and redraw the graph.

Other: the mid point is locked in the original, but it is not that important IMO.

That's all for the pitch curves...

However in case of the throttle curves, there is the question: shouldn't we map these to the 0%..100% range just like you did with the gyro value?
The original (and I think the other brands too) handle the throttle between 0 and 100.