Ground Radar plugin 1.2.2 beta 3

[Ricardo Sousa (1110850)]

New beta version is available:

Ground Radar plugin 1.2.2 beta 3

• Bug fixes

 

 

Edited to include the download link and change list above. Original post below:

-----------------------------------------------------------------------------------------------------------------

Hello, we are looking into implementing TopSky and the ground radar plugins in Portugal vACC. We have an issue with the stands, some of the stands at LPPT overlap in a way that some of them are essentially in the same position, the pictures shows it better

 

The diagonal ones are for wide bodies generally speaking and the straight ones have A321 as critical aircraft type.

 

In the future could the plugin use more info such as the heading or aircraft type to determine which stand is being occupied? In my eyes this layout could be solved by either telling it the heading or by having a minimum wingspan or weight or something to differentiate between narrow and wide body stands.

Edited February 1, 2020 by Juha Holopainen

[Juha Holopainen]

Adding the possibility to check for aircraft heading when considering stand occupancy appears to require very little additional code, I'll put that in.

[Adrian Bjerke (1339353)]

I got this screenshot from one of our controllers, and he asked what it meant.
https://prnt.sc/purqlk

I am not so sure myself, any help on this one?

[Christian Kovanen (1379372)]

@Adrian Bjerke What do you mean? I see nothing weird in the picture. To me it looks just like ground radar always does. If you mean the labels thats just pro mode from settings > display, when an airacft doesnt have their transponder on

Edited November 10, 2019 by Christian Kovanen

[Jonathan Hougaard (1457572)]

Hope this is the right forum.

In the Ground Radar plugin, how do I save the settings, so I don't have to change the settings every time I load ES?

[Adrian Bjerke (1339353)]

2 hours ago, Jonathan Hougaard said:

Hope this is the right forum.

In the Ground Radar plugin, how do I save the settings, so I don't have to change the settings every time I load ES?

Settings have to be specified in the GRpluginSettings.txt file. Lot's of info about it in the developer guide that is included with the gpplugin download.

[Jonathan Hougaard (1457572)]

Perfect, worked it out, thanks!

[Adrian Bjerke (1339353)]

Regarding the groundplugin, what is concidered mil, mil cargo, mil heli?
In Oslo we have issues with A333, B752/3 (can't not remember exactly, we rarely have them) are issued the military stands instead of the civillan ones.

 This happends even though the A333 is not defined as military in the GRpluginAircraftInfo.txt file.

A332    60.3    58.8    17.4    230000    A
A333    60.3    63.6    16.85    230000    A

Here is our definitions of military stands:

// Military Stands
//STAND M1
STAND:ENGM:M1:N060.12.37.184:E011.05.52.867:40
ATYP:C130
USE:T
WINGSPAN:41

//STAND M2
STAND:ENGM:M2:N060.12.35.512:E011.05.51.965:40
ATYP:C130
USE:T
WINGSPAN:41

//STAND M3
STAND:ENGM:M3:N060.12.33.893:E011.05.51.214:40
ATYP:C130
USE:T
WINGSPAN:41

//STAND M5
STAND:ENGM:M5:N060.12.28.935:E011.05.48.136:20
USE:IMT

//STAND M6
STAND:ENGM:M6:N060.12.28.516:E011.05.51.085:20
USE:IMT

//STAND M7
STAND:ENGM:M7:N060.12.28.121:E011.05.53.898:20
USE:IMT

//STAND M8
STAND:ENGM:M8:N060.12.27.675:E011.05.56.837:20
USE:IMT

//STAND M9
STAND:ENGM:M9:N060.12.27.296:E011.05.59.782:20
USE:IMT

//STAND M10
STAND:ENGM:M10:N060.12.26.897:E011.06.02.702:20
USE:IMT

//STAND M20
STAND:ENGM:M20:N060.13.10.030:E011.06.12.205:20
USE:M
PRIORITY:-3

 

Edited December 12, 2019 by Adrian Bjerke

[Martin Loxbo (811805)]

Maybe this is the key to why they get sent to the military stands:

Quote

If automatic stand assignment fails to find a suitable stand, the plugin tries again with some restrictions removed (first the CALLSIGN, then also the NOTCALLSIGN, USE, ADEP, NOTADEP, SCHENGEN, NONSCHENGEN, VIA and NOTVIA restrictions are lifted).

Since many of your stands don't have any restrictions in terms of aircraft dimensions, type or WTC, as soon as the "USE" restriction is lifted I suppose any aircraft is likely to get assigned to those stands.

Also if my understanding is correct, having both ATYP and wingspan restrictions for the same stand is redundant, as the only aircraft that will ever get assigned to those stands are the C130. If you want to make it so that C130 has to go there, but the stand is also available for aircraft with wingspan up to 41 m, then you should create a duplicate stand with different priority, for example:

//STAND M1
STAND:ENGM:M1:N060.12.37.184:E011.05.52.867:40
PRIORITY:+1
ATYP:C130

STAND:ENGM:M1:N060.12.37.184:E011.05.52.867:40
USE:T
WINGSPAN:41

This means that firstly stand M1 would be used by C130, but it's also available for any "T" aircraft with wingspan up to 41 m. Looking in the aircraft file the C130 is defined as C by the way, so you would not be able to direct C130s to any stand using the "T" usage category.

[Juha Holopainen]

13 hours ago, Adrian Bjerke said:

In Oslo we have issues with A333, B752/3 (can't not remember exactly, we rarely have them) are issued the military stands instead of the civillan ones.

Your stands definition file doesn't seem to have any stands those aircraft types could use. The plugin then has to relax some restrictions as Martin wrote in order to be able to assign a stand.

The stands file seems to contain some strange definitions, apparently due to misunderstanding the required syntax. For example

//STAND 49
STAND:ENGM:49:N060.11.35.090:E011.06.23.520:20
USE:A
WTC:J
ENGINETYPE:J
CODE:E
NOTADEP:EN
WINGSPAN:61
LENGTH:64

defines the stand to be useable by aircraft of wake turbulence category J whose max aerodrome reference code is E and max wingspan 61m (plus some other limitations). Now there's nothing wrong with specifying both max code and wingspan, but it doesn't really do anything useful as the code is only another way of specifying the wingspan limit (for the plugin, CODE:E is the same as WINGSPAN:64.999). The problem with this stand is that there are no aircraft that can meet all the requirements (there are no WTC J aircraft with wingspan 61m or less). The mistake is probably the WTC line, which should list all the categories allowed, not the maximum (so to allow any WTC, either don't have a WTC line at all, or define "WTC:LMHJ")

3 hours ago, Jonathan Hougaard said:

Hmm. When trying that, I get "Error: Unable to create APL (invalud callsign)". Any idea why?

That error is caused either by a blank callsign, or a callsign that isn't online. If the callsign is correct, I could use a log file of such a situation so I can troubleshoot.

Edited December 12, 2019 by Juha Holopainen

[Simon Thornqvist]

Hi.

I have a small bug with ES GRplugin. When i open inbound list and get a aircraft that is about to arrive the callsign and all aircraft info gets under the gray area.. 

Like this: 

But i don't know how to fix it so if someone mabye know anything about it please tag me.

Edited December 18, 2019 by Simon Thornqvist

[Juha Holopainen]

I'll get that fixed for the next version