Closed GeekPro101 closed 2 years ago
Won't have time to finish this AIRAC (2022/02) + want to get down to 0 PRs but WIP can be found in issue-4110
from @zyriantdt-x
The London ones have never worked. I tried a few times before but nothing seemed to get the prediction to behave how I wanted it to. Maybe I didn't try hard enough 🤷🏼♂️ but it would be good to have it working!
I've had a thought with this regarding London agreements if you haven't tried it already: add guest ownership to LFRR Low for JJ CTR?
@danielbutton i've got a free evening on Thurs so I was going to try that then but if you have some spare time + want to test some things out you can commit some stuff to the branch and use the compiler to generate an SF
@danielbutton @GeekPro101
I've had a thought with this regarding London agreements if you haven't tried it already: add guest ownership to LFRR Low for JJ CTR?
As long as the COPX use a 'FIX', then EuroScope should fix the climb profile to remain within JJ airspace. What would be useful though is to add guest ownership to LFRR that allows S6/S21 to climb traffic after the Jersey RFC Line. This may also resolve any COPX display issues for northbounds, as EuroScope sees that S6/S21 is 'allowed' to keep that traffic through LFRR's airspace.
We should also take this opportunity to change London AC Worthing -> London S21 in this file: Agreements/Airport/JJ_S.txt
Final suggestion from me to try... should probably look to expand the LFRR Low sector so that it actually covers the southern border! 😄
The London -> JJ CTR agreements are all currently set up as FIR_COPX, would that make a difference?
The London -> JJ CTR agreements are all currently set up as FIR_COPX, would that make a difference?
@danielbutton nope, that's effectively just a label rather than anything impacting functionality
What is the bug?
For EGJJ_C_APP (ORTAC) and EGJJ_S_APP (SKERY) the handoffs to LFRR Low do not work Also the London ones
What is the expected functionality?
(what should it be doing/ look like?) it should work
How can it be reproduced?
(if not obvious) Logging on as relevant callsigns with LFRR_CTR adjacent
Additional information
(do you have an idea of what is causing the bug, etc.) Some dummy sectors + guest ownership for LFRR