Kenneth Haught 1067681 0 Posted March 7, 2016 Share Posted March 7, 2016 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 post Share on other sites
Josh Glottmann 13 Posted March 7, 2016 Share Posted March 7, 2016 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. Oakland ARTCC Link to post Share on other sites
Ross Carlson 72 Posted March 7, 2016 Share Posted March 7, 2016 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 post Share on other sites
Kenneth Haught 1067681 0 Posted March 15, 2016 Author Share Posted March 15, 2016 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 post Share on other sites
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now