• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

FSXA Helipad

Yes, just read the manual about helipads. Then you can fly a chopper onto that pad. You cannot use helicopters nor helipads for AI traffic.
 
There's a 3rd party program called Heli Traffic 2009 from Flight1 that will do heli AI traffic and you can create a traffic file for your airport in case anyone has both that and your airport but as far as default FSX AI goes, what tgibson said
 
Since Heli Traffic 2009 is an extremely popular program, I wanted to make a point to airport developers who substitute one of their own custom helipads for one of the default FSX helipads. One would think that a custom helipad, a helipad start, and a helicopter scheduled to use the helipad would be all that Heli Traffic 2009 would require to use a custom helipad for AI helicopter traffic. That is not the case. Enabling Heli Traffic 2009 to use a custom helipad requires that one of the default FSX helipads be placed beneath the custom helipad. Without an accompanying default helipad, Heli Traffic 2009 users would have to land (or place using the FSX menu) a user-piloted helicopter (or other user-piloted aircraft) at the custom helipad, and they would have to tell Heli Traffic 2009 that the location of the custom helipad (the current location of the user aircraft, really) is a helicopter landing spot. Both of the preceding steps are steps that shouldn't be necessary for Heli Traffic 2009 users, and the steps can be avoided easily by making sure that any and all custom helipads at airports are accompanied by a default FSX helipad. Just locate the custom helipad slightly above the default helipad to assure the default helipad's textures are not revealed.

NOTE: I define "default helipad" as being the same as one of the four FSX helipads available via the Airport Design Editor add-helipad function. The four available are: H, Square, Circle, and Medical. In other words (and for example), even with one of the FSX starts and FSX lighted helipads present, the placement of an H, Square, Circle, or Medical helipad is required beneath the lighted helipad to enable use of the helipad for Heli Traffic 2009 AI helicopter traffic. Heli Traffic 2009 sees any helipad that is not a default FSX H, Square, Circle, or Medical helipad as being a custom helipad, and Heli Traffic 2009 knows nothing about custom helipads.
 
Last edited:
Or, you can just make sure to include your landing spots data file with the release. This can be placed in the user's HeliTraffic user files folder using an installer or just have extra instructions in the ReadMe for users to copy that file to the location.

I'm not saying this way is better, just another option
 
Also worth mentioning is that airport developers who are developing with Heli Traffic 2009 in mind should be aware of the fact that Heli Traffic 2009 uses a helipad numbering scheme that differs from FSX. Whereas FSX uses the helipad numbers that were assigned when the airport was created, Heli Traffic 2009 assigns helipad numbers based upon the order in which the helipads appear in the file. If there is only one helipad at an airport, of course, this creates no problem. However, when there is more than one helipad at an airport, there can be one or more mismatches between Heli Traffic 2009 helipad numbers and the numbers that were assigned to default FSX helipads. Do the following to determine if any mismatches have occurred:

Open the airport's xml file, and make sure the order in which the helipads are listed in the file correspond to the FSX helipad numbers that were assigned. If all correspond, then there will be no mismatchs between the helipad numbers that Heli Traffic 2009 assigns to the helipads and the helipad numbers that were assigned when the FSX helipads were added to the airport. However, if one were to find that FSX helipad 3 (for example) was not the third helipad listed in the file, then it would be necessary to cut and paste the code for it into third position in the xml file. Make similar changes for any other mismatches. When all helipads are in correct order, do a final xml to bgl compile.
 
Last edited:
You must log in or register to reply here.
Back
Top