TopSky plugin 2.5 beta 15

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?

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.

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 😄

Alexandr Belyakov (1720655)

Hello, staff. Today i want to ask you about leader lines
Is it possible to do create a custom leader line like on the image? If yes, how to do it?

Bernardo Reis (1096507)

Alexandr Belyakov (1720655)

Not with Topsky or Euroscope. You would need a separate plugin to display it like an arrow

Felix Musselmann (1025793)

Hi Juha,

would it be possible to add RDF support for TrackAudio?
The API can be found here: https://github.com/pierr3/TrackAudio/wiki/SDK-documentation

Felix

Bernardo Reis (1096507)

Two requests that I hope are small enough and not too much work:

Would it be possible to keep the time in the A-A QDM?
Would it be possible to remove SEP vectors and A-P QDM by right clicking anywhere in the vector instead of only at the tip?

Juha Holopainen (839337)

The feature set for version 2.5 has been closed for some time now. Any new stuff would be eventually considered for some possible future version.

Clicking anywhere on a line won't be possible unless the EuroScope plugin API is updated to allow for mouse areas other than standard rectangle shapes. As it is now, making this possible would involve creating dozens or hundreds of small mouse area rectangles along each line, depending on the line's length on the screen.

« Previous Page Next Page »