Closed phoenixegmh closed 4 years ago
It's likely, but this is a sector file problem, not a vSMR one. If your sector definition has the correct coordinates for FAOR, it'll work fine. it sounds like your sector file needs to be updated.
Just looking at the sector file now and FAOR appears to be in there correctly. It has co-ordinates and they appear correct
Airport is defined under AIRPORT section in the .sct file as:
FAOR 000.000 S026.08.01.298 E028.14.32.341 D
Maybe an issue with the altitude filter for ground traffic? FAOR is known for this since it is above the default value of 5000 ft.
Maybe an issue with the altitude filter for ground traffic? FAOR is known for this since it is above the default value of 5000 ft.
Negative, options adjusted for 5600ft and it doesn't show any airborne tags either
I see the elevation of FAOR ASML is 5558ft, try to raise the altitude filter to at least 7000ft and see what happens.
Raised to 7000ft, still nothing showing (AC on Stand A1 in the attached)
I think we could be onto something with the AD elevation though, I've just tried FALA and that didn't work. Awaiting further testing at FYWH to see if that clarifies the issue as it has a similar elevation.
There is the problem ;) You need to change the altitude filter in the config file (see https://github.com/pierr3/vSMR/wiki/Editing-the-Plugin-Settings-(.json-file)#changing-the-settings-values-in-a-profile), changing it in the EuroScope dialog will change nothing as it does not communicate with the plugin.
That's got it! Perfect, thanks!
With vSMR running at FAOR (old code FAJS), no tags show. Have used FACT and shows OK, is this a problem because of the ICAO code change?