4 minutes ago, Christopher Low said:

I have never seen an AI plane turn left after landing on 23R, so that is a bit of a mystery. To be honest, when I saw your screenshot, the only conclusion I came to was that the TUI plane must have landed on 23L!

I might restore the supplied AFD and see what changes.

1 minute ago, Christopher Low said:

On a side note.....my cousin was at Manchester a couple of weeks ago, and he told me that two planes landed on 23L, even though 23R was fully operational

That might have been a historic Dakota which had an engine fail and landed on 23L for operational reasons.

No, I am pretty sure that it was two airliners.....and very close together.

1 minute ago, Christopher Low said:

No, I am pretty sure that it was two airliners.....and very close together.

Okay, that's unusual.

Quick Question: Where do I go to access the utility to tell P3D AI what runway to use?

1 minute ago, SKEWR said:

Quick Question: Where do I go to access the utility to tell P3D AI what runway to use?

Not sure what do you mean..

S.

3 minutes ago, SKEWR said:

Quick Question: Where do I go to access the utility to tell P3D AI what runway to use?

You need to use a utility like Airport Design Editor to change the AFD file parameters, and that includes setting up runways for landings and take offs.

14 minutes ago, SKEWR said:

Quick Question: Where do I go to access the utility to tell P3D AI what runway to use?

In short, you can’t. That is determined internally by P3D if more than one runway is available for the current wind conditions.

Thank you for the replies and clarification. I thought there was a way to manage AI runway selection in P3D. I misread. 

 

8 hours ago, Pete Dowson said:

I've never noticed a problem at EHAM? I thought I only had the one AFD BGL.

The one that's always bugged me is EHAM, where the South and North runways conflict. This change certainly fixes that with one AFD BGL now.

Pete

 

 was thinking of how FlyTampa EHAM has five different AFCAD's you can select through their configuration depending on wind direction since EHAM doesn't just use different sets of parallel runways.  I think KBOS has something like that too.

10 hours ago, regis9 said:

 was thinking of how FlyTampa EHAM has five different AFCAD's you can select through their configuration depending on wind direction since EHAM doesn't just use different sets of parallel runways.  I think KBOS has something like that too.

Ah, I see. Yes, possibly. That's more to do with realism than conflict resolution, excepting of course in zero or very light winds. Everything goes awry then as the AI go every which way left to themselves. (This is why Active Sky has, or at least had (?), a minimum surface wind speed option).

Pete

 

I’ve solved the problem of landing Ai exiting left on 23R at EGCC when they should exit right. P3D will use the first exit point and it so happens it’s that one. I’ve deleted it and now Ai exit to the right as they should.

I’ve also changed 23R to landing only as no Ai were being directed to 23L despite it being available. Maybe that’s something LM could look at.

I’ve changed LEMD and now have landing on 18L and 18R with departures using 14R. Result! 😊

It seems arrivals can use two runways but departing cannot.

2 hours ago, Ray Proudfoot said:

It seems arrivals can use two runways but departing cannot.

I think they just use the nearest valid runway (not necessarily nearest threshold). I can understand why it might be programmed that way.

Pete

 

8 minutes ago, Pete Dowson said:

I think they just use the nearest valid runway (not necessarily nearest threshold). I can understand why it might be programmed that way.

Pete

I've been monitoring LEMD and departing were using 14L and 14R. Bigger airport and two terminals so that could explain why. Do you think that's something that L-M might look at and tweak? Or is it far more than a tweak?

1 hour ago, Ray Proudfoot said:

Do you think that's something that L-M might look at and tweak? Or is it far more than a tweak?

The "fix" they've done in HF2 is really just a bug fix. As the scenery SDK has always allowed different settings for either end of a runway, it was always a bug that only the primary setting was being used.

Enhancing the way ATC directs traffic is an entirely different matter. A random choice of runway would not seem appropriate, which might otherwise seem easiest, but an intelligent one based on direction of travel after takeoff and numbers waiting for each runway, would need to be considered part of a general overall update to AI control.

I think that this will be best dealt with for the time being by third party add-ons, like, hopefully, the one being developed by Simbol.

Let L-M concentrate on graphics and performance. I personally am eager for improved multiple scenery window performance. More threading and a consequent better spread of core usage would be a good start I feel.

Pete

 

Hi Pete,

Fair points. Although I don't have multiple screens so wouldn't benefit from those type of changes will help others. Looking forward to meeting @simbol for a chat about Ai. I'm thinking about disabling 05R EGCC for landings as it's so far to the first exit even other Ai 3-4 miles behind are performing go-arounds.  Not good.