Hi,Probably a stupid question, but still... :) What's the correct reaction to traffic advisories? For example, there's an AI plane on the reciprocal course, RC issues an advisory when it's 13-15 nm away from me, I check my TCAS and see that a risk of collision is present. What should I do next? Request higher/lower from RC, climb/descend to avoid a collision without telling RC, turn left/right to avoid collision? If I should request higher/lower, what should I do if RC denies the request? It will probably clear us in 2 minutes, but when there are 13 nm between the planes, we can't wait 2 minutes :)ThanksYuri

Hi, Probably a stupid question, but still... :)

It's actually a very sensible question Yuri and I, for one, will be fascinated to see what answers you get... and from whom. :(

It's actually a very sensible question Yuri and I, for one, will be fascinated to see what answers you get... and from whom. :(

from a code perspective, and advisory is telling you that you and the other plane will violate the seperation rules set within the program. if you were on a collision course, the ai would be vectored away from you. in rc, you don't have to do anything. the ai will pass above or below you, to your left or to your right, or a combination of these. during that pass, you and he will violate the sepearation rules. i can look them up in the code, if necessary.jd

if you were on a collision course, the ai would be vectored away from you. in rc, you don't have to do anything.

Excellent, you learn something new everyday. I could have sworn you dropped the ai vectoring routines ages ago but, obviously not. Thanks for putting me right. Pity you replied so quickly though - I was hoping to be entertained by some amusing answers along the lines of those posted in the current "250kt speed limit" thread. I see even CAP393 got a mention there! :(

I have had the odd situation where my TCAS resolution advisory went nuts and told me to climb or decend which I actually ignored as I didn't want ATC (RC4.3) to go nuts at me and I have collisions off, out of the few times it's happen no collision would have occured but once during approach it would have though. Haven't had this happen for a while though and I do see RC4 moving AI around.

Excellent, you learn something new everyday. I could have sworn you dropped the ai vectoring routines ages ago but, obviously not. Thanks for putting me right. Pity you replied so quickly though - I was hoping to be entertained by some amusing answers along the lines of those posted in the current "250kt speed limit" thread. I see even CAP393 got a mention there! :(

what i took out was vectoring you out of the conflict. unlike the human controllers who can visualize 3 dimensionally, and can noodle out a solution based on years of experience in a matter of seconds, to get a computer to do it without causing another conflict, which would then require me to vector you again, which might cause another conflict, which in the end could you put the pilot in far more serious danger than if i had left him alone, i took the stance of moving the one ai out of the conflict. if he causes a conflict with another ai, i don't care if the ai's collide :-)i haven't looked at the other post after reading the first response or two. is it entertaining?jd

I have had the odd situation where my TCAS resolution advisory went nuts and told me to climb or decend which I actually ignored as I didn't want ATC (RC4.3) to go nuts at me and I have collisions off, out of the few times it's happen no collision would have occured but once during approach it would have though. Haven't had this happen for a while though and I do see RC4 moving AI around.

if i'm not mistaken, i have a tcas climb and a tcas descend options in v5, so you can follow the tcas alerts if you want. essentially it's just another form for requesting deviations for weather.jd

Nice to know :)

Thanks for explaining! Yes, I noticed I rarely have a conflict with an AI plane when flying with RC (and I almost never fly with it :) ). So I'll ignore TCAS warnings, knowing that RC will take care of potential conflicts :)

If sometime you figure out to do the user-vectoring a bit better (like v6-ish...), do put it back in.. would add a lot of realism. Oh, and the other thread is not only entertaining, but we actually also have some discussion going on in there...