TopSky plugin 2.5 beta 15

Domonkos Ujhelyi (1623074)

Hey, I've managed to find a bug, if an aircraft gets removed by Euroscope's built-in altitude filter while the level band highlight is active for that aircraft, all callsigns stay red.
Thanks,
Domonkos

Juha Holopainen (839337)

Domonkos Ujhelyi (1623074) Hey, I've managed to find a bug, if an aircraft gets removed by Euroscope's built-in altitude filter while the level band highlight is active for that aircraft, all callsigns stay red.

I'll implement a timer to automatically cancel the highlight after a couple of seconds if the label is no longer visible. Until then, the stuck highlight can be removed by activating it for a short time from any other label.

Hongye Rudi Zhang (1326158) I can't troubleshoot the area activation issue very well without knowing everything you're feeding the plugin with. The complete remote area activation data file the plugin is downloading, the area definition for the area in question (that one I do know unless you've made changes to it after posting it above), the NOTAM that should be activating the area, any plugin settings related to areas/NOTAMs/remote activation/anything else you think might be relevant you've changed from the default settings and the exact sequence of steps you're doing from the time EuroScope launches until the issue is seen (such as opening plugin windows, activating settings, etc.).

Hannes Altmann (1395737)

Juha Holopainen (839337) I've so far had zero feedback on how the remote activation feature works, or if it works at all. If it works fine or at least for the most part, the setting will be published. If some parts work ok, it'll remain an experimental feature with the setting remaining unpublished. In case there are major issues with it, it'll be removed completely from the release build and reintroduced in some later version.

The feature itself works great. I also didn't know that auto-activation for remote areas was available as a settings option. However, I noticed that I cannot edit or activate areas in the Topsky AMS/TSA window manually when the remote option is active.

George Daniel Schoonraad (1768227)

Hello @Juha Holopainen (839337),

Is it possible for you to add more options to the Weather Radar URLs? We at VATSSA are currently looking into implementing a form of weather radar into the sector files, but unfortunately, RainViewer's API doesn't cover Africa.

We found another free API from OpenWeatherMaps, which provides a weather radar precipitation layer that covers all of Africa. However, the URL format is a bit different than RainViewer's API, and as such, we cannot use OpenWeatherMaps' API currectly:

https://tile.openweathermap.org/map/precipitation_new/{z}/{x}/{y}.png?appid={API key}

This differs from RainViewer's format. Is it possible for you to adjust the settings so we can use this API?

From what I can tell, the data provided from the API is formatted very similarly to RainViewer's API.

We would really appreciate it!

Regards,
George
VATSSA Staff

Bostjan Laba (1190497)

Juha,

I've added polygons to MSAW file. Lines/Polygons are displayed properly but altitudes numbers are not displayed "within" each polygon:

Navigraph sectors:

Lines in msaw:
//LJLJ
//LJLJ Sector 1
P:17:N046.29.21.900:E014.00.10.000:N046.29.37.300:E014.02.35.900:N046.26.18.700:E014.10.23.900:N046.26.59.500:E014.26.15.300:N046.25.44.400:E014.31.11.300:N046.26.12.800:E014.35.46.100:N046.27.17.000:E014.40.35.800:N046.22.59.400:E014.52.06.000:N046.17.44.700:E014.48.20.200:N046.15.31.200:E014.42.16.500:N046.17.23.100:E014.34.56.000:N046.16.21.800:E014.32.41.300:N046.17.29.400:E014.29.14.700:N046.19.21.100:E014.27.23.400:N046.20.52.800:E014.21.31.100:N046.19.12.300:E014.14.10.000:N046.16.56.400:E014.05.05.600:10500

//LJLJ Sector 2
P:8:N046.22.59.400:E014.52.06.000:N046.19.48.900:E015.00.32.400:N046.17.32.800:E014.58.33.000:N046.13.27.800:E014.36.13.700:N046.13.01.700:E014.31.49.700:N046.14.28.300:E014.27.26.700:N046.15.31.200:E014.42.16.500:N046.17.44.700:E014.48.20.200:8000

//LJLJ Sector 3
P:10:N046.15.31.200:E014.42.16.500:N046.14.28.300:E014.27.26.700:N046.16.33.600:E014.21.21.300:N046.18.05.100:E014.16.49.000:N046.19.12.300:E014.14.10.000:N046.20.52.800:E014.21.31.100:N046.19.21.100:E014.27.23.400:N046.17.29.400:E014.29.14.700:N046.16.21.800:E014.32.41.300:N046.17.23.100:E014.34.56.000:9000

//LJLJ Sector 4
P:7:N046.19.12.300:E014.14.10.000:N046.16.56.400:E014.05.05.600:N046.06.07.100:E014.09.22.400:N046.05.56.900:E014.15.47.000:N046.10.51.300:E014.15.24.900:N046.14.09.600:E014.13.48.700:N046.18.05.100:E014.16.49.000:7000

//LJLJ Sector 5
P:4:N045.54.56.800:E014.24.33.200:N045.57.06.100:E014.25.37.700:N045.57.06.100:E014.27.48.800:N045.54.56.800:E014.32.05.100:5400

//LJLJ Sector 6
P:23:N046.06.07.100:E014.09.22.400:N045.54.54.700:E014.13.41.400:N045.54.56.800:E014.24.33.200:N045.57.06.100:E014.25.37.700:N045.57.06.100:E014.27.48.800:N045.54.56.800:E014.32.05.100:N045.54.57.200:E015.00.59.700:N045.59.37.900:E015.03.55.000:N046.01.20.000:E014.58.52.300:N046.10.58.700:E014.52.39.400:N046.11.04.100:E014.48.39.100:N046.11.56.800:E014.39.37.800:N046.09.38.500:E014.46.24.100:N046.01.49.600:E014.52.55.700:N045.56.50.800:E014.48.07.500:N046.00.23.600:E014.23.49.000:N046.07.46.900:E014.24.54.100:N046.13.09.200:E014.18.45.700:N046.16.33.600:E014.21.21.300:N046.18.05.100:E014.16.49.000:N046.14.09.600:E014.13.48.700:N046.10.51.300:E014.15.24.900:N046.05.56.900:E014.15.47.000:5000

//LJLJ Sector 7
P:10:N046.13.01.700:E014.31.49.700:N046.13.27.800:E014.36.13.700:N046.11.56.800:E014.39.37.800:N046.09.38.500:E014.46.24.100:N046.01.49.600:E014.52.55.700:N045.56.50.800:E014.48.07.500:N046.00.23.600:E014.23.49.000:N046.07.46.900:E014.24.54.100:N046.13.09.200:E014.18.45.700:N046.16.33.600:E014.21.21.300:4000

//LJLJ Sector 8
P:10:N045.59.37.900:E015.03.55.000:N046.04.57.800:E015.07.15.000:N046.09.20.100:E015.06.07.700:N046.14.33.000:E014.51.35.200:N046.15.01.100:E014.44.45.000:N046.13.27.800:E014.36.13.700:N046.11.56.800:E014.39.37.800:N046.11.04.100:E014.48.39.100:N046.10.58.700:E014.52.39.400:N046.01.20.000:E014.58.52.300:6000

//LJLJ Sector 9
P:6:N046.09.20.100:E015.06.07.700:N046.14.33.000:E014.51.35.200:N046.15.01.100:E014.44.45.000:N046.17.32.800:E014.58.33.000:N046.19.48.900:E015.00.32.400:N046.18.40.800:E015.03.42.400:7000

//LJLJ Sector 10
P:6:N046.15.03.200:E014.22.59.100:N046.05.53.800:E014.27.19.100:N046.01.05.200:E014.37.30.600:N046.08.56.000:E014.39.14.600:N046.12.11.900:E014.31.58.900:N046.12.29.900:E014.29.27.500:3500

Any idea why is that so or is there a workaround?

Thank you

Bostjan

Juha Holopainen (839337)

Bostjan Laba (1190497) I've added polygons to MSAW file. Lines/Polygons are displayed properly but altitudes numbers are not displayed "within" each polygon

The view option for the data file contents is meant for development purposes, to be able to see if the file contents are read by the plugin as intended. The labels are placed to the geographical center points of the polygons. You should create sector file or plugin maps for anything the controllers should be looking at, there you can define the label positions and other parameters as needed.

Ricardo Sousa (1110850)

Can the AUP be automatically be downloaded when connecting to the network (same logic as the winds aloft)? Otherwise it's an annoying extra step every time someone logs on.

Max Kuhla (1157125)

[unknown]
In the Swedish setup it downloads when connecting as an active position,

HTTP_AUP_URL=https://statsim.net/lfvuseplan/beta/.txt
Areas_AUP_Activation=1

then we've specified the window to open with all login suffixes:

[_CTR]
Window_ASM=1,100,400,640,317
[_APP]
Window_ASM=1,100,400,640,317

and so on for DEP, TWR, GND and DEL.

Ricardo Sousa (1110850)

Max Kuhla (1157125)
Oops forgot about Areas_AUP_Activation, now it's working, thanks.

Magnus Meese (997444)

Request: Option to show SELCAL as list item, and in FP window.

TopSky is used in multiple ocanic sectors, and while I guess it wasn't made to do that, it'd be nice to have SELCAL visible. At present, the FP window even hides it completely in the way it breaks down and separates out the RMK section. With that in mind, maybe there could/should be a field for remaining info Topsky isn't able to decode in the FP window?

Ricardo Sousa (1110850)

Juha can you please add an option to inhibit APW when cleared for approach, like in Divergence_RAM_Inhibit_App_Clr or MSAW_AppInhibit?

Bostjan Laba (1190497)

Juha Holopainen (839337) Thank you, I understand now.

Max Kuhla (1157125)

Y (and guessing Z-)FPL indicators are triggered even when the respective rule should not trigger it.

A VFR flight plan where the route contains "VFR" triggers the indicator Y despite it already being a VFR flight plan, I'd assume it works the same way, triggering Z when having "IFR" present in the route of an IFR flight plan.

My suggestion is to change this behaviour, ignoring route strings that do not differ from the "main" flight rule, sometimes vfr pilots (incorrectly) file VFR in the route, this should be interpreted as a V flight plan and not Y if I'm not mistaken?

Bernardo Reis (1096507)

I'm currently unable to retrieve TAFs (getting "No TAFs found" with the default HTTP_TAF settings. NOAA recently changed the website, maybe that's related?

Juha Holopainen (839337)

As Y and Z are not possible as filed flight rules on the network, the plugin uses the filed flight rules as the current flight rules (and changes them on "Assume"/"On-Contact"), and the existence of "IFR" or "VFR" in the route section as an indication of the "originally filed flight rules", triggering the respective flag and flight rule in the FPL window.

The TAFs are loading normally for me, so appears to have been a temporary issue.

Bernardo Reis (1096507)

Still couldn't pin point the issue exactly, however it appears that on STAR acknowledge, the FPL gets reset or something similar and the last asssigned CFL and RFL are lost and revert to the previous/FPL values.

Juha Holopainen (839337)

Bernardo Reis (1096507) Still couldn't pin point the issue exactly, however it appears that on STAR acknowledge, the FPL gets reset or something similar and the last asssigned CFL and RFL are lost and revert to the previous/FPL values.

After trying out various different cases, I believe this happens when you acknowledge the the STAR when the STAR is not found in the FPL route string. This makes the plugin insert it there and amend the plan. Amending the plan appears to reset any previous controller assigned RFL value which is a bit unexpected. If at that time the CFL was equal to the controller assigned RFL, it also gets reset to the original FPL RFL (this is because on the network the CFL is set to zero when it's equal to the RFL, as it's still handled as a "temporary altitude" which gets discarded if it's the same as the "requested altitude", and any RFL change changes CFL accordingly unless a plugin notices it and intervenes). I have not been able to reproduce the CFL getting reset if it was a value different from the RFL.

I can add a check for a controller assigned RFL in the code before amending the plan and then reassign it. The plugin likely needs changes elsewhere in the code as well now that I know about this behavior...

Romtam Kangsawiwat (1338465) In the SOIR setups, the runway on the left side MUST be defined first. In your setups for 01/02L and 01/02R this is reversed, you're telling the plugin that the approach path for rwy 01 is on the left side of the approach paths to 02L and 02R which is not true. This causes the NTZ areas to be defined wrong (as can be seen in the image) and other issues in the calculations.

Romtam Kangsawiwat (1338465)

Hello, I am trying to diagnose an issue where STCA triggers between aircraft on final and aircraft on ground.

If I comment out everything in TopSkySTCA.txt, no STCA seems to occur. Here is the content of the file:

FINALAPP:VTBS:01:25
FINALAPP:VTBS:02L:25
FINALAPP:VTBS:02R:25
FINALAPP:VTBS:19:25
FINALAPP:VTBS:20L:25
FINALAPP:VTBS:20R:25

SOIR:VTBS:19/2500:20L/3500:25
SOIR:VTBS:19/2500:20R/3500:25
SOIR:VTBS:01/2500:02L/3500:25
SOIR:VTBS:01/2500:02R/3500:25

In TopSkySettings.txt, STCA_Floor is set to 2200, it looks overwritten by the STCA settings (as probably is intended)

Any help would be appreciated.

Marius Linge (1621930)

Feature request: It would be great to allow for subfolders under LMAPS at some point! Trying to organize and find LMAPS can be somewhat of a headache.

Romtam Kangsawiwat (1338465)

Juha Holopainen (839337) Thank you for the reply. Looks like no longer getting STCA after swapping 01/02LR around 😄

« Previous Page Next Page »