Jump to content

Maps don't follow ASR file with ES fast key


Jakob Arne Bronstad (1000634)
 Share

Recommended Posts

Jakob Arne Bronstad (1000634)

If we use ES fast keys the maps don't follow ASR file: 

ASR1: Radar looking at a TMA X

ASR2: Radar looking at a TMA Y

The fix is now to go and reload setting file. This must not be intentional?

 

Jakob Brønstad
Sectorfile Department Polaris FIR

Email.png

Link to comment
Share on other sites

Juha Holopainen

The intended behavior is as follows:

Maps are radar-screen specific unless otherwise defined in the data file, much like the sector file items whose display is ASR-specific. When a new ASR file is opened, maps defined as global will be synchronized (in some cases a screen refresh by zooming/panning may be necessary to trigger redrawing the background).

If non-global maps are toggled in the settings file, their status is changed only in the currently displayed radar screen - for this reason, when changing the login callsign - i.e. logging on the network - the screen meant to be primarily used should be active so the intended maps will be displayed (so when logging on as CTR, you can have opened additional TMA ASRs already and set them up map-wise ready for action, but have the CTR ASR open when logging on so the correct maps will appear there).

If necessary, a snapshot of currently active screen-specific maps can be saved and then loaded in another ASR. Status->Plugin Status->Maps->Save set and then with the other ASR active, Load set.

If the plugin does not work according to this: version 2.3.1 or some earlier? Is there a difference in the behavior when the ASR is opened by not using the fast keys or is this specific to opening the ASR using the keys?

Link to comment
Share on other sites

Jakob Arne Bronstad (1000634)

In Norway we have one Radar Scope Natcon RaDsThis is used by CTR and APP. For Twr we use Gnd radar.
Some controllers have duplicated the RaDs ASR file to make it easier to go to the northern part of the FIR or a TMA.
In the setting file we have a load maps on logon-callsignall is on one screen in one instance of ES.

There is no difference if we use ES fastkeys or F7 key

Setting file:

[ENOR_CTR]
Setup_LoadMap=MVA\MVA ENGM

Maps file:

MAP:MVA ENGM
COLOR:MVA
FOLDER:MVA
ZOOM:9
FONTSIZE:-:1
STYLE:DOT

Jakob Brønstad
Sectorfile Department Polaris FIR

Email.png

Link to comment
Share on other sites

Juha Holopainen

Looks like everything is working as intended there. Unless you've left some key parts of the data file out, that map is screen-specific, therefore toggling its state using the settings file will only affect the current radar screen.

Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
 Share

×
×
  • Create New...