Bohdan Bessonov Posted June 25, 2015 at 03:35 PM Posted June 25, 2015 at 03:35 PM Okay, we have a situation. CTR controller (UKBV whole center) UKBV_CTR and me, UKBB_APP (dep+arr UKBB) And we have a traffic - AUI123 that goes from SLV to BBW101, then full transition.See the picture below: If CTR would like to direct to BB668 or BB665, he can do shortcut without my accept. But only for fixes BB638, BB636, BB634, BB632 and BB630 he needs my accept. WHY? Sectors are properly defined (as you see) and BB668/665 are in my sector. Why CTR don't need my accept? Thanks Bohdan Bessonov ACCUA03 ATC Manager Link to comment Share on other sites More sharing options...
Jonas Kuster Posted June 25, 2015 at 10:38 PM Posted June 25, 2015 at 10:38 PM From my experience, this has changed with ES V3.2 compared to 3.1d. Now, the partner for coordination has to be selected explicitly. This mean, even when the correct following controller is shown correctly to CTR (in tag or list), it has first to be reselected (changes color) and then a coordination request should be initiated. As CTR, you can see while selecting fix and/or altitude if a coordination request will be initiated. Fixes and altitudes in the dropdown will then be followed by the position id (of the controller to initiate a handoff with) in brackets. I don't know if this change in behaviour related to the earlier version is a bug or a feature. 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...
Bohdan Bessonov Posted June 26, 2015 at 12:36 AM Author Posted June 26, 2015 at 12:36 AM It's abnormal that CTR needs to reselect next controller. Without reselect CTR has BB665, BB664 BB662... and only BB638(TC4) BB636 (TC4) etc... We will try tomorrow and answer here. p.s.Maybe Csernak will answer: bug or feature is this? Bohdan Bessonov ACCUA03 ATC Manager Link to comment Share on other sites More sharing options...
Panagiotis Konstantinidis Posted June 26, 2015 at 09:20 AM Posted June 26, 2015 at 09:20 AM Also, make sure you have requested the COPX altitude before requesting the COPX Point. If the current altitude of the aircraft is higher than the upper vertical limit of the next sector, COPX won't work Panagiotis Konstantinidis ACCGR11, HvACC Deputy Director Airport Briefing | Air Traffic Overview | Euroscope Guide | Euroscope Sector Files Link to comment Share on other sites More sharing options...
Bohdan Bessonov Posted June 26, 2015 at 01:38 PM Author Posted June 26, 2015 at 01:38 PM CTR set a40 before coord. Nothing changed. (my sector is 1000-9000 feet) UPD. Worked if CTR choose next atc manually Bohdan Bessonov ACCUA03 ATC Manager Link to comment Share on other sites More sharing options...
Pavel Brodsky Posted June 27, 2015 at 09:50 AM Posted June 27, 2015 at 09:50 AM Any update why the ATC needs to manually select next controller ID before COPX works? Happens to me also quite randomly, sometimes it works without preselecting, sometimes not, quite annoying. Pavel Pavel Brodsky VACC-CZ Link to comment Share on other sites More sharing options...
Bohdan Bessonov Posted June 27, 2015 at 06:16 PM Author Posted June 27, 2015 at 06:16 PM I don't know what's going on with ES? Why it has no route? only to BO (he p[Mod - Happy Thoughts]ed BO 10 minutes earlier) WTF??? AIrac 1507 sure installed p.s. Maybe revert to pure ES 3.2? without latest patch (2014 year), it's so buggy, or wtf? Thx for help... Bohdan Bessonov ACCUA03 ATC Manager Link to comment Share on other sites More sharing options...
Bohdan Bessonov Posted June 30, 2015 at 09:21 PM Author Posted June 30, 2015 at 09:21 PM Any help up Bohdan Bessonov ACCUA03 ATC Manager Link to comment Share on other sites More sharing options...
Jonas Kuster Posted July 1, 2015 at 07:08 AM Posted July 1, 2015 at 07:08 AM Hi Bogdan Keep calm. It will most probably be a problem with the data from the sct/ese file. As I'm not familiar with the region and airport, let me ask: What STAR procedure did you define? Possible that ES has detected a STAR from BO which is incomplete. There are 2 ways to display a route, once with the expected time (what your picture shows obviously) and once with the calculated altitude. Is there a difference between? You said the AIRAC is up to date. Which files does that cover? So which files have been updated? I see also the aircraft isn't appearing in the list also show in the screenshot, where the STAR should be visible. Did you check that the airport settings have been set correctly? Route drawing is sometimes messed up when a direct has been given before and the p[Mod - Happy Thoughts]ing of this waypoint hasn't been registered by ES. If you cleared a direct before, drop it again. 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...
Kirk Christie Posted July 1, 2015 at 09:15 AM Posted July 1, 2015 at 09:15 AM Route drawing has nothing to do with the sector files or the sector file cycle. Its all in the airway.txt file in your euroscope folder, this needs to be updated with data from navigraph. Kirk Christie - VATPAC C3 VATPAC Undercover ATC Agent Worldflight Perth 737-800 Crew Member Link to comment Share on other sites More sharing options...
Bohdan Bessonov Posted July 1, 2015 at 05:49 PM Author Posted July 1, 2015 at 05:49 PM Its all in the airway.txt file in your euroscope folder, this needs to be updated with data from navigraph. All files from FSNavigator data copied and replaced to Docomeents. And, these NDBs also were in old AIRAC + are here in new AIRAC Bohdan Bessonov ACCUA03 ATC Manager Link to comment Share on other sites More sharing options...
Gergely Csernak Posted July 21, 2015 at 06:44 PM Posted July 21, 2015 at 06:44 PM Sorry about the real and possible bugs Be sure that next controller selection is three dimensional so the calculated profile is at least as important as the route itself. What is changed between 3.1d and 3.2 is that in case of direct the profile is not a straight line anymore, but a highest possible profile. Because of that the expected altitude is higher than it was before. That may cause situations like this. Please note Jonas' second question. Use the "Toggle route prediction points draw" function. That will show the estimated altitude as well as the selected sector. You will see why ES thinks you do not need a coordination. Try adding some altitude restriction for the STAR to force the profile a bit lower. Even so it still may be a bug ... Gergely. EuroScope developer Link to comment Share on other sites More sharing options...
Jonas Kuster Posted July 22, 2015 at 07:18 PM Posted July 22, 2015 at 07:18 PM Try adding some altitude restriction for the STAR to force the profile a bit lower.How can this be done? 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...
Gergely Csernak Posted July 26, 2015 at 05:47 PM Posted July 26, 2015 at 05:47 PM Well, it seems that I wrongly remembered that you can define COPX points four yourself along the star. But that is not the way. It seems that the only thing you may do now is to define a coordination altitude as well before the point. That will change the profile calculation. Gergely. EuroScope developer Link to comment Share on other sites More sharing options...
Recommended Posts