Open Marcel510 opened 5 years ago
Analysis:
~Currently~ In 6.10, the exithold
method is basically "if currently in a holding pattern, exit it":
However, absent an explicit command to cancel holding, exithold
is instead implied by various other commands. The intended behavior is:
Here is proceedDirect
:
L770 and L771 are in wrong order, so dct TIMBA
results in:
~Before I PR this -- should I make it a bugfix or hotfix?~
From 6.11 onwards changes in cancel hold code behavior slightly complicates things (see #1333)
bugfix imo. obviously defer to someone more experienced but this has been a known issue for a while, it's important but not absolutely critical
Well, it's either a hotfix for 6.10.x, or subsumed by #1333 in 6.11 due to changes by #1160.
bugfix for 6.11 (which we ideally release in 6.12)
When an aircraft has holding instructions (though in this case, its implied by the STAR rather than being explicitly issued), and they are cleared direct to the holding fix, we would have to reiterate the hold instructions. So the behavior is a pretty standard one. But I can see your point. More thought is needed to see what we should do here... 🤔
Issue Description
Some STARs have holds built hin for example: EGKK TIMBA4B
which works perfectly: but as soon as you give the aircraft a direct to the holding fix the holding is omitted:
Steps to reproduce