Military AI Works

Hi, I just want to ask how to make ai do double takeoff and landing? I have seen many screenshots in Screenshots Forum are doing double takeoff or double landing. Could you help me?

Here is a quick answer. I'm no pro at this so I'm sure someone will chime in.

You must use 2 AFCADS. 1 overlays the other. Each having the runway off center from the scenery. Each aircraft uses a separate AFCAD to simulate the formation take off and landings.
Your flightplans must also reflect the 2 different AFCADs to make this happen.

Than you very much,Kevin. I'll give a shot.

Have a look at this package.

http://library.avsim.net/esearch.php?Ca ... DLID=81318

It will give you some more help on timing and double AFCADs. At least it helped me to understand it

Thanks, guys. But I still don't get it. I tried but the strange thing is there are 2 aircrafts park in 1 parking. What's the problem?

I'm not one of the guru's either, but I know the general answer to this. Each AFCAD must have only 1/2 of the parking spots,, alternated each second parking space with the one's from the other AFCAD. For example for the first AFCAD, you would have parking spaces 1,3,5,7 and so on. For the other AFCAD you would have parking spaces 2,4,6,8 and so on. You will have only 1/2 of the spaces on each AFCAD, but together the spaces will still equal all of the spaces.

Hope that helps.

Ron

Well, that's one way to do it, of course.
But the reality is that either afcad can have as many or as few parking spaces as one wants - so long as they don't overlap or occupy the same physical space in the FS world.

The way I accomplish this, myself, is to:
1. Start with/design a single afcad designed with ALL parking spots for the airport, both military and civilian.
2. Save this afcad as "wherever.original".
---This both provides a backup and something needed for step 4.
3. Delete parking spaces to create "parking groupings"
4. Save that as "wherever.1" leaving the civilian parking intact.
5. Reload the "wherever.original" afcad
6. Delete parking spots which I had left in place for "wherever.1"
------ This creates a "mirror image" of the parking for "wherever.1" in the same FS physical world,
7. Save this afcad as "wherever.2"

By using "wherever.1" and "wherever.2" I don't risk overwriting the original or duplicating another afcad already in my system.

8. Now, rename the 2 afcads to whatever "works" for me - ex., AF2_KSTL.bgl might become AF2_STL1.bgl and AF2_STL2.bgl ---- or, more likely AF2_KSTL.bgl with all the civilian parking and AF2_STL1.bgl with the "mirror image" parking.

9. Adjust flightplans using KSTL as a destination or departure location to reflect KST1 and/or 2.

What I've left out is that you can delete entire taxiways, apronways, vehhicle paths, etc. from either afcad. The "paired runways", I draw on the "wherever.original" afcad before saving and then delete appropriately when I get to "wherever.1" and..2 as I'm cleaning things up. You can and probably should adjust the comms for 1 of the afcads.

Obviously, other people may do things differently, possibly even more efficiently. My method works for me.

What I've left out is that you can delete entire taxiways, apronways, vehhicle paths, etc. from either afcad

Does that means we have to clean up the taxiways, apronways,etc. surface or the taxiways,etc. lines?

Well, "have to"? No.
But if you have 2 taxiways (or whatever) occupying the same physical space (but not quite) in the FS world, you could end up with 2 visual representations of a single taxiway. By making th eoriginal as accurate as possible and then deleting things, I don't need to make any geographic adjustments other than through deletion and I maintain" "the calibration" or location accuracy.

That's why I start with a single afcad, design it to the hilt (including navaids, airport vehicle pathways, closed taxiways, etc.), and then delete parts from it that will be used solely in "afcad.2". The second afcad is, for me, a limited version of the complete original afcad and contains only those things which I want - usually far less than half the parking, only the absolute minimum in terms of taxiways necessary to get the traffic to and from those parkings spots and the runways, no "just for the visuals" taxiways (representing airport vehicle paths, for example), etc.

In my system or method, afcad 1 contains all the hardstands for both afcad 1 and 2; afcad 2 has ZERO polygons representing hard surfaced parking areas - only parking spots.

Otherwise, afcad 2 must be completely self-sufficient in terms of functionality, but winds up being "much less" in terms of visual appeal within the FS world.

Remember that there is a significant distinction between ai/atc functionality and visual appeal/function. Consider that: any aircraft can parking at a parking spot made of any surface type other than water; only amphibious/float enabled aircraft can park at water surfaced parking spots; float enabled fixed-wing aircraft without wheels can't move from non-water parking spots. See what I mean?

Yes, Ford. Now I get it. And thanks to all too for helping me out. I'll try it and I hope I can post a screenshot