lb767 / vsmr Goto Github PK

Suggest to enable sounds for different events.

• Events and files can be defined in the json.
• Muting ES (Sounds off) should also mute vSMR sounds
• Adding audio events for: DCL request, RIMCAS alert (stage 1 & 2)

The system in Zurich does change the appearance of the tag depending on different clearances. What could be implemented for the plugin is that a change of the ground tag to DEPA makes the frame of the concerned aircraft wider. Should generally be a white border. So the border from hovering should be displayed then permanently and in bold.

When attempting to login to hoppie for the PDC, no server message is received as outlines in the wiki.

Is there any option to have different status of labels, like the native tagged/detail tagging level of EuroScope?
Is there any chance to use the native EuroScope tags so they can be setup via the tag editor?

The items named in the title should be available separately to offer best configuration options.

When an instance of a vSMR radar has been opened and the active runway are changed via the ES dialog, ES (r25) crashes to desktop.

RIMCAS seems pretty dumb as it is in vSMR (from what I can tell, I haven't look in too much detail).
Just alerts as soon as 2 planes are inside the runway area.

It would be good if we could get a bit more realistic with this, if you have more insight about this feel free to share @kusterjs

Mouse symbol should be reset to system default always when leaving a SMR view (so a custom defined symbol doesn't stay on default radar views). I would also make the cursor part of the settings that a controller can change in the plugin itself. So this would mean to move this from profiles to plugin settings.

First line of the label should allowed to have a different (larger) font size than the remaining lines.

The measuring for the distance to touchdown currently considers the far end the runway (opposite threshold).
The IAT is only used for arrivals. I wouldn't also remove the existing Impending Arrival Window (IAW), but keep them as they are and add a new option for the IAT, preferably in the Display section. It's not an actual alert.

The current organisation of settings (in the asr file) and profile items (in the json file) seems to follow no clear philosophy. I suggest to differentiate between settings the user might want to change or adapt during a session according to his needs and the profile, which should contain data for the display which should not be required by the user to be changed. So the more static data will be in the json, and any user customisation in the asr file. Or in other word, anything you can change as a user should be in the asr, what you can't change directly remains in the json.
I therefore suggest the following changes regarding the json file:

1. remove entry "cursor": use the default one when no value is found in the asr file, save the value to the asr
2. change font size to a value that can be entered by the user and save this value in the asr, remove the preset for the 5 sizes in the menu and the json
3. move "pro_mode" to asr, the "accept_pilot_squawk" might be considered taken from the ES settings
4. move "auto_deconfliction" to asr
5. move "leader_line_length" to asr
6. move "extended_lines_length" to asr
7. move "extended_lines_ticks_spacing" to asr

ProMode settings and its associated subsettings should be taken from ES directly. It makes no sense to maintain f.e. two different lists of squawks.

I think the "Ä" before the ° should not be there.

As there is no own label specification available for traffic on ground, but inside the RWY area, I request an additional tag displaying groundspeed only if inside the RWY area.

Can the text for fields with no value determined yet (noGate, noFPL) be changed? Maybe it could be a global setting (to be chosen by the user) to either display those generic "there is no value" texts or not.
It would be nice to have an option to make such empty tag fields just a clickspot of about 1-2 letters wide in case no text is displayed. So you can still click there to use the assigned functionality (open FP, edit scratch pad).

I observed that the closed runway area is changed with the LVP status. However, the closed runway area should always be displayed in the same dimensions. Only the area considered for RIMCAS warning should change, but this is an area not to be displayed at all. Runway data could be taken from the sct file directly. Then, only the width for normal visibility and LVP would need to be specified additionally in the vSMR settings file.

Appearance of predicted track line should be configurable with the following elements:

• thinkness of the line
• symbol on the track position visible or not
• length of the leader line (smaller steps need to be possible, line should start at the target position)
• these settings should be change in the main window and the SRW independently

The current release leads to a crash upon closing ES r24.

Is it possible to use RAW files for playing sounds?

To trigger the change from the airborne label to arrival and from departure to airborne, an altitude value should be introduced in the json file.
This would make the change more realistic since I guess currently the ES speed value is taken into consideration.