TopSky plugin 2.4 beta 4

[Juha Holopainen]

Beta 4 changes:

• MTCD/SAP CTD issue introduced in beta 3 fixed
• Updated maps data file syntax (new "area" option to "active" line to activate the map based on specified area activity

 

Edited March 24, 2022 by Juha Holopainen

[Juha Holopainen]

For the Finnish setup, the attached file provides some files to set up the new features. No changes from beta 3.

With the new default color scheme since beta 3, please have a look once again - if you haven't already, please do now - at the sector package guide document section about selecting a suitable color scheme, and possibly creating different profiles for each scheme.

To summarize, there are three color schemes:

1. EFIN - used to be very close to the EFHK colors but with the new colors this is very, very grey
2. EFHK - greenish grey active sector color (no change)
3. Other - blueish grey active sector color (no change)

EFIN is the default if nothing is done as the Symbols.txt file the default profile file points to is a copy of Symbols_EFIN.txt

As the color schemes are now more and more different, and as the plugin automatically switches its own colors based on the login callsign, it's getting more and more important to use the correct Symbols settings file for EuroScope so that the EuroScope colors are a match with the plugin ones. The easiest way to get good results is probably to first set up the profile file as desired, and then make two copies out of it, and edit the files to point to the correct symbols settings files.

 

Edited February 15, 2022 by Juha Holopainen

[Jonathan Fong (1308253)]

BIRD NOTAMs look to all be downloading properly now. Thank you so much!

[Jakob Arne Bronstad (1000634)]

ES CTD when trying to unload topsky.dll

EuroScope.exe.17532.dmp

[Juha Holopainen]

The plugin has already been unloaded at that point, so there's nothing to see. The good news is that I can unload the current development version just fine so whatever it is, it's possibly fixed. On the other hand, if it's not and for some reason I just can't replicate it, the ability to unload the plugin is not going to be very high in the priority list.

[Jonas Kuster (1158939)]

Does the new ICAO format options to “use equipment codes” preserve the ICAO flight plan item 10 content in the aircraft type field of the flight plan when the flight paln is changed via the TopSky flight plan mask (it currently doesn't)?

[Juha Holopainen]

That setting should have no effect on flight plan modifications. Can you provide exact steps to reproduce the issue? I tried a couple of different modifications to a flight plan but could not get an unwanted change to appear in that field.

[Jonas Kuster (1158939)]

Identified this issue when supporting another controller regarding an issue with another plugin.

So, take a flight plan that has in the aircraft type field "A319/M-SDE3FGIJ1KRWXY/LB1". Then open the flight plan with TopSky. Do any modification. Save the modification. The aircraft type is reset to something like "A319". I believe the NAV and SUR equipment is stored in a separate way for TopSky. But it's lost for any other plugin or a next controller not working with TopSky.

[Juha Holopainen]

Did the following tests with exactly that string as the starting point, flight plan state after applying each change verified from both the plugin's Flight Plan Window and the EuroScope's Flight Plan dialog:

1) change route and apply: no change in flight plan type string

2) change remarks and apply: no change in flight plan type string

3) change equip field and apply: changes to flight plan type string applied as expected

4) change sur field and apply: changes to flight plan type string applied as expected

5) clear sur field and apply: sur field automatically set to "C" (expected behavior), flight plan type string updated correctly

6) change destination and apply: no change in flight plan type string

I cannot get it to produce any unwanted changes.

Edited November 12, 2021 by Juha Holopainen

[Jonas Kuster (1158939)]

Hm, ok, then some of our neighbors are maybe using old versions of the plugins. I often get aircraft transfered with an assigned code 1000 that are not eligible (due to missing NAV/SUR equipment codes). But at some point, they have had to be, why would code 1000 be assigned otherwise?

Thanks for investigating. It seems at least that the issue is not present in this current version.