Larry Fortna
Retired 72 year old, previous RC club officer and flyer of RC controlled aircraft. Been out of the game for a few years, but bought a Tello drone for some fun and then a Mavic Mini.
Comments
Recent activity by Larry Fortna
-
I understand, but there are 3 markers between 9 and 13 all of which have interpolation values set to none. I would have expected the marker 13 interpolation value to begin at marker 13 not marker...
- View comment
- 0 votes
-
So the last change I had made to the plan was at marker 13 in which I set interpolation to curved. I ran the mission in preview mode and observed the same flight path as it did in real time so I c...
- View comment
- 0 votes
-
One more screen capture. This is where the drone was actually on the correct 270 degree path heading after marker 9.
- View comment
- 0 votes
-
Is the SDK bug only triggered by the Beta release? What about the zoomed map?
- View comment
- 0 votes
-
I modified the plan to use a destination component at the end rather than depend on just a path with markers. That seems to work just fine. I'm not going to worry about it, but if it happens agai...
- View comment
- 0 votes
-
I would be inclined to agree with you except for the fact that the drone should not have descended from 50' to 8' until it reached marker 3. The actual decent came about at marker 2 which was a si...
- View comment
- 0 votes
-
If you watch the video again, go to the 3 minute mark and pay attention to the altitude of drone as it approaches marker two. It is easy to spot on the 24th because it missed the bush by a foot.
- View comment
- Edited
- 0 votes
-
Marker 3 was where it was supposed to have dropped from 50' to 8'. However, the problem occured at Marker 2 which was simply a Point of Interest marker to face the drone toward the landing zone. O...
- View comment
- 0 votes
-
I can understand there can be deviations and such, but what occurred on both the 24th and 25th with the same plan was an unexpected drop in altitude, not just a deviation. Yes, it could explain th...
- View comment
- 0 votes
-
Encountered this again today... Had disabled hardware acceleration in Google Chrome. When I put it back, the problem went away.
- View comment
- 0 votes