I was just trying out a flight from Redhill to LeTouquet to see how well SkyDemon coped with the stepped-climb required to remain clear of controlled airspace, and found that while I could control the climb to some extent, I couldn't get exactly what I expected without adding in a LOT of extra waypoints. The best I managed is shown below:







In particular, notice that the climb from 1400' to 2400' starts before Bough Beech not after it, thus causing the flight to enter CAS. Second, whereas I would like to step-climb (or even better, cruise-climb with SkyDemon suggesting a desired RoC in fpm) to remain just below CAS at all times, the actual profile created keeps me at 2400' all the way to LYD, then makes one long climb all the way up to FL054 (which, interestingly, is shown as 5400' despite the airspace being define as a flight level).



Am I doing something wrong, or is this something that isn't (yet) supported fully by SkyDemon?



Thanks,



T67M

I manage this by simply adding waypoints along the track at which I want to remember to climb.  Defining these points relative to the turning points makes it easy, e.g. if I wanted to climb at CPT 270/10 I would create a waypoint named like that in Skydemon, and in the aircraft's GPS (its in the panel so I can't upload but it is very quick, accurate and easy to add waypoints to the GPS by hand when named in this way) and then use this "turning point" as a prompt to remind me it's ok to climb, or I need to descend... works for me!