Jonas Kuster Posted June 28, 2021 at 03:58 PM Posted June 28, 2021 at 03:58 PM I might be missing something quite essential, but I remember times when there were possibilities to define a COPX beyond the own sector boundary and I was able to provide a direct to any flight up to this point. Now this point, despite the intended COPX rule is captured, is marked already to be subject to coordination (marked with the ID of the next sectors controller). I would expect this point (as it is the agreed COPX) NOT to be subject to coordination as proposed by ES. Am I wrong? How do you manage to implement COPX outside of the transferring sector? PS: I'm aware of the option "Allow direct beyond COPX point", but this is just to mute any coordination that is not in your own sector. I would want to mute such coordination until and including the COPX. Any ideas? 1 Jonas Kuster Network Supervisor Leader Operation vACC Switzerland | vacc.ch @vaccswitzerland GNG Support Team | gng.aero-nav.com ES Plugin Developer | CCAMS Link to comment Share on other sites More sharing options...
Matisse VanWezer Posted June 29, 2021 at 10:49 AM Posted June 29, 2021 at 10:49 AM Until someone has an answer, you can always right click the COPX point in the direct menu to avoid coordination (with ES beta). Not sure about individual points. Streaming Brussels Control since 2018 on MatisseRAdar - Twitch to create time lapses on YouTube and TikTok Link to comment Share on other sites More sharing options...
Jonas Kuster Posted June 29, 2021 at 05:46 PM Author Posted June 29, 2021 at 05:46 PM 6 hours ago, Matisse VanWezer 1385143 said: Until someone has an answer, you can always right click the COPX point in the direct menu to avoid coordination (with ES beta). Not sure about individual points. I'm aware, thanks. I need to assume this has been broken at some time during development. Because otherwise there wouldn't be a reason for an option "Allow direct beyond COPX point". This at least to me suggests that otherwise direct up to the COPX are allowed. Jonas Kuster Network Supervisor Leader Operation vACC Switzerland | vacc.ch @vaccswitzerland GNG Support Team | gng.aero-nav.com ES Plugin Developer | CCAMS Link to comment Share on other sites More sharing options...
Matisse VanWezer Posted June 30, 2021 at 02:35 PM Posted June 30, 2021 at 02:35 PM It would indeed be nice to see it return. Or else, be able to define a set of points to which no coordination is required even though they are outside the controller's airspace (just like in real life). Streaming Brussels Control since 2018 on MatisseRAdar - Twitch to create time lapses on YouTube and TikTok Link to comment Share on other sites More sharing options...
Mateusz Zymla Posted July 1, 2021 at 09:11 AM Posted July 1, 2021 at 09:11 AM Open scratchpad, put name, hit enter. DCT will be there without coordination. Mateusz Zymla - 1131338 VATSIMer since 2009, IRL pilot rated. Link to comment Share on other sites More sharing options...
Jonas Kuster Posted July 1, 2021 at 06:25 PM Author Posted July 1, 2021 at 06:25 PM 9 hours ago, Mateusz Zymla said: Open scratchpad, put name, hit enter. DCT will be there without coordination. Well, that's the same as right click in the COPX list. But I would like to have an option to correctly identify the waypoints where coordination is needed and where it is not. Jonas Kuster Network Supervisor Leader Operation vACC Switzerland | vacc.ch @vaccswitzerland GNG Support Team | gng.aero-nav.com ES Plugin Developer | CCAMS Link to comment Share on other sites More sharing options...
Bernardo Reis Posted November 26, 2022 at 12:01 PM Posted November 26, 2022 at 12:01 PM We found the same problem recently, the lack of ability to define a COP beyond sector AoR. Link to comment Share on other sites More sharing options...
Recommended Posts