3.2.1.23 issue with US SID/STAR

[Philip Harris 0]

Glad to see the fix in 3.2.1.23, however further to the active runways, can ES also take notice of the order of the runways in the ESE file please?

 

For example, KATL

 

SID:KATL:09L:VRSTY2:GRITZ MYZMN TROFY VRSTY MCN

SID:KATL:27R:VRSTY2:SLAWW RIGGZ RIVTT VRSTY MCN

SID:KATL:26R:VRSTY2:SNUFY SLAWW RIGGZ RIVTT VRSTY MCN

SID:KATL:26L:VRSTY2:SNUFY SLAWW RIGGZ RIVTT VRSTY MCN

SID:KATL:27L:VRSTY2:SLAWW RIGGZ RIVTT VRSTY MCN

SID:KATL:28:VRSTY2:WLSON ZALLE VRSTY MCN

SID:KATL:08L:VRSTY2:SKNNR GRITZ MYZMN TROFY VRSTY MCN

SID:KATL:08R:VRSTY2:SKNNR GRITZ MYZMN TROFY VRSTY MCN

SID:KATL:09R:VRSTY2:GRITZ MYZMN TROFY VRSTY MCN

SID:KATL:10:VRSTY2:GRITZ MYZMN TROFY VRSTY MCN

 

In west ops normally this SID will depart from 27R, but ES is selecting 26L as I guess its sorting the SID's alphabetically.

[Bjoern Helge Smaavollan 0]

As per the ES wiki for ESE files:

 

The lines priority is from top to bottom. The topmost line has most priority. The first line that completes all conditions will be chosen as the correct routing.

 

If a pilot has filed a FPL with the SID points in his plan it will be selected.

 

Also if you set 27R as the active departure runway in ES that one will be selcted as long as 26L is not set as departure rwy

[Philip Harris 0]

The problem at airports like KATL is both 26L and 27R are departure runways. But certain SIDS depart 26R and others 27L

 

Until this beta, the order of SIDS in the ESE file was observed.

[Philip Harris 0]

And I see your quote about priority in the ESE file. In that case that isn’t working anymore then when you have multiple departure runways. It used to work