No, the drone will not execute the mission like that. This is an error in the simulation only. It does not represent what the drone will actually do.
This bug was fixed btw
Bug Report
When a combination of “Interpolated” and “POI” headings are used in the same flight plan, the simulation does not behave correctly. As the simulated drone transitions from a POI heading to an interpolated heading, the drones heading is locked to the previous POI heading and then snaps to the interpolated heading once it reaches that waypoint.
I would expect that whether the heading at a waypoint is defined by a corresponding POI or explicitly set, the transition behavior should be the same.
The problem is best understood by selecting the simulation button while in 2D mode in this sample mission:
When I am using the simulator while planning a waypoint mission, it would be helpful if the simulation dialog would include the current distance from home/WP1 in addition to the current height, speed, heading, etc.
Every time I create a new mission, the “Path Mode” is set to “Straight Lines” and the “Heading Mode” is set to “Follow Path”. Would it be possible for those settings to be stored in such a way so that they are set to the previous values used?
1 Like
This is not really a bug, Litchi’s waypoint engine works like this even in real flight (the snap will not be as instant as in simulator but it still snaps). It’s also the same behavior for gimbal POI vs Interpolate/Transition mode.
With Litchi engine (both old and new apps), the heading mode at a WP defines what happens during the segment started by the WP (note for old apps Custom+POI = POI mode, different to Custom with no POI which is equivalent to the new app’s Transition mode). If WP1 has POI heading mode, then the drone will focus on the POI until WP2. The one exception is if WP2 focuses on a different POI then it will transition between both POIs.
Agree that both would be useful, I have recorded these suggestions in our system