Hi everyone. I have looked through the forums about this problem and it seems to be common. At some larger (but default) airports like Heathrow, upon you contacting tower all taxiing aircraft will stop moving. Also upon landing at some airports, aircraft that are waiting for takeoff will never be cleared to do so even after you've left the runway and no other traffic is approaching; they'll just eventually be deleted automatically. More recently, I also noticed that some planes that, for example, had just taken off, will freeze in mid-air during their climb. I just got RC a few weeks ago. I'm using it with Ultimate Traffic. FSUIPC is 3.75, Interact with AI is on, AI chatter is on, and I rebuild the scenery database before the first use and haven't installed any new scenery since. Makerwys is 4.12. Any help is much appreciated.Al

While maybe not specific to your problem your FSUIPC version is way behind as is your makerwys. Get them from here:http://www.schiratti.com/dowson.htmlWhat is your RC version including build number. It is displayed on the RC screen.

Thanks for the help. I will download the new version of FSUIPC and Makerwys. My RC is 4.3.3845.After some time observing AI traffic movement, I have some questions regarding the tower control logic. 1) I've noticed that AI aircraft contact the tower initially and get cleared for final and receive wind speed and direction, but never any actual landing clearance before they land.2) When AI aircraft go-around, they do so without prompting by ATC.3) After standing in a queue for 15-20mins while other aircraft were taking off/landing (without incident) the logic seemed to break down and an aircraft was cleared to enter the runway and takeoff even though another had already contacted tower to land and was just a mile or so out. Before I could see what was going to happen, the aircraft behind me in the queue, which had been doing a good job of holding behind me, taxied up to the hold-short point and crashed into me from behind. 4) Was it a design decision that you would not hear radio chatter for other runways even if they share the same frequency? It seems if another aircraft departs on another runway you will hear it get handed off to departure, but not hear it get cleared to line up or takeoff.5) This is a minor point, but is COM2 not recognized?Thanks for a great product which is really enjoyable to use.

Thanks for the help. I will download the new version of FSUIPC and Makerwys. My RC is 4.3.3845.After some time observing AI traffic movement, I have some questions regarding the tower control logic. 1) I've noticed that AI aircraft contact the tower initially and get cleared for final and receive wind speed and direction, but never any actual landing clearance before they land.2) When AI aircraft go-around, they do so without prompting by ATC.3) After standing in a queue for 15-20mins while other aircraft were taking off/landing (without incident) the logic seemed to break down and an aircraft was cleared to enter the runway and takeoff even though another had already contacted tower to land and was just a mile or so out. Before I could see what was going to happen, the aircraft behind me in the queue, which had been doing a good job of holding behind me, taxied up to the hold-short point and crashed into me from behind. 4) Was it a design decision that you would not hear radio chatter for other runways even if they share the same frequency? It seems if another aircraft departs on another runway you will hear it get handed off to departure, but not hear it get cleared to line up or takeoff.5) This is a minor point, but is COM2 not recognized?Thanks for a great product which is really enjoyable to use.

1) you won't hear ai chatter for runways that aren't the one you are assigned to. when i developed the ai chatter, i found that there was way too much chatter going on, and the i spent more time chattering than making things happen. so i limited tower chatter to ai on the same runway as you. in v5 that's changed, now you hear everybody (on your frequency).2) similar to 1, way to much time was spent chattering to ai about going around. i wasn't making them go around, but a lot of time was spent telling them to go around.3) make sure you have the latest makerwys, and you click on the rc scenerday database rebuild button. if i don't accurately know where your runway and taxiways are, things get messed up. if that's not the case, make a log, and send it to me.4) see 1)5) you can use it, but rc won't be talking on it.

Hi JD,I've experienced that "hanging in the Air AI Traffic" also. I've tried all programs separately (AISmooth, AI Separation and RC) and found that RC is the program slowing the AI traffic in the air.It only happens to the AC that I am in direct conflict with...not the ones well away from me or passing behind me...only the ones that are flying toward me. I've seen 747s at FL350 flying at 40 knots...looks funny when you fly by them!I've attached a log file and provided a screen shot of what FS Commander sees (me and AI Traffic N733JD). I'm in slew, so disregard my speed ;)AI Traffic shot with FlightSim CommanderAs you can see, N733JD is slowed down to 16 knots where once it was at 185 knots. It just hangs in the air hardly moving. It seems that all the traffic that slows down is moving at about 10% of speed.I have FSUIPC version 3.93I use WideFS version 6.78RC version is 4.3.3843Interact with AI is toggled on.Thanks JD!Devin

Hmmm..the attachment didn't work. Let me try again. Seems like it's too big.I've put it here:http://rapidshare.com/files/300157043/aitrafficlog.zipDevin

Hmmm..the attachment didn't work. Let me try again. Seems like it's too big.I've put it here:http://rapidshare.com/files/300157043/aitrafficlog.zipDevin

