Carl Stallone 925048 Posted April 2, 2010 at 07:53 PM Posted April 2, 2010 at 07:53 PM Operating in Anchorage Center (as well as I would guess some of the Russia, China, Japan sectors) the route does not calculate or display correctly when the route will cross 180 longitude (same for time or distance calculations in the "planes" list). Is there a workaround for this on any affected sector? Link to comment Share on other sites More sharing options...
Todor Atanasov 878664 Posted April 4, 2010 at 05:02 PM Posted April 4, 2010 at 05:02 PM Only G can answer this one. Copied to the beta forum. EuroScope BETA Tester/Board of Designers Link to comment Share on other sites More sharing options...
Carl Stallone 925048 Posted April 5, 2010 at 01:36 AM Author Posted April 5, 2010 at 01:36 AM Thanks. A second part of the question would be that our airspace crosses the 180 line, and generally we've been just sending the traffic to advisory frequency before they cross westbound, as they will disappear from our scope. Is there any way to regain visibility for the controller West of the 180 as well? Setting the vis west of the line doesn't work. Link to comment Share on other sites More sharing options...
Todor Atanasov 878664 Posted April 5, 2010 at 03:57 PM Posted April 5, 2010 at 03:57 PM I'm not sure if it is a ES issue or server issue. Is the traffic shown in VRC? EuroScope BETA Tester/Board of Designers Link to comment Share on other sites More sharing options...
Norman Blackburn Posted April 5, 2010 at 04:07 PM Posted April 5, 2010 at 04:07 PM The server sees the world as flat, with the divider being at 180deg. In VRC a user can open a second window with a vis point set. I [Mod - Happy Thoughts]ume ES users can do something similar. Norman Link to comment Share on other sites More sharing options...
Karl Kornel 964857 Posted April 5, 2010 at 08:04 PM Posted April 5, 2010 at 08:04 PM I wonder, would it be possible to work around the issue by settings two vis points, one east of the International date line, and one west? A. Karl Kornel - vZID C1, FE, and Mentor Smoke Bomb! POOF Link to comment Share on other sites More sharing options...
Carl Stallone 925048 Posted April 6, 2010 at 12:17 AM Author Posted April 6, 2010 at 12:17 AM The issue does exist with VRC as well, but the setting of the vis points to the west of the line doesn't help. We can open a separate sector file and see only what's west of the line, but the same problem to the east, and coordination is a bit tough between the two - if you wait for the eastern controller to be able to see the target, you can't handoff, and if you handoff early the eastern sector can't see the target. May be a vatsim limitation, but was hoping someone had another workaround. Add to it the size of our airspace - we need all 4 vis points for the area east of 180, and even that will not provide adequate radio coverage for the aircraft. Link to comment Share on other sites More sharing options...
Gergely Csernak Posted April 12, 2010 at 05:31 PM Posted April 12, 2010 at 05:31 PM I will implement the variable back-end in ES. That will default to the center point defined in your SCT +-180 degree. For the server issue I guess that multiple visibility points should work. Gergely. EuroScope developer Link to comment Share on other sites More sharing options...
Recommended Posts