I really like this app, it has been working very well for me (and I would happily have paid 2 or 3 times more for it). I have a question concerning setting the Altitude for Waypoint Missions. Until now, I have been using it in relatively flat open spaces where the ground elevation doesn’t vary a great deal and I easily understand that in this situation setting the Altitude of a Waypoint will determine the height of the aircraft above the take-off point (i.e. ‘ground level’). However, I should like to plan some missions in hills and cliffs near to the sea, where the ground elevation varies considerably from 0 at sea level to hundreds of feet about sea level on the hills and cliffs. Here is the point that I am not sure about. If, for example, I were to take-off from a hill top that is, say, 200 feet above sea level and set the Altitude of the 1st Waypoint as ‘100 feet’, then at the 1st Waypoint the aircraft will be 100 feet above ground level and 300 feet above sea level – I believe that this is correct. Next, if the setting for the Altitude of the 2nd Waypoint, which is some distance away over the sea, is kept at ‘100 feet’, will the aircraft simply fly horizontally at a constant 300 feet above sea level and, therefore, will still be at 300 feet above sea level when it reaches Waypoint 2, or will it descend as it flies to Waypoint 2 and will end up at 100 feet above sea level, but 100 feet below the take-off point? I could try this as an experiment to find out, but getting it wrong could be disastrous as I am a little reluctant to accidentally drop it into the ocean or fly it into the side of a cliff because I have misunderstood the Altitude Setting. I was wondering if anyone knew for certain how it would behave in this type of situation?