- Messages
- 26
Hello All,
my problem with AI this time is about forcing AI planes to land on a specific runway, and take off in the opposite direction.
Here is what I am trying to achieve
(in fact, I have achieved it on a test airport, but not where I really want it):
What I have tried:
The weird thing is that I have tried the same with another fictitious airport elsewhere (on land), and there everything worked fine.
Apparently just the "blocking" in the runway properties was enough to force landings on one runway only, even if that meant a 10 kn tailwind...
(The fake ILS approach there also worked; it was used to make a curved approach.)
Correction: On next test, the same problem at this airport: AI (IFR flights) land on R09 even though the only available (fake) ILS approach is ILS27, and R09 is blocked for landings in runway properties. Even when there is no wind.
My question:
Cheers,
Martin
my problem with AI this time is about forcing AI planes to land on a specific runway, and take off in the opposite direction.
Here is what I am trying to achieve
(in fact, I have achieved it on a test airport, but not where I really want it):
- fictitious airport (actually seaport on a lake, but runway and taxiways are concrete),
so conflicts with Stock airports are not an issue. - single runway 04/22
- the snag: there are mountains to the NE, therefore:
- all landings must be on R04
- all take-offs must be on R22
- winds are assumed to be calm, so tailwind etc is not an issue
- weather could be VMC or IMC (but no wind)
- user aircraft requirements can be ignored
- runway and taxiways are properly connected etc (OK as per ADEX Fault Finder).
- an appropriate parking spot is available.
- only one (fake) ILS approach created, for R04.
- there is only one flightplan (AIFP3) for one aircraft; this flight is set up to be IFR
What I have tried:
- made an ILS approach (in ADEX) only for R04 ;
My understanding is that this should then always be used for AI at top priority, regardless of weather;
and certainly so for all AI IFR flights. - set runway properties in ADEX so that R22 is blocked for landings, and R04 is blocked for take-offs;
- shifted the IAF so that the AI aircraft does not have to overfly the whole airport first to reach the IAF
(and thus might be tempted to use the more direct R22 instead of going the long way round to R04, as per ILS approach), - tried two different aircraft, in case it has anything to do with a/c performance;
- split the airport BGL into two, one of which (airport scenery etc) going to the Addon Scenery folder,
the other (which includes the ILS approach) going to Scenery\Global\scenery (as seen in Jim Vile's examples)
Apparently just the "blocking" in the runway properties was enough to force landings on one runway only, even if that meant a 10 kn tailwind...
(The fake ILS approach there also worked; it was used to make a curved approach.)
Correction: On next test, the same problem at this airport: AI (IFR flights) land on R09 even though the only available (fake) ILS approach is ILS27, and R09 is blocked for landings in runway properties. Even when there is no wind.
My question:
- Which other factors can cause an AI aircraft to completely ignore the sole ILS04 approach coded (via ADEX) in the airport BGL,
and land in the opposite direction (R22) which should be blocked for landings anyway via ADEX runway properties?
Cheers,
Martin
Last edited: