- Fri Jan 12, 2018 11:43 am
Just a few notes to your previous requests (yes, I still follow this topic from time to time
Patrick Weineis 1244867 wrote:We have at Austria 2 new station, and hopefully you could intigrate it into the System.
LOVV_N_APP -> provide APP service for LOWL and LOWS
LOVV_S_APP -> provide APP service for LOWG and LOWK
Don't know if this is possible
possible with VATSpy in its current state. VATSpy cannot determine any sub-sectors by underscores, e. g. LOVV_N_APP is handled the same way as LOVV_APP. Only solution would be to assign another callsign to both units without
underscores, for example LOVV-N_APP.
Toby Rice 1245046 wrote:What will it take to update the Honolulu airspace name and identifier for VATSPY?
We want to replace:
PHZH with HCF
Honolulu FIR, USA with Honolulu Control Facility, USA
HNL_CTR -> HCF_CTR
Replacing the FIR designator which is shown as label inside VATSpy, that is "PHZH" with "HCF", is no optimal solution because VATSpy will then think the FIR is located in Somalia ("HC" is its country ID
). If you replace the FIR description "Honolulu" with "Honolulu Control Facility", VATSpy will display this as "Honolulu Control Facility FIR" or, if controlled, as "Honolulu Control Facility Center" which is a bit weird IMO.
Thus my suggestion: add the following line
to VATSpy.dat and leave the rest unchanged.
I see you still have strong "bindings" to VATSpy, but always keep in mind that the software itself will likely not be updated in the future and has some strong technical limitations, especially in displaying sub-sectors.
Bristol Bulldog IIA, G-ABBB, Borkum (EDWR) to Port Elizabeth (FAPE)
current location: Reggio Calabria (LICR)
flight time: 13:45 h