Lastly the result of the flight. Note the missed images on the first leg and makes for a very abrupt mission not to mention really slow getting around the turns:
looking at the waypoint programming, I don’t see any reason they the first leg was skipped.
cam trig did was turn on after wp4, and then off after wp 6, and I can see that the cords are 172m apart. so I don’t know why it didn’t work.
the slow wp’s issue is because there are duplicate wp’s with the same locations, this is a bug because the leadin/overshot distance are set to 0m
So if I add a meter to the leadin and ovreshot it will work? Just tried it, but the same results. Any workaround for this? If I didn’t throw the old missions away I wouldn’t even need to create new ones. Maybe I could use previous flights. I had asked this in another thread, but no answer. When I downloaded the data flash files preciously for goetagging, there’s 3 other files 2016-07-30 10-16-14.log0wp, 2016-07-30 10-16-14.log1wp and 2016-07-30 10-16-14.log2wp. Seems the 1 and 2 versions aren’t complete, but the 2016-07-30 10-16-14.log0wp loads like the original mission. Is that ok to use? Thanks!
Awesome! Work today consisted of flight plans I had saved previously, so the day went well. BTW, can I use those other files for missions? The next few jobs had pretty complex flight plans. If I can use the .log0wp files it sure would save a lot of time.