- Mon Aug 14, 2017 9:39 pm
Kieran Samuel Cross 1298134 wrote:This problem has been around literally since at least December 14th 2016, so we're now upcoming on the 9-month anniversary!
That would be kind of acceptable. I reported the problem back in January 2015! 2.5 years ago! Then I started participating in the VATSIM UK forum to establish contact with the developper Craig Phillips. But no answer. With increasing pressure from VATSIM UK itself and the community, some smaller changes were introduced and Craig promised to fix the bug. But he couldn't do it. So the same bug still exists.
Kieran Samuel Cross 1298134 wrote:Little bit counter-intuitive, making other controllers download, install and use a plugin, just for the benefit of a few controllers in the UK.
Seems to be one only way right now to at least identify the controller using the plugin while a session is running.
Andreas Fuchs 810809 wrote:The issue is that we cannot determine who EXACTLY is using that plugin that is causing the modification of a plane's TEMP ALT and SQ CODE. That's the start of the issue.
You can, with help of the (manually launched) ES log file function. But the file can only be reviewed after the logging has been stopped. So you would need to stop the log every time you identify a VCA interruption, go back to the log and look for the controller. Pretty complicated to aim for a smooth session.
Nicholas Cavacini 1084329 wrote:If there is an issue with a controller using the plugin, please summon a Supervisor through the use of .wallop... If the user refuses to terminate use of the plugin and it is causing issues with other users, then the user is in violation of Code of Regulations section 6.03 (C) which relates to conduct which interferes with other users enjoying the VATSIM Network.
I'm aware of this option, but refused to use it so far. It's not the way I like to see VATSIM going, but proposed now by you, Nicholas, seems to be the only current option to get rid of this faulty plugin.
As I understood some discussions in the VATSIM UK forum, the automatic squawk allocation and the automatic setting of the temporary altitude (the two "features" which cause problems) are options which can be enabled/disabled separately. So it might already help if every controller using VCA disables this functions by himself. He can continue to use then VCA without causing trouble to other controllers on the network. Even better would be a stop of those services by the developer himself. But after all my experience, Craig is not caring about others on the network ...
Jonas Kuster Leader Administration - vACC Switzerland | www.vacc.ch