Starting the programs

This is how you start everything up. Order of execution is important.

1. First start SquawkGear.
   Check for the “SquawkGear is ready” message before proceeding to the next step. It may take up to a minute, if TCP port 1863 is busy.
2. Next start FlightGear. Two command-line options are required:
   • --generic=socket,out,1,IP.addr,port,tcp,squawk
     This option tells FG to send data to SquawkGear. “IP.addr” and “port” should be the IP address and port number that SquawkGear is running on.
   • --telnet=5900
     This option tells FG to receive data from SquawkGear on TCP port 5900.

   I suggest you enable multiplayer input (with --multiplay=in,10,,5000), but disable multiplayer output, in the FG commandline. You want to see air traffic out your windshield, but you may not want your position to be transmitted to the FG mpserver (unless you would like FGTracker to record your flight). Your text transmissions to VATSIM will also be broadcast on FG mpserver — this is improper and discouraged.

   When FG is fully started up, SquawkGear should indicate a successful telnet connection.

3. Next start SB747 and AVC.
   Check that SB747 reports a successful connection to SquawkGear.
4. File a flightplan in SB747.
   See SB747 manual pages 12-14. Do not connect to the VATSIM network yet.
   (The reason being, FG usually places you on a runway at startup. If you connect to VATSIM and suddenly appear on the active runway, ATC and other aircraft will not be pleased.)
5. Prepare your aircraft in FlightGear.
   This is the equivalent of the pre-flight and external walkaround phases of real flight. Taxi your aircraft away from the runway; preferably move it to an apron or terminal gate.
6. When you, your aircraft and your software are ready, connect to VATSIM !