Develop
Ticket #1646 (closed defect: fixed)
Auto MC behaviour
| Reported by: | alex8735 | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | XCSoar 6.2 |
| Component: | Other | Version: | 6.2.3 |
| Keywords: | Cc: |
Description
I did some testing with auto MC using condor and got some unexpected results.
- When sinking below final glide auto MC does not ajust below a value of MC 0.4. I would expect it to set to MC 0. Safety MC is set to 0 and auto MC is set to final glide. Is this a bug or a feature? If it is a feature please explain.
- When setting the destination for final glide from a reachable waypoint to a non reachable waypoint auto MC is not corrected to a lower value but sticks to the old value. I would suggest switching MC to 0 in this case.
Change History
comment:2 in reply to: ↑ 1 Changed 17 months ago by alex8735
Since auto MC was set to final glide and not to both (including trending average climb) I would expect no inclusion of the calculated value since I have turned it off? Is my understanding of trending average climb being the same as the calculated default MC value wrong?
I know this is only a low priority issue with room for different interpretations and an easy workaround by setting MC manually but I thought it may be worth opening a ticket anyway to give some feedback.
comment:3 Changed 17 months ago by max
Ah, you did not specify your AutoMC setting previously!
What is your safety MC setting?
Note: See
TracTickets for help on using
tickets.
What was the value determined by AutoMC before you entered final glide? When going below final glide, the "final glide automc" algorithm is disabled, and it will be back to using the "normal" calculated values for cruise/climb.