Jump to content

STAR selection logic


Recommended Posts

At present, when a flight plan route string includes a STAR (with no runway specified) - for example, ...LOGAN LAM3A - and there is more than one runway available on this STAR, EuroScope will select the first STAR/runway entry specified in the sector file, regardless of the active runway.

 

STAR:EGLL:27R:LAM3A:LOGAN TRIPO SABER BRASO LAM FI27R RW27R
STAR:EGLL:27L:LAM3A:LOGAN TRIPO SABER BRASO LAM FI27L RW27L
STAR:EGLL:09R:LAM3A:LOGAN TRIPO SABER BRASO LAM FI09R RW09R
STAR:EGLL:09L:LAM3A:LOGAN TRIPO SABER BRASO LAM FI09L RW09L

 

So, EuroScope will always select LAM3A landing runway 27R for any route string that ends in LAM3A, regardless of the active runway for arrivals in EuroScope.

 

Would it be possible for EuroScope to cross check the active arrival runway(s) with STAR entries, and to, in the first instance, allocate the arrival runway and STAR for which matches that of the runways in use?

 

(Thanks Gergely!)

ATC Examiner, VATSIM UK

No nonsense controlling Twitch - HazControl ✈️

@HVatsim

Link to post
Share on other sites

I don’t think you’ve quite understood my explanation, perhaps because in the UK we have the same STAR name for ALL runways?

 

So in the case where the WILLO3B for 26L and 08R are both in the ese file, and the pilot has put WILLO3B in their flight plan route string, EuroScope will select WILLO3B 26L if it comes before the entry for 08R in the ese. This is done regardless of the runway in use according to the runway dialog. So it’s fine when the active runway is 26L but not when 08R.

 

Some more useful background to the perhaps specific problem to the UK, but logic that would not be unwelcome in EuroScope in any case: https://github.com/VATSIM-UK/UK-Sector-File/commit/0846660eca6fd136ed87e0830f000e6c5b6f7962

ATC Examiner, VATSIM UK

No nonsense controlling Twitch - HazControl ✈️

@HVatsim

Link to post
Share on other sites
I don’t think you’ve quite understood my explanation, perhaps because in the UK we have the same STAR name for ALL runways?

 

So in the case where the WILLO3B for 26L and 08R are both in the ese file, and the pilot has put WILLO3B in their flight plan route string, EuroScope will select WILLO3B 26L if it comes before the entry for 08R in the ese. This is done regardless of the runway in use according to the runway dialog. So it’s fine when the active runway is 26L but not when 08R.

 

Some more useful background to the perhaps specific problem to the UK, but logic that would not be unwelcome in EuroScope in any case: https://github.com/VATSIM-UK/UK-Sector-File/commit/0846660eca6fd136ed87e0830f000e6c5b6f7962

 

If you activate the runway in ES then the problem should be solved AFAIU.

 

If this issue still remains, then the best way to solve this problem would be by adding a letter code with STAR in your ESE file.

 

For instance:

STAR:EGLL:27R:LAM3Ax27R:LOGAN TRIPO SABER BRASO LAM FI27R RW27R
STAR:EGLL:09L:LAM3Ax09L:LOGAN TRIPO SABER BRASO LAM FI09L RW09L

 

Hope this helps.

Link to post
Share on other sites

Activate the runway? I'm not sure I understand. I would always have an active runway set...?

 

Thanks for the suggestion, though I would say this isn't about finding an urgent solution. It's just a little hiccup in the logic of EuroScope that I'm suggesting could be addressed - we're just about managing to manually change the runway each time so we can continue doing that for now!

ATC Examiner, VATSIM UK

No nonsense controlling Twitch - HazControl ✈️

@HVatsim

Link to post
Share on other sites
  • 1 month later...

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...