make a few changes to your rc options.first, change your heading deviation to 30. you have 80. there is no reason to have it so high. i think you can fly a heading +/- 30 degrees of what you are assigned. if you did it so you wouldn't get yelled at, let's work on what the cause of getting yelled at.second, define the .flt/.wx path. click the .flt/.wx path, and enter the path where fs stores the .flt/.wx files. in your case it is H:\Users\Devin Pollock\Documents\Flight Simulator Files\lastly, in departure, you were given a traffic advisory, and you never acknowledge. RC was sitting there waiting for you to respond. you never did.jd

make a few changes to your rc options.first, change your heading deviation to 30. you have 80. there is no reason to have it so high. i think you can fly a heading +/- 30 degrees of what you are assigned. if you did it so you wouldn't get yelled at, let's work on what the cause of getting yelled at.

Never noticed that...I guess I changed it a long time ago and forgot to put it back! :(

second, define the .flt/.wx path. click the .flt/.wx path, and enter the path where fs stores the .flt/.wx files. in your case it is H:\Users\Devin Pollock\Documents\Flight Simulator Files\

Done.

lastly, in departure, you were given a traffic advisory, and you never acknowledge. RC was sitting there waiting for you to respond. you never did.jd

I was just waiting to get an AI aircraft to slow down to show my example...I never got around to answering. On a normal flight I answer every call.I'm not entirely convinced that RC is to blame as FSUIPC has been updated many times over the past years/months. I do know that in my situation, it is RC that does this. If I don't run RC, the AI traffic fly right on past at full cruise speed.Let me know if you need more (as in a full flight log and the FSUIPC log.Devin

Never noticed that...I guess I changed it a long time ago and forgot to put it back! :( Done.I was just waiting to get an AI aircraft to slow down to show my example...I never got around to answering. On a normal flight I answer every call.I'm not entirely convinced that RC is to blame as FSUIPC has been updated many times over the past years/months. I do know that in my situation, it is RC that does this. If I don't run RC, the AI traffic fly right on past at full cruise speed.Let me know if you need more (as in a full flight log and the FSUIPC log.Devin

yes, if you can duplicate the problem, send me another rc log, and tell me in the email, what happened or should of happened, or shouldn't have happened, and when. if there is another ai involved, telling me his callsign would be fantastic.then i can zero in on the log, and see what rc saw, and why rc did or didn't do something.jd

No problem JD. Once I do a flight that has this problem (its random of course when AI will conflict with me to duplicate the error during a flight of course) I'll e-mail you the logs.D

Alright JDI did some testing, and RC is fine...it was not the problem alone. It seems that if I run AISmooth and RC together, I get this reaction by the AI. If I do a clean connection (meaning FS9 boot up with only WideFS and Radar Contact) the problem doesn't appear.So basically I live with it or I don't run AI Smooth. Thanks for your time JD! ;)Devin

There is a fix for AI Smooth for this:First download version 1.20 here from AVSIM or flightsim.Then in the AI Smooth settings turn OFF Respond To User Aircraft if the problem is still in v1.20. I have it off as it freezes or slows AI aircraft in a wide range around the user aircraft at least in previous versions. If you are stopped anywhere in a runway vicinity it just freezes them on the ground.

Alright JDI did some testing, and RC is fine...it was not the problem alone. It seems that if I run AISmooth and RC together, I get this reaction by the AI. If I do a clean connection (meaning FS9 boot up with only WideFS and Radar Contact) the problem doesn't appear.So basically I live with it or I don't run AI Smooth. Thanks for your time JD! ;)Devin

Hi Ronzie...Thanks for your response. I have v1.20 and have "User plane respone" turned off. What I decided to do is re-unzip AI Smooth. I found that my "AISmooth_RO" file was 0kb where in the zip it is 574kb...so that may be a problem, I don't know. I'll test it again with the fresh install of AIsmooth and see how it goes.Thanks for your help! :)Devin

I have the same problem with ai traffic and i don't know how to solve this problem.I try to solve it over three days but without results.I use radar contact v4.0 and FSUIPC 3.70.When i set on the tower frequency ai traffic stops when i contact with departure all get back to standard.I don't know what I may do with it.Please help me!

I have the same problem with ai traffic and i don't know how to solve this problem.I try to solve it over three days but without results.I use radar contact v4.0 and FSUIPC 3.70.When i set on the tower frequency ai traffic stops when i contact with departure all get back to standard.I don't know what I may do with it.Please help me!

first, email me, and get a link to version 4.3, which is the current version. also use the link pinned at the top of the forum, and download and install the latest version of fsuipcalso get the latest makerwys.exe, and install it into the root directory of fsTHENwhen you start rc, click the rebuild rc scenery database button, and let me read your scenery files, so i know where your runways and taxiways are.then see if the problem still existsjd