ArduPilot / ArduPilot/MissionPlanner
MP 1.3.10 release notes say waypoint delay issue fixed, but it isn't
- Dominant language
- C#
- Stars
- 2.4k
- Forks
- 2.9k
- Avg merge
- 19h 16m
- Merged PRs (30d)
- 4
Description
It appears from the release notes that you guys did quite a bit in MP 1.3.10. I noted two items among many that interested me:
"Survey (Grid) Delay and HeadingHold Upgrades"
"Survey (Grid).copter. Change waypoint delay."
As usual, these messages are so terse that it is not clear what they mean exactly, but my guess was that you fixed the bug I reported earlier that even if the user entered a value for the waypoint delay in the Grid dialog (with a multicopter), the delay value for each waypoint was always zero in the actual mission. I just now tested this in version 1.3.10, and the behavior is just as it was in the previous version, i.e. not fixed. To what do the above lines in the release notes refer, then?
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the MP 1.3.10 release notes entries for “Survey (Grid) Delay and HeadingHold Upgrades” and “Survey (Grid).copter. Change waypoint delay.” Reproduce the reported behavior in the Survey (Grid) dialog with a multicopter, then determine whether the entries refer to this bug; done means the release-note meaning is established and the waypoint delay behavior is corrected or clearly documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100