Mission waypoint bugs in latest release of QGC

I am using latest release of Ardupilot on Plane. I planned a mission using ‘above terrain’ (mission planner would call this Terrain frame) as the initial reference, then added waypoints, and finally a landing sequence, then uploaded this to the plane. I also saved the mission to a file. I then disconnected the plane and closed QGC, then opened QGC again, and loaded in the mission from the saved file. The landing sequence doesn’t show the same now. Instead. It shows a ‘Land Start’ point in the mission which is 2 steps from the landing point instead of the landing sequence I had saved, and it has inserted a waypoint in between this Land start point and the land point itself, and now all the altitudes show with the AMSL frame type instead of Terrain frame - the altitude values of each waypoint are converted to AMSL values though in this instance - so that in itself is OK as both the values and the reference frame match (but a bit annoying as no way to show it back in ‘above terrain’ values), but if I download the mission from the plane to overwrite the one on the screen - the mission looks almost exactly the same except that it has now replaced the AMSL reference altitude values with the ones I originally entered (30m that originally entered using an ‘above terrain’ reference) but with the frame still showing as AMSL - so my 30m altitude now shows as below the ground level on the chart at the bottom of the screen (see below). Really messed up, and I would say dangerous!

Just as a follow up. I just launched the current version of Mission Planner and downloaded the mission from the plane into the planner screen. This shows that the value scale that was used when saving to the plane was AMSL frame, but the actual values/numbers shown are those related to Terrain - so QGC really messed up here! I am able to change the scale/frame reference in Mission planner to Terrain frame, which corrects the value references, and cvan see that if I then save this back to the plane, and then read it back from the plane, this verifies they were saved correctly by Mission Planner. This hopefully demonstrates that there is a serious issue with QGC, and I am happy to provide more details if devs need them.

Actually it wouldn’t. “Above Terrain” is not equal to Terrain Frame. Above Terrain takes the amount you want to fly above terrain and calculates and AMSL altitude based on that. If you want to use Terrain Frame you must use “Terrain Frame” It might not show up until you connect to a vehicle which has the TERRAIN_ENABLE parameter turned on. Also there was a bug in Landing Pattern which has been recently fixed. Daily builds have the fixed. Can’t remember if latest Stable has it in it yet or not. If not 'll be marking a new stable soon.