Hello,I'm really glad that the new version of Radar Contact will have more control over AI traffic. This is one of the best add-ons I've ever bought for FS. Thank you. I am curious, though, about something. In the current version, I like to switch to the default ATC at 200 nm from my destination when flying into busy airports to avoid conflicts with other aircraft. However, when switching back to ATC, I get a command to turn about 180 degrees from my current heading and sometimes I'm just left in that pattern, actually flying in the opposite direction than I should be. I will note that on takeoff, I do request permission from the default tower, as well as RC, and acknowledge handoff to departure when instructed...however, I don't contact departure, since that would cause a conflict with RC. At 200 nm, I reset the squawk code to that given to me by the default ATC at clearance before I contact the default center (after exiting RC), so I don't think that's the problem. Any idea what could be causing this?Oh yeah...one suggestion for RC version 4 would be the ability to set a user-defined squawk code in the options memo.Thanks again for a great product!

Hi there,I think I understand correctly that the problem arises after you have closed RC. It is a problem with the default atc.The most obvious answer would be that a waypoint has been missed and you are being instructed to fly back to it.Hopefully with v4 you'll be able to forget the default atc and enjoy RC control all the way to the arrival airport. We should protect you from other aircraft better than MS will ;-)It's probably also worth running a utility like AISmooth to further improve the separation of arriving aircraft.All the best,John