Hi, recently I came across interesting issue. It was in Paris few days ago. I got RWY assigned and while on approach - still about 20miles from RWY I got different winds, where it was natural that I would prefer new RWY assigment. RC was telling me the new rwy in use, however it could not assign it. I got messarge, can't comply due to traffic, use rwy xy - where xy is the old assigment. As a result i landed in crosswinds, which was not that bad, but still. Any ideas? From my point of view it was alright but you never know...

Hi, recently I came across interesting issue. It was in Paris few days ago. I got RWY assigned and while on approach - still about 20miles from RWY I got different winds, where it was natural that I would prefer new RWY assigment. RC was telling me the new rwy in use, however it could not assign it. I got messarge, can't comply due to traffic, use rwy xy - where xy is the old assigment. As a result i landed in crosswinds, which was not that bad, but still. Any ideas? From my point of view it was alright but you never know...

i'm pretty sure the ai were using the opposite end of the runway you wanted. better to land with a crosswind than to land on the opposite end of the runway being used for takeoffs by the aijd

True, but landing/departind was the rnw that I wished to request. Could it be that... RC was giving proper rwy that shoulbe be in use, and AI was using the opposite? Next time it happens (it was first time in months) I will hit restart traffic in UT2.

I think UT2 spawns traffic about only 40 nm out from your aircraft. I could be wrong. RC looks at traffic at just outside 40 nm for destination so if AI changes it may not be recognized.You might also want to add the statement below to your FSUIPC.ini (after backing it up) General section to insure if you have a TCAS using FSUIPC it is getting its maximum range:TCASrange=0

I think UT2 spawns traffic about only 40 nm out from your aircraft. I could be wrong. RC looks at traffic at just outside 40 nm for destination so if AI changes it may not be recognized.

You can change that in UT2 settings.. so you're saying traffic in UT2 should be visible for more than just 40nm from your a/c? I have it set to 25nm now because with 40 I'm afraid the performance hit would be massive (traffic loading on surrounding airports and so).

If you are worried about performance hits then spawn your traffic 50 nm out if you can and lower your percent of traffic. That way RC will see your AI just before you are contacted by approach, or just 40 nm if you wish. I don't know how UT2 traffic responds to FS sliders for AI percent.However, your setup looks like it should handle quite a bit of traffic. Only in certain areas where a number of high density airports are in close range would AI traffic become a heavy burden. The Chicago area is one.To see how AI is running you can in a separate window run this program:http://fsuipc.simflight.com/beta/TrafficLook.zipwhile parked. As in the previous reply after backing up your FSUIPC.ini set the TCAS range to 0. Start FS and load a parked flight in an area of concern. Start Traffic Look. You can switch windows (alt-tab) between FS and Traffic Look. The Traffic Look program reports what AI FSUIPC sees and gives details for location (departure or destination), status, runway to be used, altitudes, distance, etc. Just give a chance for your AI to build correctly as it takes awhile. You can select just ground or air traffic but to see all after doing that I had to restart it.Be sure FS is not set to pause on a task (window) switch.

You can change that in UT2 settings.. so you're saying traffic in UT2 should be visible for more than just 40nm from your a/c? I have it set to 25nm now because with 40 I'm afraid the performance hit would be massive (traffic loading on surrounding airports and so).