A status bar is probably needed to show:

• Radar range
• Radar aid single marking value
• Number of "strikes" (lives left)
• Played scenario?

Overall multiplier based on scenario's difficulty.

• Possible cause: wrong ILS vector at one of the two ends of the asphalt strip
• Also need some test in the testing suite

So far they are the ugly HTML standard ones... brrr!

Remember to add blank lines separating from rest of text.

They truly need some TLC.

Additionally, a mechanism for handling the case in which the number of strips is higher than the space allows to stack them should be put in place.

One of the testers wrote to me:

It would be useful to allow the combination of LAND and SPEED commands

This is indeed a possibility, and I am looking forward for suggestions. At the moment the approach happens in 4 phases, and each of them must be successfully concluded for the plane to pass to the next one. The plane will abort the landing if it will find itself unable to complete any of the phases.

1. INTERCEPTING - The plane keeps current heading, altitude and speed and waits for the right moment to turn into the ILS projection on the ground (in other words: to be aligned with the runway --> same heading, foot of the runway straight ahead). The plane aborts if the ILS doesn't pass in front of its nose, or if the plane itself is too close to veer into the ILS (it would overshoot it)
2. MERGING - The plane maintain speed and altitude and veer into the ILS projection.
3. MATCHING - The plane maintain heading and speed, and adjust altitude to precisely fly along the ILS vector (the line starting from the foot of the runway and going up at 3° angle. The plane aborts if the plane is flying above the ILS and its speed is too high to lose altitude quick enough to intercept the ILS vector before the runway.
4. GLIDING - The plane follows the ILS vector maintaining speed until the moment comes to slow down to landing speed. The plane abort if at the beginning of the glide its speed is already too big for it to slow down to landing speed before the foot of the runway.

On landing and takeoff the runways must be busy for a little while.

Needed for alpha and beta testers

Pay attention to the screen format, as flight strips and/or airport maps might become warped / not readable.

Currently the maps over the sencond will go out of screen.

• Switching between None | Grid | Circles
• Varying the step
• Display scale value

Currently the config file allows testers to do various things that shouldn't be allowed to players in the release version:

• assigning custom points values
• choosing length of runway busy time

CLEAR

Will mark the plane busy until flown over a beacon.

Also trigger appropriate score event.

Heading should accept variations like:

>>> ABC1234 HEADING +15

or

>>> ABC1234 HEADING -30

• help
• pause
• sort flight strips
• list scenarios
• load scenarios

Issuing // on the command line will break the program.

• colour codes
• shapes

To implement helicopters two things are needed:

• Helicopter sprite
• Helipads modelling

Scores must be saved locally

This command would print to console the queue of commands for a given plane.

The idea would be that veering during the ILS alignment phase should happen at "expedite" rate (without fuel penalty) to simulate the sharp veering that often planes do before touching down.

update: it appears the expedite functionality is broken in normal veering too! :(

In said directory:

• Config files that override general setting
• Directory for user-generated / user-downloaded entity files
• Logs
• README.txt with basic info on the above

• Aeroplane model gives important information to the player about max and min speeds, max altitude etc...
• The /HELP command should probably be modified in order to provide this informations.

Present configuration makes impossible to use several runways simultaneously.

I've tried to find (from any Readme or docs) to run this game.
Is there anyone can shed me some lights here...

Thank you

Hello, I want to run the game but all the download link are offline.
Can someone help me?

Flight strips could have more useful information:

• Callsign?
• Indication of how close the plane is to declare fuel emergency?
• Expedite mode
• Emergency blinking light?

Make sure all screenshots and images are consistent with the released version of the game.

Cause tracked, needs some general rework of the way commands are executed.

It appears the calculation return double the distance.
Sprites appear to be correctly scaled, so the problem seems to be at math level.

Reported by Jack.