World Traffic 3 Update Page

MAC Users - Note that the Mac version does not run for many users for often more than about 30 minutes. 
If you find that it crashes, disable sounds from the World Traffic Preferences menu as there appears to be some type of sound conflict with the latest version of X-Plane.  You won't get any sound but at least it will run.  I'll have to rewrite the sound engine using a different sound API some time in the new year.


Notes for buyers:


Get the Quick Start guide below which includes setup instructions:  NOTE:  USE NEW INSTALLATION INSTRUCTIONS BELOW FOR AIRCRAFT AND FLIGHT SCHEDULES.  There is no more file as mentioned in the manual.  

Get the World Traffic Technical Manual below:
Technical Manual

See the excellent video tutorial on installation and setup here by Captain K-Man:
Video Tutorial


Get the World Traffic 3 installer for the PC using the link below.  Extract the installer from the zip file and run it.  The Mac version will be coming shortly with the linux version to follow in a few weeks.

Installers (Windows Only!):

WT3 Installer
- The full installer for WT 3.1.9
WT3 Updater - Run this to update to WT 3.1.9 only if you already have any previous version of WT3 installed.  See release notes below for changes.

Zip Files for Mac or Linux (or Windows if you're having problems with the Windows installer or updater or bogus complaints from virus scanners):

WT3 Full Package - Read the read_me.txt file for installation instructions.  
WT 3.1.9
WT3 Update - Downlaod this to update to 
WT 3.1.9 if you have any previsou version of WT3 installed.   Read the read_me.txt file for installation instructions.


Aircraft and flight schedules (formerly known as have been put together by this awesome group of people.  Get them all here after you have installed WT3:
Aircraft and Flight Schedules

Release Notes (see bug/feature list here for desrcription of bugs):   Bug/Feature List

3.0.1 - Added support for new serial number key
3.0.2/3.0.3 - Bug fixes to read serial number key correctly if there was no carriage return at the end of the line
3.0.4 - Bug fix for bug #3 - ground routes were not being generated for some airports and could only be generated a few times in a row before not working

3.0.5 Changes

3.0.6/3.0.7 Changes
3.0.8 Changes 
3.0.9 Changes 
3.0.10 Changes 
3.0.11 Changes 
3.0.12 Changes
3.0.13/14/15 Changes  - 3.0.15 - fixes the pause problem in 3.0.14
3.1.2 Changes  
This is a major update with some cool new features.  The manuals have all been updated so make sure to check out the applicable sections in the quick startup guide and the technical manuals.  First off, lots of code oprtimization has been done so that the AFRE_Real_Traffic region can now be used to provide real flight schedules without performance problems like the stutrers.  I'd recommend using this over the AFRE Thurrsday region or auto-generated traffic except for places in Asia and Africa where real flight schedules are missing lots of flights.

When using the AFRE_Real_Traffic region, now all aircraft positions can be determined precisely so you won't see incorrect planes parked at gates, planes being swapped out for others or appearing at empty gates if the airport layout is setup correctly.  You will now see planes parked as expected based on the real world flight schedules.  Since all AFRE flights have an aircraft tail number, the plane will land, park at a gate and the next departing flight with that same tail number will leave from the same gate.  Aircraft setup will take longer when you are creating flights as WT needs to look at every aircraft in the created flights to determine if the plane is in flight or to determine what airport it should be parked at.  You can still use auto-generated flights if you don't care about any of this and don't want to wait for aircraft positions to be determined.  

A description of the other new changes is below: 3.1.3 / 3.1.4 Changes  
3.1.5 Changes  
3.1.7 Changes  
3.1.9 Changes  


When departure ground routes are generated now, a ground route is generated to both the start of the runway (new) and to the displaced threshold (how it's currently done).  Now the ground routes going to the displaced threshold have the text DTHR added in the ground route name.  Most of the time, planes should take off at the beginning of the runway so you normally you'll want to delete the DTHR routes but they're there in case you want them.  For example at LIRQ, you will get two departure ground routes generated as follows:

The first one will have the plane taxi all the way up the start of the displaced threshold before taking off.  The second one will have the plane takeoff as soon as it taxis onto the runway.  You'd want to delete the first ground route normally.  As usual planes, still land on the displaced threshold so there are no separate arrival ground routes.