Deviation model writing service?

That service is also for people who simply don't want to learn to program a transmitter. I get the impression that this isn't an uncommon attitude for users of commercial firmware, and that's why companies like horizon offer config files for all their models.

I don't plan on offering two model files. Instead, I'm going to create a table in the wiki for the models that get created this way - if any ever do. One table for each transmitter, with columns for model info (manufacturer, model name/variant), then a column for each switch on the transmitter saying what it does for this model file, and a link to the model file. A column of notes should do for the other analog inputs, buttons, or odd users of the sticks.

Since it's in the wiki, anyone will be able to add model files to it. Or even create the table if I don't.

My final stance on this is i'd be fine as long as PB and maybe FDR are
Would like to help new users with explanations and files if possible

mwm wrote: That service is also for people who simply don't want to learn to program a transmitter. I get the impression that this isn't an uncommon attitude for users of commercial firmware, and that's why companies like horizon offer config files for all their models.

I don't plan on offering two model files. Instead, I'm going to create a table in the wiki for the models that get created this way - if any ever do. One table for each transmitter, with columns for model info (manufacturer, model name/variant), then a column for each switch on the transmitter saying what it does for this model file, and a link to the model file. A column of notes should do for the other analog inputs, buttons, or odd users of the sticks.

Since it's in the wiki, anyone will be able to add model files to it. Or even create the table if I don't.

Instead of a commented file as I suggested, something like an explanatory text file along the lines put forward by "robpur" in a couple of previous posts sounds more reasonable and less time consuming.