{SI} specific settings not working

Jannik Vogel (1432304)

The manual states: "Sections can also start with a position ID enclosed in curly brackets – a section starting with “{D}” will be read if the current position ID is “D”. Partial matches are not supported".
However in v2.5 this is not working as intended. Filtering by login (square brackets) does work as intended.

Juha Holopainen (839337)

Just tested and it appears to be working so this may be a setup issue on your side - such as another matching section later on that changes the setting(s) again.

Jannik Vogel (1432304)

Indeed, wasn't aware. Moving the {SI} matchings to the very end of the TopskySettings fixes the issue. Thanks for the help!

Ricardo Sousa (1110850)

Actually, all { } settings are not getting applied at first load, similar to the Ground Radar issue.

[LPPT_]
Window_CARD_View_Notif=1
Window_CARD_View_Future=0
Label_PEL_Default=0000
Label_WTC_Default=0000
Label_XFL_Default=0000
List_TfcMgmt1_Via=MAZUK,ORTUG,EKLID,DEKKI
List_TfcMgmt2_Via=CASLU,ESP

{ARRLI}
Setup_LoadMap=TWRCAS\ext_cntrline_35
Setup_Informed=LPPT,LPCS,LPAR,LPMT:*:*:1

Loading as LPPT_F_APP for example, whose LFUNC is ARRLI, loads all the [ ] settings, but the TWRCAS\ext_cntrline_35 is only loaded after manually reloading settings from the STS menu.

Juha Holopainen (839337)

Sometimes EuroScope does seem to take its time assigning the correct SI after a login callsign change. If it is still reporting an "unidentified station" SI (a numeric value) by the time the plugin code gets around to checking for callsign/SI specific settings, the wrong SI will be used. I'll see what can be done about it.