Alex Vainer 929287 Posted May 6, 2007 at 03:51 AM Posted May 6, 2007 at 03:51 AM I'm controlling right now, MDW_TWR, and was browsing around the forums. I noticed that my vatsim indicator had KMDW_ATIS instead of MDW_TWR. Just a heads up, nothing big. Alex "AV" Vainer C1 Los Angeles ARTCC Link to comment Share on other sites More sharing options...
Ross Carlson Posted May 6, 2007 at 03:53 AM Posted May 6, 2007 at 03:53 AM Hah ... it never even occurred to me that that would happen. The vatsimindicators.net site admin will need to modify his script to ignore _ATIS connections in the data file. I'll be doing that for my own indicator script as well ... thanks for the heads-up. Developer: vPilot, VRC, vSTARS, vERAM, VAT-Spy Senior Controller, Boston Virtual ARTCC Link to comment Share on other sites More sharing options...
Martin Georg 811874 Posted May 6, 2007 at 07:19 AM Posted May 6, 2007 at 07:19 AM Possibly comes from the fact that usually you will connect your voice ATIS later than your main connection, and the indicator always uses the last connection made ... best regards, Martin Georg Link to comment Share on other sites More sharing options...
Ross Carlson Posted May 6, 2007 at 07:52 AM Posted May 6, 2007 at 07:52 AM Possibly comes from the fact that usually you will connect your voice ATIS later than your main connection, and the indicator always uses the last connection made ... The vatsimindicators site uses the servinfo data file, which sorts callsigns alphabetically, so if you are providing a voice ATIS, the callsign shown in your indicator would depend on which callsign comes first in the file, and on how the indicator site script processes the file. My guess is the one that comes later in the file will override the earlier one, so if I'm on as BOS_TWR, and as KBOS_ATIS, it would show KBOS_ATIS in my indicator. Developer: vPilot, VRC, vSTARS, vERAM, VAT-Spy Senior Controller, Boston Virtual ARTCC Link to comment Share on other sites More sharing options...
Recommended Posts