We have some big news...LCMC is coming to Autopilot! We are still testing the feature internally, but it should be available for external testing shortly. It is important to note that
some features in Waypoint Mode will be disabled when using LCMC.
That's awesome! I can't wait to try it!
BTW - I found a bug today that hopefully you've already found and corrected - but in case you haven't, I'll mention it here:
I was creating a waypoint mission. I created about 12 waypoints - and then went back to the first one to assign altitude and speed. At each waypoint, I wanted to hover and take a picture also.
Now to be honest - when flying the mission - nothing worked like I expected and the camera aim was all over the place with the aircraft yawing at strange times - but that's not what I'm calling a bug. It's possible that was my fault.
Back to the bug. Ok, so - after I set the altitude and speed on Waypoint 1, I clicked next to go to Waypoint 2 and then clicked Previous, Previous for Altitude and Speed - and then clicked Hover. The instant I clicked Hover - the value for speed changed from "Previous" to "Input". That's the bug. When clicking "Hover" for a waypoint action - the value for Speed changes to "Input" regardless of whether it was set to "Previous" or the other setting.
As for the behaviour I saw when I executed the waypoint mission - I'm not sure if it was a bug or not. Unfortunately I didn't save the mission - but for the Focus parameters I had selected "Direction" relative to "Course" at 270degrees. Each waypoint was set for 75m, 35km/h, hover for 5 seconds, start camera photo HDR, 3 seconds.
First of all - I'm not sure I understand that the 3 seconds is for.
But what I saw as this ran was that drone would fly to a waypoint at the correct speed and yaw - and when it arrived - it would begin to higher, then start yawing and the picture got snapped during the yaw (so they all came out very blurry).
It was almost like the camera action when attached to they waypoint (or the hover action) did not respect my focus strategy for the mission and while it was hovering, preparing to take the photo - it wanted to point the drone in the direction of the next waypoint instead of honouring my focus strategy directive "direction 270degrees relative to course".
Is that clear...? Now that i type it out in detail - I do think that this is also a bug. To recap - the drone flies from one waypoint to the next yawed 270degrees (as expected). But when it arrives at the waypoint - it *should* hover and take a photo - but just before it takes the photo, it begins to yaw. I think it's unwinding the 270degree yaw so that it can point at the next waypoint.
Have either, or both of those problems already been discovered/reported and corrected for the next release? If not - please investigate!