Euroscope deletes initial fix on runway change

Support Controller Software
1

When developing a plugin that suggests and optionally assigns appropriate SIDs to assist controllers, we noticed that when changing the runway for a flight plan (via the entry in departure list), not just the SID would disappear from the flight plan route text, but the entire initial fix too.

Eventually, via much breakpointing, I came to this minimal case:

  1. Have a flight plan with a route string similar to this: EBBR/25R CIV5K CIV N782 FIX , the airway and fix are irrelevant.
    The crucial bit here is that we include EBBR/25R AND CIV5K. The plugin uses this to force a runway and SID, lacking another option for SID. If either is missing, the bug does not trigger
  2. Change the runway
  3. Observe the route now looks something like EBBR/07R N782 FIX, without the plugin being triggered at all.

This can be relatively easily demonstrated by manipulating the route field manually in a simulated session.

I am currently working around this by limiting what our plugin puts in the route field, but it can absolutely happen without any plugins.

Would love input @904331

2

If this proves tricky to fix, a way to change SID and / or runway assignment without messing with the bare route text would be neat.

3

While I don’t know what might be causing, let alone could resolve the problem, what you are trying to do with your plugin seems to be pretty similar - if not identical - to what has been developed here in VATGER with our vSID plugin, which does not have this issue. Maybe the vSID plugin could also be a suitable solution for your usecase and save you some development time?

4

I’ve looked at it in the past, for various reasons decided not to go with it. I see you insert data as CIV5K/25R CIV N782, which indeed would not trigger the bug. I didn’t know that was a possible way of setting the SID and runway, will test if it works for us as a workaround.

Considering this issue is present even without any plugins though, I’d still like to see it fixed. Losing part of a flight plan is nasty

5

The way VATGER handles SID/runway notation with the format SID/RWY might indeed be a good workaround.

6

Indeed, I have started using this notation and it does work around the issue. It doesn’t fully negate it, as when selecting a runway in the euroscope drop-down, it does use the ICAO/RWY notation, so naively leaving that will result in triggering this bug again…

Less of an immediate issue now, still nasty that it exists imo