Kenneth Haught Posted March 7, 2016 at 02:39 AM Posted March 7, 2016 at 02:39 AM Hey ross, I got an error (shown in the linked screenshot) when using the .nobreak command this evening. Not sure if it's a network error or a veram error. https://www.dropbox.com/s/y47tqhh8zfm21zb/Screenshot%202016-03-06%2021.37.55.png?dl=0 Cheers! Anchorage Deputy Air Traffic Manager VATSIM Senior Supervisor (Team 1) Have a question or concern? Email me at [email protected]. Link to comment Share on other sites More sharing options...
Josh Glottmann Posted March 7, 2016 at 02:47 AM Posted March 7, 2016 at 02:47 AM Kenneth, If I'm not mistaken, that's a server-side issue caused by aircraft. I've gotten it before while flying and I don't think it has anything to do with the command, just coincidentally occured at the same time. Link to comment Share on other sites More sharing options...
Ross Carlson Posted March 7, 2016 at 02:57 AM Posted March 7, 2016 at 02:57 AM Yes, you can ignore that error ... it's caused by a previous version of vPilot that sends out invalid lat/lon values at certain times. That error will stop appearing once everyone updates vPilot to the latest version I released a few days ago. Developer: vPilot, VRC, vSTARS, vERAM, VAT-Spy Senior Controller, Boston Virtual ARTCC Link to comment Share on other sites More sharing options...
Kenneth Haught Posted March 15, 2016 at 04:49 AM Author Posted March 15, 2016 at 04:49 AM Sorry I missed your reply Ross, but thanks for explaining that. I'll keep that in mind, just confounded me to see that in the chat. Anchorage Deputy Air Traffic Manager VATSIM Senior Supervisor (Team 1) Have a question or concern? Email me at [email protected]. Link to comment Share on other sites More sharing options...
Recommended Posts