AI, Runway, and AFCAD issues...

[Wingding]

Ok, after building a new PC and reinstalling all my fav software, I'm at the stage of tweaking my FS9 back to how I like it. This time, I'm going with WOAI and so far, I'm loving it. BUT....

I've rebuilt KLAS/McCarran with excellent parking and configured the different runways for smoother AI and ATC operations, but I'm coming across a glitch that I can't fix. Here's the deal:

25L and 25R are working just fine, but 19L and 19R are a different story. I have closed 19L for landings, but AI continue to use it. I worked several hours yesterday on the issue and now I want to continue working on it. I set the user-defined weather to blast wind at 26kts from 190*, but all the AI are all using 25L/R for takeoff/landings, even with the hellacious crosswind. What gives? Why won't ATC start using the "longest active runway with a heading closest to that of the wind direction" (as described in various SDK's and programming manuals)? Any ideas?

[ReggieF5421]

Why won't ATC start using the "longest active runway with a heading closest to that of the wind direction" (as described in various SDK's and programming manuals)? Any ideas?

By closing 19L for landing, did you also close 1R?

I'm assuming that you have setup an x-wind runway pattern so that all runways are active at the same time.

If so, the system thinks the 25 runways are parallel to the 19 runways. Takeoff aircraft will use the takeoff runway with a center point closest to the AI aircraft when it calls for taxi instructions.

If you do not have a x-wind setup, the 19 runways will almost never have priority over the 25 runways. The 25 runways have ILS approaches. There are only GPS and RNAV approaches to the 19 runways. Non-parallel runways need a very high wind factor before the weighting calculations will over rule ILS approaches. Most of the testing I've seen done indicates it takes above 64 knots of wind to give the non-parallel runway a high enough score to be the active runways.