I’ve noticed that a user (@baixingnan0011) has been occupying the “London Center” frequency on the Training Server for the past three days without responding to any pilot requests.
I don’t know if this is a bug or something, but is there any way to report or address this situation? It would be great to know if there’s something that can be done to resolve this.
It’s a bug. Normally you get kicked out if you don’t respond to any messages for a little over a minute. They’re not even actually controlling, the server just thinks they are. I’ve been the person on the other end before and it’s problematic for everyone. Hopefully it gets fixed soon. Currently the only solution is a server restart so maybe someone will see this and restart the server.
That’s going to be the difficult part, from what I have learned reading other posts regarding issues with the training server, it actually doesn’t matter if something doesn’t work on the training server
It is a bug. If a controller is non-responsive to a message for 60 seconds, a warning appears on the screen. If another 60 seconds goes by and no response to a pilot is made, the system automatically disconnects the controller.
In this case, there isn’t a controller actually there so no one to be disconnected.
I mean I can hear someone say they are requesting to change frequency or change altitude or requesting to approach etc, and then never anything after that from the pilot which suggests they have received a response or any sort of response that suggests communications with the ATC. Some people are repeating their messages etc trying to get a response.
There is no controller there to respond which is why it’s not automatically disconnecting them when pilots’ are not replied to.
This seems to only happen rarely with certain user network errors occur and/or the controller force closes the app without ending the session. It doesn’t happen very frequently so there’s insufficient data to pinpoint the issue but the problem is when it does occur, it’s generally with a frequency where many will notice. Unfortunately the only way to resolve it at this time is if a dev reboots the entire server.