FSX Kandahar Scenery
- Download hits
- Microsoft Flight Simulator X (FSX) including Steam Edition & Prepar3D (P3D)
- File size
- 37.85 MB
- Virus Scan
- Scanned 29 days ago (clean)
- Access to file
- Free (Freeware)
- Content Rating
Kandahar v1. Kandahar, Afghanistan. Kandahar (OAKN) is for FSX with Acceleration running in DX10 or DX11. Version 1 is an extensive and detailed version of the busiest single-runway airport on the planet. Parking spaces include four cargo, 11 military cargo, 69 military combat (17 coded for A10s), two Ariana Afghan Airlines spaces, 79 Heli Traffic 2009 compliant helicopter landing spots, and a fuel space that can fit a 747. By Dan Mesmer.
IMPORTANT SPECIAL NOTE:
Although Kandahar can be used by itself, Bagram AFB (bagram_ver_3.zip) is being released concurrently with Kandahar Ver 1. It makes sense to download and install both airports so that AI flights can be set up between the two airports. This is particularly true for Heli Traffic 2009 users, since Kandahar has 79 helicopter landing spots, and Bagram has 65 helicopter landing spots. The helicopter landing spots at both airports are intended for use with Heli Traffic 2009.
HELI TRAFFIC 2009 USERS:
To avoid seeing civilian helicopters at Bagram, Heli Traffic 2009 users should go to Heli Traffic 2009's "Options," and move the "Random traffic density" slider to "0%." Then set up some AI helicopter flights to and from Bagram using only military helicopters.
1. Copy the "Kandahar Ver 1" folder (including the folder, itself) to the FSX "Addon Scenery" folder.
2. In FSX, go to "Settings," and under "Other settings," click the "Scenery Library" button.
3. On the "Settings - Scenery Library" window, click the "Add Area" button.
4. Navigate to the "Addon Scenery" folder, and then double-click on the folder to open it.
5. Click once on "Kandahar Ver 1," and click the "OK" button. (After clicking the "OK" button, Windows 7 users will also need to click once in an empty space below the folder names in the "Select Scenery Directory" window).
6. Under "Available scenery areas," "Kandahar Ver 1" will now appear at the top of the list. Be sure "Enabled" is checked. Then click the "OK" button.
I suggest turning off ground scenery shadows to reduce texture flickering.
Setting weather visibility at 10 miles will enable FSX to show Kandahar as it is often seen in photos and videos. Kandahar is in a semi-arid region, and the air is often full of dust. There are times, though, when visibility is nearly unlimited. Of course, there are also times when a sand storm hits the airfield, and visibility goes down to only a few feet.
A scenery complexity setting of "Dense" or higher shows everything. A setting of "Normal" blocks display of some of the open hangars, but everything else is displayed. Settings of "Sparse" and "Very Sparse" show significantly less.
Open the "Helipad Reference" folder, and double-click on "Helipad Reference.htm." This is a visual reference to be used in setting up both user helicopter and AI helicopter flights. All helipads at Kandahar are shown, and both the FSX and the Heli Traffic 2009 helipad numbers are shown for each helipad. The location and heading of each helipad is based upon satellite imagery.
The "Slingload Flight" folder contains files to implement a slingload flight. Copy the files (but not the folder itself) to the "Flight Simulator X Files" folder within your "Documents" or "My Documents" folder. A flight called "Kandahar Sling" will now be listed on the FSX Free Flight's "Load Flight" menu. The flight uses an AgustaWestland EH-101 that takes off from helipad 36. The slingload is a pallet of boxes that is located at the opposite end of the airfield near helipad 32 in a portion of the airfield that is used by the Afghan Air Force (AAF). Do whatever you wish with the pallet of boxes, but watch out for the power lines.
Kandahar Ver 1 contains 17 parking spaces coded for A10 "Warthogs." There is a freeware file called "hoga10.zip" that is available at FlightSim.com and elsewhere. The file contains a freeware A10 that can be used both as a user aircraft and as an aircraft for AI flights.
The files in the "A10 Enhancements" folder contain texture conversions that I have done to add DirectX 10 and DirectX 11 compatibility and, therefore, enable the A10 to render properly in FSX's "Preview DirectX 10" mode. I have made no changes whatsoever to the original model nor to the livery. I have simply converted the textures for use with DX-10 and DX-11, and I have saved the textures using DDS compression to make rendering faster.
To use the textures, download and install the files contained within the hoga10.zip file. Then copy all of the files with a .dds extension from my "A10 Enhancements" folder to the "texture" folder within the installed A10's "358th FS A-10 ThunderboltII" folder. Delete all files with a .bmp extension from the same A10 "texture" folder.
To enable AI A10s to find and use the A10-coded parking spaces at Kandahar, copy the "Aircraft.cfg" file from my "A10 Enhancements" folder to the "358th FS A-10 ThunderboltII" folder, overwriting the original file. The only difference in the files is that I have added the line "atc_parking_codes=A10" (without the quotes) to the "[fltsim.0]" section of the Aircraft.cfg file. The same technique could be used in the aircraft.cfg file of any A10 to enable the A10 to use the parking spaces that are coded for A10s at Kandahar. Just be sure to use "A10" with no dash between the "A" and the "10" if you use the technique with an A10 that you already have in your FSX hangar. Remember, too, to add the same line to each texture referenced within your aircraft.cfg file if your A10's aircraft.cfg references more than one texture.
An IED has hit a vehicle on a road outside the airport. It's not the highway that runs by Kandahar's gate, but a road that is a bit more distant. Flying a helicopter on a heading of 80 degrees from near the center of the airfield will bring smoke into view. Continue flying toward the smoke to see the aftermath of the explosion.
While I was developing Kandahar, some real-world tanker trucks came under attack in Pakistan. That prompted me to add a tanker truck that had been attacked. I allowed my tanker truck to make it into Afghanistan, but it is closer to the Pakistani border than it is to Kandahar. The aftermath of the attack can be seen at N 31° 9.84' E 66° 9.03'. The tanker truck can be found by using the highway that runs by Kandahar's gate as a visual reference. Follow the highway south, and eventually you will come across the tanker truck.
I have already created a Heli Traffic 2009 landing spot at the site of the tanker truck attack (and at other remote Afghanistan sites) for use by AI helicopters. If a Heli Traffic 2009 flight is scheduled using the attacked tanker truck's landing spot, then it would also be possible to find the location of the attack by following the AI helicopter from Kandahar to the tanker truck. See "QUICKLY ADD A SET OF REMOTE AFGHANISTAN LANDING SPOTS TO HELI TRAFFIC 2009."
QUICKLY ADD A SET OF REMOTE AFGHANISTAN LANDING SPOTS TO HELI TRAFFIC 2009:
The files AfghanistanLandingSpots.txt and AfghanistanLandingSpots.xml in the "Additional Afghanistan Landing Spots for Heli Traffic 2009" folder contain additional helicopter landing spots to supplement the landing spots that already exist at Afghanistan airports. In some cases, these Heli Traffic 2009 landing spots add spots to Afghanistan airports that previously had no helicopter landing spots. In most cases, though, the additional landing spots are located outside of airports in relatively remote areas. Most of these remote landing spots use the ICAO code of the nearest airport as part of the landing spot name.
Remote landing spots have been associated with airports having the following ICAO codes:
Adding these remote Heli Traffic 2009 landing spots provides additional realism, since real-life helicopters do more than fly between airports. The remote spots also enable Heli Traffic 2009 schedules to be created that result in seeing AI helicopters departing airports on a variety of headings.
There are two options for adding the additional landing spots.
1. TO MAINTAIN A SINGLE XML FILE FOR ALL HELI TRAFFIC 2009 LANDING SPOTS:
Open the AfghanistanLandingSpots.txt file in a text editor, and copy the entire contents. Open the HeliTraffic-MyData.xml file in a text editor (the default location for the HeliTraffic-MyData.xml file is the Heli Traffic 2009 folder within the Documents folder), and paste the previously copied contents just above the last line in the HeliTraffic-MyData.xml file. (The last line is ""). Save the modified file, and make sure it has an .xml extension.
2. TO USE A SEPARATE FILE FOR THE ADDITIONAL LANDING SPOTS:
Copy the AfghanistanLandingSpots.xml file to the Heli Traffic 2009 folder within the Documents folder. Be sure to copy the .xml file rather than the .txt file.
TAKE A DRIVE:
This is a great airport to drive. There are openings in all the fences so you can drive everywhere, and there are many details that are likely to be seen only by taking a drive through the airfield. Additionally, as is the case in real life, there is a perimeter road. A drive around the entire perimeter makes one aware of just how large Kandahar Airfield is.
A great vehicle to use in driving Kandahar is the freeware Humvee by Bruce Fitzgerald. It is available from FlightSim.com. There are two files to download and install. Download and install humvee.zip and hmvupd.zip. Be sure to install the contents of humvee.zip before installing the contents of humvupd.zip.
Q & A
Q: Why all the power lines?
A: One of the first things that struck me when first researching Kandahar is that there are power lines everywhere. Apparently, it takes a lot of power to conduct a war.
Q: Why all the stuff setting around outside buildings?
A: Because, at the real airfield, photos show hundreds of times more stuff setting around outside buildings, and I thought I should at least show some of it.
Q: Why doesn't the main terminal look like the real-world main terminal?
A: Because I chose not to take the time to model the main terminal. I may do so later, though, and add a realistic model of the terminal to a future update of the airport.
Q: Why does the alignment of the trees appear to be artificial?
A: Most of the trees at Kandahar airfield were planted. There has been an international effort over the years to help Afghanistan recover from decades of deforestation.
Q: Where's the static A-10?
A: It's in "an undisclosed location."
Q: What aircraft are seen at the real-world Kandahar?
A: Here's a list of most of the aircraft that are likely to be seen at Kandahar:
C-130 Hercules (various liveries)
C-17 Globemaster III (USAF liveries)
F-16 Fighting Falcon (Royal Netherlands Air Force livery)
Harrier (RAF livery)
A-10 Thunderbolt II ("Warthog") (USAF liveries)
Antonov AN-32 (Afghan Air Force livery)
Boeing 727-200 (Ariana Afghan Airlines livery)
Airbus A300 (Ariana Afghan Airlines livery)
Airbus A310 (Ariana Afghan Airlines livery)
MQ-1 Predator UAV (USAF and CIA)
V-22 Osprey (USMC liveries)
A variety of helicopters.
Q: One of the accompanying screenshots shows Predator UAVs parking in specific hangars. What has been done to reduce the likelihood that other aircraft will use those hangars?
A: Although the parking spaces in the hangars used by Predators are not coded specifically for Predators and, therefore, have the potential for use by other aircraft (for users who do not have a Predator model), most aircraft will find other spaces to be more attractive and will stay away from the Predator spaces. This is true because military cargo aircraft will seek military cargo or cargo spaces, A-10s will seek the spaces coded specifically for A-10s, and military combat aircraft will seek the military combat spaces that have a 7-meter radius rather than the larger 8-meter radius spaces that the Predators need because of their wingspan. If a military combat aircraft were to use one of the Predator spaces, most likely it would be either because the aircraft's wingspan would not allow it to park in a 7-meter space or because there were no more 7-meter spaces available.
Q: I've downloaded and installed your version of Bagram AFB, but there isn't any Predator-specific parking area at your version of Bagram. Where should I send Predator UAVs?
A: Because it has sufficient aircraft parking, and to avoid seeing Kandahar Predators flying into Bagram, I suggest you make Jalalabad (OAJL)the destination for Predators flying out of Kandahar.
Q: Why do some scenery objects disappear at night?
A: Because the freeware developer provided no night textures, because I felt the scenery object was important enough to use even though it would not be seen at night, and because I decided seeing the object at night was not important enough to take the time to add a night texture. One exception was the checkered water tower, where I did take the time to produce a night texture.
SPECIAL THANKS TO-
Jon Masterson and team for developing Airport Design Editor FSX Edition (ADE9X v.1.47.07). Copyright 2007-2011 ScruffyDuck Software.
Jim Dhaenens for allowing freeware airport developers to use his radar, hangar and lights models.
David Grindele for his accumulation of freeware scenery.
Guy Diotte for the static A-10 Thunderbolt II ("Warthog").
Digital Globe for providing satellite imagery.
Google for providing access to Digital Globe imagery via Google Earth.
Islamic Republic of Afghanistan Ministry of Transport and Civil Aviation for publishing detailed information about the airport.
This software is freeware and may be distributed only with permission of the author. No commercial use is allowed without the author's permission.
This software is distributed without warranty of any kind either express or implied. The author is not responsible for any damage caused by this software.
The archive kandahar_ver_1.zip has 118 files and directories contained within it.
This list displays the first 500 files in the package. If the package has more, you will need to download it to view them.
|Filename/Directory||File Date||File Size|
|A10 Enhancements||03.10.11||0 B|
|Additional Afghanistan Landing Spots for Heli Traffic 2009||03.11.11||0 B|
|Helipad Reference||03.07.11||0 B|
|Helipad Reference.htm||03.07.11||2.64 kB|
|Kandahar Ver 1||03.07.11||0 B|
|A10 library.bgl||01.13.10||840.59 kB|
|ez-fuel tanks.bgl||06.14.06||2.35 MB|
|Water Tower 3 RedWhtCheckered.bgl||08.03.10||11.38 kB|
|A10 GREY.bmp||01.13.10||682.75 kB|
|propane 2.bmp||06.13.06||32.07 kB|
|Behind the Northeast Flight Line.png||02.06.11||790.19 kB|
|Bell 212s on Stallion Ramp.png||02.07.11||768.10 kB|
|C-130J Taxiing After Sunrise.png||02.26.11||661.69 kB|
|C-130s on Whiskey Ramp.png||02.05.11||953.96 kB|
|Canada Provides Airport Administration.png||02.10.11||965.93 kB|
|Forklift with Pallet.png||02.10.11||990.38 kB|
|Guard Tower.png||03.10.11||807.24 kB|
|Helicopters Early Morning.png||02.20.11||767.78 kB|
|Helipad 36 at Dawn.png||02.03.11||715.52 kB|
|Kandahar After Daybreak.png||02.06.11||914.13 kB|
|Kandahar After Sunrise.png||02.10.11||775.48 kB|
|Kandahar from Southwest Corner Near Sunset.png||01.31.11||710.80 kB|
|Kandahar Medivac.png||02.06.11||780.12 kB|
|Kandahar Preview 2.png||02.07.11||1023.62 kB|
|Kandahar Preview.png||02.06.11||945.27 kB|
|Morning Landing on Rwy 23.png||02.02.11||673.99 kB|
|Near Sunset at Kandahar.png||01.31.11||859.75 kB|
|Phone Call at Dawn Closeup.png||02.06.11||592.75 kB|
|Pickup with Cargo.png||02.09.11||964.99 kB|
|Predator Hangars.png||02.02.11||1.08 MB|
|Predator on Taxiway F.png||02.03.11||599.33 kB|
|Rare Rain at Kandahar.png||02.10.11||875.73 kB|
|Rare Rain.png||02.07.11||1.31 MB|
|Return at Sunset.png||03.02.11||695.39 kB|
|Rwy 23 at Dawn.png||02.02.11||680.72 kB|
|Tanker Truck Hit Near Pakistani Border.png||02.03.11||1.41 MB|
|View from a Hangar.png||02.10.11||732.80 kB|
|Slingload Flight||03.10.11||0 B|
|IFR Kandahar to Bagram Helicopter.PLN||01.24.11||1.45 kB|
|Kandahar Sling.FLT||03.02.11||11.52 kB|
|Kandahar Sling.FSSAVE||03.02.11||93.92 kB|
|Kandahar Sling.SPB||03.02.11||420 B|
|Kandahar Sling.WX||03.02.11||151.53 kB|
|Go to Fly Away Simulation.url||01.22.16||52 B|
Complementing Files & Dependencies
This add-on mentions the following files below in its description. It may be dependent on these files in order to function properly. It's possible that this is a repaint and the dependency below is the base package.
You may also need to download the following files:
Installation of Add-on Aircraft/Scenery
Most of the freeware add-on aircraft and scenery packages in our file library come with easy installation instructions which you can read above in the file description. For further installation help, please see our Knowledge Center for our full range of tutorials or view the README file contained within the download.