- Fri Mar 24, 2006 1:49 pm
Here is what I send to my student(s). Feel free to use it.
About AcSim 1.0
AcSim 1.0 Is a program that allows the instructor to steer several data tags appearing on the controller client radar scope. You could compare it with a very simple flight simulator without scenery. The instructor enters the data in the autopilot and AcSim send's it data to the Vatsim server, as would any aircraft do when connected to Vatsim with FsInn or Squawkbox. So you can handle the traffic as you would normally do or as the instructor will teach you to do.
What can each aircraft do in AcSim 1.0?
- fly a heading / direct to (not more than one waypoint at a time)
- enter a kind of hold on a fix (the aircraft will tend to fly around the fix).
- intercept an ILS or LLZ at 30Â° angle or less (the aircraft will not intercept at an angle higher than 30Â°)
- descend or climb to an altitude/flightlevel
- intercept a glideslope if following the LLZ of an ILS (it is possible that the aircraft stops descending if it reduces speed below 160 kts).
- increase or decrease airpseed (it can affect or even stop the descend/climb behaviour of the aircraft).
- increase or decrease descend rate (it may stop the descend or climb of the aircraft if the airspeed is not in accordance)
- transmit a squawkcode and Ident, but not squawk stantdby.
- show a flightstrip on the radar client.
There are however some limits to AcSim 1.0.
It can be, in some situations, that the instructor will pause the simulation. Either in some extreem situations where he receives too much instructions, or to discuss the situation with the student.
- Lateral navigation
AcSim is conceived to receive vectors, as well for arrivals as for departures. It can however fly direct to any given waypoint (intersection, VOR, NDB, airport) present in the sector. But never more than one waypoint at a time. Furthemore, it is the only instructor that flies all the aircraft, who is alos the voice for all aircraft (very exceptionally, a second instructor could 'fly' a part of the aircraft). So avoid giving instructions like 'leave Flora VOR heading 310' to one aircraft, and similar instruction to another aircraft. Try to limit the lateral navigation instructions to headings or 'direct to'. The same is valid for departures: aircraft will not follow complicated SID's.
- Vertical behaviour
It can be that the aircraft stop's climbing or descending when speed or descend rate are changed.
An aircraft departing will not takeoff if speed is 250 kts and climb rate higher than 1800 ft/min. (climb rate can be increased later.
All departures will be on the runway.
- How to connect?
- With ASRC: In your ASRC folder, edit or create an 'ipaddr.txt' file and the following line: 'sweatbox.vatsim.net Sweatbox'. If you like to have Sweat box appear at the beginning of your list, enter this line instead: 'sweatbox.vatsim.net 0-Sweatbox'. If on the contrary you would like to see Sweatbox appear at the end of your list enter this line instead 'sweatbox.vatsim.net zz-Sweatbox'
- Open ASRC and prepare it as you would do for a normal ATC session. (Visibility range, primary voice, open the sector file, etc.)
- In the 'connect' box enter the data as you would normally do (callsign as indicated by your instructor. e.g. EBBR_APP). In the 'Server' list choose 'Sweatbox' or what you entered in your 'ipaddr.txt' file. Click 'OK' and you will probably see your instructor waiting for you with a bunch of arrivals and a few others ready to copy the departure clearance.
Xavier Van Nieuwenhuyse