Troubleshooting
The answers to what usually goes wrong, and how to file a report the operator can act on.
| What you see | What it is |
|---|---|
| A server command produces no reply at all | A spelling the server cannot place. Only a line addressed to an aircraft is answered when it cannot be read |
| An aircraft ignores you | Check the comma after the callsign. A callsign nothing is flying under is answered by name, so silence means the line never reached the aircraft parser |
session start is refused | A previous session at that airport is still draining. Work its traffic down, or session delete it |
session start is refused naming a limit | The server already runs sessions at as many airports as it is set up for. The reply names them. End or delete one of those first |
| A session command names a file it could not read | The file is there and has been edited into a shape the server does not accept. Only the operator can repair it, and the server records which fault it hit. This is not the same as a file that is simply not bundled, which is a different message. session list names any scenario it had to leave out for this reason |
| Everything disappeared while you were away | Five minutes with no controller connected clears all traffic, tears down the running session and lifts a pause |
| Your airport's session ended while others were still connected | Nobody who works that airport was connected for five minutes, so the session ended and took its traffic with it. Aircraft a controller still online had assumed stayed. The end was announced on the frequency the session was started from |
| You connected and the simulation was already paused | Somebody paused it and is still connected, or left less than five minutes ago. Type resume, or session status to see who and since when |
| An aircraft sits above the glideslope and does not come down | More than one dot above the path it holds the altitude you gave it until you descend it. Within one dot it joins the path on its own, so if it is not coming down it is higher than it looks |
| You went around and do not know what it is doing | go around flies the published missed approach for that runway and climbs on its published levels. cancel app is the other option: it hands the aircraft back to you with no follow-up |
Reporting a problem
Type feedback with a short description, on any frequency, while
the problem is still in front of you. It works whether or not an aircraft is selected:
feedback DLH123 turned left instead of rightThe server collects the logs covering that moment into an archive, confirms the filename to you, and notifies the operator. You do not need to copy anything or take a screenshot.
The timing is the point: the archive is cut when you type the command, so a report filed the next day describes traffic that no longer exists. Name the aircraft if it is about one in particular, and say what happened, because an archive nobody can interpret is not worth keeping.