after having used Skydemon since quite a while, I've invested quite some time to build very detailed performance profiles based on the figures from my three relevant POHs, generating the whole XML-Data of the profile via a makro from a very detailed spreadsheet. While the current possibilities with multiple performance values per profile for different altitudes is great, this could easily be extended to offer even better flexibility without much effort:

Suggestion 1:

Add an (ISA based) temperature field to the performance data, allowing us to enter multiple values for the same altitude (e.g. ISA, ISA+20°C and ISA-20°C). Then either let us select the correct temperature level (e.g. ISA+20°C) in the "route"-tab in addition to the performance profile [basic implementation] or alternatively calculate it based on the weather data for the planned route (maybe even even interpolating the performance figures, e.g. for a leg in ISA -7.4°C) [advanced implementation]. 

But when using power percentage profiles, one always need to keep a copy of the power charts at hand, especially when flying permanently changing altitudes (starting at 2500 ft, then 4500 to fly over a CTR, then 5500 when turning NE, then 2500 while turning NW and flying below an C airspace....). It would be great if SD could just show the appropriate values for the selected profile during navigation so I can see my target RPM (and MP, if applicable) value for the current altitude.

Best regards

Florian

while I can understand that you're hesitant regarding the different temperatures, adding (optional) fields for RPM and MP wouldn't make it more complicated but add quite a level of comfort especially for pilots flying many different planes.

In addition when entering the performance data for the different altitudes it would be much more user friendly if the data could be directly entered in a table containing addition rows for the intermediate altitudes in steps of 1000 or 2000ft containing the values calculated by SD. 

That way, when entering the performance data for e.g. a C172, one e.g. start entering the data for the lowest altitude (e.g. 2000ft), the highest altitude (e.g. 12000ft) as well as the altitude with the peak TAS (e.g. 6000ft) and then compare the calculated values for the intermediate altitudes (4000 / 8000 / 10000ft) to see how far they are apart from the POH figures to decide whether we want to add more data or keep it that way.

Best Regards

Florian