SID selection tends to delete part of route in FP

[Jonas Eberle]

Lets take this FP:

SOBRA Y180 BITBU Y181 MAKIK UY181 DEMUL UM624 BUB UL608 LOGAN BIG1E.LOGAN

 

If I select a SID on it, it changes the FP to:

SOBRA1S/18 SOBRABITBU <>

 

The SOBRA Y180 BITBU part contained 4 waypoints that are correctly shown in the waypoint/airway-box in the FP-dialog (all as "OK", no connection errors).

 

The .ESE part:

SID:EDDF:18:SOBRA1S:DF197 DF201 DONAB SOBRA

 

This is reproducable on all "SOBRA Y180 BITBU" departures.

 

 

If we have this FP, which also happens to be there:

SOBRA BITBU Y181 MAKIK UY181 DEMUL UM624 BUB UL608 LOGAN

->

SOBRA1S/18 SOBRA BITBUMAKIK UY181 <>

 

EDIT: some more

ULKIG Y180 RUDOT Q762 <>

-> ULKIG4U/18 ULKIGRUDOT Q762 <>

and ULKIG4U/18 ULKIG Y180 RUDOT Q762 <>

-> ULKIG4U/18 ULKIGRUDOT Q762 <>

 

I happened to write that now, even though it was persistent since I use EuroScope (3.0a)

[Todor Atanasov 878664]

Jonas, can we have a look at your ESE file to test it. Is the Y180 in the ICAO_Airways.txt file?

[Jonas Eberle]

The AIRWAY.txt contains Y180 and EuroScope shows the connection SOBRA Y180 BITBU correctly resolved to 4 points.

 

Thanks for having a look: http://idisk.mac.com/janniswiese-Public/VATSIM/EuroScope-ESE/stable/EuroScope.zip

 

The SIDs where I encountered the problem are SOBRA1S, SOBRA3L and ULKIG4U (all from EDDF).

[Todor Atanasov 878664]

Hi Jonas,

 

First, your ese file takes 10-15 sec to load or to open any menu connected with the reading of the file....try to make some smaller files not one big.

 

Second I tried all the FPs you mentioned and everything is working very good. I tried changing Rwys and then [Mod - Happy Thoughts]igning new SIDs and ES doesn't cut anything from the FP except to add the SID/Rwy.

 

Here is the shot

 

 

Try to reload all files in your ASR.

[Jonas Eberle]

Thanks for looking Todor,

I have this even in a newly configured EuroScope instance and from know it from another controller at Frankfurt. I will ask around if others do not have the problem.

[Stephan Boerner 945550]

First, your ese file takes 10-15 sec to load or to open any menu connected with the reading of the file....try to make some smaller files not one big.

Really, 10 - 15 secs? Then there must be something wrong on your side. It's about 2 secs for me to open the Display Dialog for example.

[Jonas Eberle]

I asked around a bit and found 3 others with that problem, all on these departures. But I have to add: Those (many ) that are using the new beta do not experience the problem, so we can lean back I think.

 

One more:

 

SOBRA Y180 BITBU Y181 MAKIK UY181 DEMUL UM624 BUB UL608 LOGAN

-> SOBRA1S/18 SOBRABITBUMAKIKDEMUL UM624 BUB UL608 LOGAN

 

It is reproducable on these routes.

[Hans Utne 813128]

Todor,

 

Again, I have to ask, are you using the Beta when you test complaints or possible problems, or the official release version?

[Jonas Eberle]

Hans, I use the 3.0a and will only report problems regarding the released version in this forum.

 

EDIT: sorry, I misunderstood that.

[Todor Atanasov 878664]

LOL I missed that one, Hans I do he test both on the v3.0a and on the latest beta. In both I got the same result.