This page will detail any support issues arising from any of my projects
If you choose to install the files for the new ICAO codes at these airports, you should also remove any previous AFCAD files you may have installed for these locations.
Updated: 20/11/07
The readme.txt file is erroneously titled "set 15" but don't let that confuse you!
Updated: 25/10/07
In the readme.txt file, I neglected to mention why there are too separate files for Laarbruch AB. This is because FS2004 uses a different ICAO code to the one actually in use in the real world. You can install both without problem, and FS will use the one appropriate to your system, even if you have modified your files to use the current code.
Updated: 25/10/07
There is one additional object library that should be downloaded if you wish to see the scenery in its complete form. This is the Default Terminal Building Subset for EZ-Scenery by Sidney Schwartz and can be downloaded from AVSIM here.
Updated: 2/3/07
The aircraft shown as AC#45003 in the flight plans are all Fokker 50s.
This set contains two updates to Flight Simulator default files for "THAI"
and "CONDOR", both of which have distortion in Voice 8. Unfortunately,
the corrected files as supplied are configured as variations rather than
replacements and Flight Simulator will still randomly use the original
sounds amongst the changed ones. This can be corrected by the following:
Open the EditVoicePack software and navigate Custom Modifications > Callsigns
> Condor in the left margin. Tick the box in the top right corner marked
Force Variation. Repeat for THAI. Save the changes (Ctrl+S) and update the files
in Flight Simulator (Ctrl+U).
All reported issues with version 1 of my AFCADs have been resolved with the release of version 2. Please upgrade to the new files.
Reference to YBAN in the list of changed ICAOs in the document changes.txt should refer to YBEN. Omitted from the list is the change YGLO to YGLG.
The new set of files totalled 121 against the 122 in the original set. the missing one (YBA3) can be downloaded here.
It is noted that part of the runway at YBI2 Boston Island appears to be in the sea. This would appear to be a coastline error on the part of Microsoft (the sea is actually 40 feet ASL for a little way offshore until it suddenly slopes away). This is a matter for either the scenery designer or Microsoft to resolve, but I have disguised it a little by creating a little grass alongside the runway.
Fixes for YADG Aldinga, YMWS Moolawatta Station and YWMC William Creek required for version 1 of my AFCADs are incorporated in version 2. Please upgrade to the new files if you experience problems.
It would appear that at some stage the scenery that these files are designed for (fs9savv1.zip at Flightsim.com) has been updated (savfs9v2.zip at Flightsim.com) although I have not identified anything that affects my files.
There is a problem with YWUD Wudinna where one runway (18/36) hovers at about 600 feet above the airport. This is not actually a fault with my files but seems to be with the scenery itself. You can fix this by removing the file Wudinna.bgl .
A problem exists at YBOV Border Village where the airstrip is located on a high plateau at around 1100 feet when the surrounding landscape is about 800 feet below. Again, this appears to be a fault with the scenery itself and not with my files. This can be fixed by removing the file Border Village.bgl and also replacing my file AF2_YBOV.bgl with a new file which can be downloaded here. This changes the airport elevation to 310 feet ASL which may or may not be true to the real world but makes it more realistic for Flight Simulator. If routing AI traffic to this airstrip, please make sure your airports file shows the elevation as 310 feet to avoid missed approaches.
There may be other locations where airfields appear to be on elevated or sunken land. Many of these problems vary according to whether you are using the Flight Simulator default mesh or one of the more accurate add-ons available, although sometimes even the latter seem to disagree on the correct height of surrounding land! Whilst I will try and fix major problems of this sort, please do bear in mind that the issue is really with the scenery itself and not with my supplementary files.
Please note that I presently do not offer support for any of these projects for use with Flight Simulator X. Some may work - most will not.
Until such time as I have have a good reason to upgrade my hardware and operating system to the levels required to run Flight Simulator X at an acceptable level I have no plans to purchase it. Which means I cannot test my projects to see if they will work. Sorry!
Then please contact John Hinson using the form below.