OnCourse Software

Is this something that I can minimise with different settings somewhere? I do occasionally get ATC permission to cross runways as I approach them, but most of the time AI traffic seems blissfully unaware of my presence. TGS seems to work, but too often it's too late - aircraft often don't stop until after they have 'hit' me.

AI traffic crosses runways I have just landed on (so I end up going right through them) or taxi across runways I have been given take-off permission for (again, no choice but to hit them when I am already'on a roll'). The issue of being given take-off clearance with other traffic still on the runway has already been discussed and I do tend to wait until a runway is clear before I enter it, permission or no, but that doesn't help with all these runway incursions.

How far is the AFCAD responsible for this? - I am sure that there is only so much that PF3 can do to stop this kind of thing, but it does seem a bit too frequent at the moment, so if I am able to tweak anything myself, that would be good...

Many thanks.

martinlest wrote:

Is this something that I can minimise with different settings somewhere? I do occasionally get ATC permission to cross runways as I approach them, but most of the time AI traffic seems blissfully unaware of my presence. TGS seems to work, but too often it's too late - aircraft often don't stop until after they have 'hit' me.

AI traffic crosses runways I have just landed on (so I end up going right through them) or taxi across runways I have been given take-off permission for (again, no choice but to hit them when I am already'on a roll'). The issue of being given take-off clearance with other traffic still on the runway has already been discussed and I do tend to wait until a runway is clear before I enter it, permission or no, but that doesn't help with all these runway incursions.

How far is the AFCAD responsible for this? - I am sure that there is only so much that PF3 can do to stop this kind of thing, but it does seem a bit too frequent at the moment, so if I am able to tweak anything myself, that would be good...

Many thanks.

Do you have the Conflict Monitor set to 'ON' ? Check Options #1, Advanced Options

Yes, that box is checked.

I wonder if part of the problem is that PF3+CM has a hard time controlling AI Traffic at complex airports, such as FSDreamteam's Chicago O'Hare, where there is a 'star' AFCAD and traffic is using all the runways (more or less). Or is that not really relevant? Certainly seems more of an issue at the bigger airports.

Thanks.

Well yes, the larger the airport you will have more AI traffic. If you were able to monitor the Ai using something like FSC you will see the AI that are being frozen to prevent incursions

FSC?

Well, whatever, AI traffic does all too often cut across runways I am just taking off from or landing at, making it hard to avoid 'collisions'. I'll keep an eye out whether this is only at larger airports - maybe some AFCADs aren't easy for FS9/PF3 to deal with from this respect (I'm not saying this is a PF3 bug, just looking for advice on how to minimise it).

martinlest wrote:

FSC?

Well, whatever, AI traffic does all too often cut across runways I am just taking off from or landing at, making it hard to avoid 'collisions'. I'll keep an eye out whether this is only at larger airports - maybe some AFCADs aren't easy for FS9/PF3 to deal with from this respect (I'm not saying this is a PF3 bug, just looking for advice on how to minimise it).

Martin, you know me well enough now to know I would never get upset if you did call it a bug and besides, it may well be!

I used FSC (Flight Sim Commander) when developing the Conflict Monitor as the AI aircraft changed colour on the FSC map when CM stop them in their tracks so I could see in real time how CM was working. If you have FSC it might be an interesting exercise and you should notice CM has stop several other aircraft but maybe not the one that suddenly causes you a problem. Just thinking aloud. Of course CM is not to blame if something occurs whilst you are taking off because all AI is frozen and released as you raise the nose

Quote:

Martin, you know me well enough now to know I would never get upset if you did call it a bug and besides, it may well be!

I only said that because I thought that it may well be the case - not to spare your feelings Dave!

I don't have FSC. I think it's fairly expensive, so am unlikely to buy it...

Quote:

because all AI is frozen and released as you raise the nose

What are the parameters exactly for AI traffic to be frozen? You mean within the range of CM, I assume? In that case, that might make sense (??), as the a/c I have encountered taxiing across runways have been more than half-way along from where I am taking off or landing and perhaps outside the distance from user a/c in which CM is active..

martinlest wrote:

What are the parameters exactly for AI traffic to be frozen? You mean within the range of CM, I assume? In that case, that might make sense (??), as the a/c I have encountered taxiing across runways have been more than half-way along from where I am taking off or landing and perhaps outside the distance from user a/c in which CM is active..

I have the same issue and always assumed it was because the AI are too far away. I just close my eyes open the cabin door and shout "hold on this could be bumpy".

Assign FSUIPC's traffic zapper to a joystick/yoke button and zap obstacles away

Quote:

Assign FSUIPC's traffic zapper to a joystick/yoke button and zap obstacles away

Yes, I do that already. Be nice not to have to though, as far as possible, of course.