Tim Roden 987596 Posted March 1, 2016 at 09:27 PM Posted March 1, 2016 at 09:27 PM Working with Alaska Radar site on Shemya Island is beyond long -180. I can't put anything out there. Tried a postive number to no avail. Then Noticed my drawings won't go past that line either. Tim Roden ZAN C3 Link to comment Share on other sites More sharing options...
Ross Carlson Posted March 1, 2016 at 10:39 PM Posted March 1, 2016 at 10:39 PM What do you mean when you say your "drawings" won't go past that line? Developer: vPilot, VRC, vSTARS, vERAM, VAT-Spy Senior Controller, Boston Virtual ARTCC Link to comment Share on other sites More sharing options...
Tim Roden 987596 Posted March 2, 2016 at 01:22 AM Author Posted March 2, 2016 at 01:22 AM Anything on the sector file past that line is not appearing in vERAM. Also you cannot scroll past that line. Tim Roden ZAN C3 Link to comment Share on other sites More sharing options...
Ross Carlson Posted March 2, 2016 at 02:39 AM Posted March 2, 2016 at 02:39 AM Please export your facility file and put it somewhere that I can download it, and I'll check it out. Developer: vPilot, VRC, vSTARS, vERAM, VAT-Spy Senior Controller, Boston Virtual ARTCC Link to comment Share on other sites More sharing options...
Tim Roden 987596 Posted March 4, 2016 at 08:39 PM Author Posted March 4, 2016 at 08:39 PM Looks like this is a general vatsim problem. looked at our sector file from VRC and all of that information was on the other side of the world. Tim Roden ZAN C3 Link to comment Share on other sites More sharing options...
David Zhong Posted March 5, 2016 at 02:01 AM Posted March 5, 2016 at 02:01 AM It's not specifically a VATSIM issue (but there is a related issue that is), but an issue with the map projection system. My understanding is that all of the controller clients to date treat lat/longs as a grid, which will fail at the 180th meridian and cause significant distortion near the poles. The workaround that New Zealand and Oakland Oceanic have been using is to have separate sector files for each side of the 180th meridian. There is a related issue with FSD (the server software) that does not handle the 180th meridian when determining whether other clients are in range. The workaround for this is to set visibility points on either side of the 180th meridian. David Zhong Link to comment Share on other sites More sharing options...
Recommended Posts