Board of Governors Don Desfosse Posted July 11, 2017 at 03:18 AM Board of Governors Posted July 11, 2017 at 03:18 AM Steven, I am aware of such an incident 2-3 years or so ago that I believed was resolved. Is your experience more recent? If so, I'd like to hear about it in much more detail. Via email, not on the forums, please. Don Desfosse Vice President, Operations Link to comment Share on other sites More sharing options...
Steven Perry Posted July 11, 2017 at 03:39 AM Posted July 11, 2017 at 03:39 AM That was probably the same one. It was resolved for that instance I believe but the technical issue of XSB I think might still exist. The problem has reoccurred since then infrequently and without much undue delay to the pilot. So long as it's not FNO, things get sorted out reasonably well. If anyone is interested in logging all such instances where pilots are spun or otherwise inconvenienced due to the frequency thing, I can start doing so. My usual airspace borders more than one ARTCC that use the .025MHz step and we also have a handful of less frequently used .025 frequencies internally. Steven Perry VATSIM Supervisor Link to comment Share on other sites More sharing options...
Board of Governors Don Desfosse Posted July 11, 2017 at 06:13 AM Board of Governors Posted July 11, 2017 at 06:13 AM Thanks. I want to be aware of any instance happening in the USA. It's not acceptable and won't be tolerated. Don Desfosse Vice President, Operations Link to comment Share on other sites More sharing options...
Dace Nicmane Posted July 11, 2017 at 10:47 AM Posted July 11, 2017 at 10:47 AM Is it true that the oldest pilot client/FS version that can still connect to the network will not fail to connect if controllers use for example 118.575 instead of 118.570? The problem I described happened during the last CTP Westbound. So no, we can't connect to a frequency ending in 5. And yes, it's confusing, because the controller says 5, but you have to tune 0. But you get used to it. I don't remember what the exact XSB messages were, whether it appeared to connect or said it couldn't or nothing at all. If anyone wants to do an experiment, I'm free for the next 10 hours or so, unless I'm flying. Link to comment Share on other sites More sharing options...
Andrew Morkunas Posted July 14, 2017 at 02:55 PM Posted July 14, 2017 at 02:55 PM There is a piece of software I keep in my ATC toolbox, Roger Wilco. EuroScope is the only ATC client that shows who is connected to your voice channel. For other ATC clients I use Roger Wilco. The current VATSIM voice servers use a recoded version of Roger Wilco (hence the rw. at he beginning of many voice server addresses). You can use Roger Wilco to see who is connected on your voice channel as well as monitor the channel itself. So when I have a pilot that is not responding to my voice instructions I just turn up the volume on Roger Wilco to monitor my transmission. If I can hear myself I know it's not me. Roger Wilco is still available for download https://www.fileplanet.com/57176/50000/fileinfo/Roger-Wilco-Mark-I Andrew Morkunas Twitch: padre_andrew ATC Simulations Link to comment Share on other sites More sharing options...
1275389 Posted July 14, 2017 at 03:24 PM Posted July 14, 2017 at 03:24 PM You can also see who's transmitting on every channel on a voice server by going to rw.liveatc.net:18009/?opts=-R-D You can also add in a specific channel or change the voice server. i.e. voice.radarcontact.me:18009/NCT_2W?opts=-R-D You have to refresh the page to see who's currently transmitting. Link to comment Share on other sites More sharing options...
Recommended Posts