Hi folks, really hope someone can help - I've only just purchased Radar Contact 4 - I had an earlier version of it some years ago and remembered how good it was then! Unfortunately I'm now having some rather frustrating problems with it. I see from looking at the forums that a few others have reported the same issue, but as there doesn't seem to be a decisive fix indicated anywhere, I thought I'd try posting the problem again.Basically I was doing a flight from EGKK to GCLP. All seemed to be going fine with departing from the gate and taxiing out to the runway all proceeding normally. RWY08R was in use on this occasion, and a medium length queue of traffic was waiting for takeoff. A few of the AI aircraft were given clearance to takeoff, and did so without a problem. Then, all of a sudden no further takeoff clearances were given, and the takeoff queue just froze completely. There was some arriving traffic, but more than sufficient gaps in between to allow a takeoff but nothing happened. One by one the traffic in front of me timed out, until one aircraft was left sitting just on the threshold, which curiously never timed out. After sitting behind it for 20 minutes to no avail, I finally gave up and took off anyway. This is the second consecutive time this happened - the first time I restarted FS because I noticed John's advice about turning off prerecorded chatter and just having AI generated chatter. Having made sure this was set, I was frustrated to encounter exactly the same problem again. I've also made sure the latest version of makerwys.exe is in place, and rebuilt the scenery db in RC. And I've made sure the latest version of FSUIPC is installed (3.9.8.0, 4th March 2010).Am I missing something or doing something wrong? If anyone could offer some advice here I'd be grateful. Regards,Tim

Hi folks, really hope someone can help - I've only just purchased Radar Contact 4 - I had an earlier version of it some years ago and remembered how good it was then! Unfortunately I'm now having some rather frustrating problems with it. I see from looking at the forums that a few others have reported the same issue, but as there doesn't seem to be a decisive fix indicated anywhere, I thought I'd try posting the problem again.Basically I was doing a flight from EGKK to GCLP. All seemed to be going fine with departing from the gate and taxiing out to the runway all proceeding normally. RWY08R was in use on this occasion, and a medium length queue of traffic was waiting for takeoff. A few of the AI aircraft were given clearance to takeoff, and did so without a problem. Then, all of a sudden no further takeoff clearances were given, and the takeoff queue just froze completely. There was some arriving traffic, but more than sufficient gaps in between to allow a takeoff but nothing happened. One by one the traffic in front of me timed out, until one aircraft was left sitting just on the threshold, which curiously never timed out. After sitting behind it for 20 minutes to no avail, I finally gave up and took off anyway. This is the second consecutive time this happened - the first time I restarted FS because I noticed John's advice about turning off prerecorded chatter and just having AI generated chatter. Having made sure this was set, I was frustrated to encounter exactly the same problem again. I've also made sure the latest version of makerwys.exe is in place, and rebuilt the scenery db in RC. And I've made sure the latest version of FSUIPC is installed (3.9.8.0, 4th March 2010).Am I missing something or doing something wrong? If anyone could offer some advice here I'd be grateful. Regards,Tim

get the latest version of makerwys, link pinned to the top of the forum. put it in the root directory of fs, and start rc. click the button for "reguild rc scenery database"two things cause this problem. incorrect runway and taxiway information or ai chatter not turned on.if the rebuild doesn't work for you, make a log, instructions pinned to the top of the forum, duplicate the problem, zip up the log, and send it to me, with the ai call signs that are misbehavingjd

get the latest version of makerwys, link pinned to the top of the forum. put it in the root directory of fs, and start rc. click the button for "reguild rc scenery database"two things cause this problem. incorrect runway and taxiway information or ai chatter not turned on.if the rebuild doesn't work for you, make a log, instructions pinned to the top of the forum, duplicate the problem, zip up the log, and send it to me, with the ai call signs that are misbehavingjd

Thanks John but as I said in my post, I have already downloaded the latest version of makerwys.exe, and rebuilt the scenery db in RC. I've also already got AI chatter turned on. I'll try to make a log.Thanks,Tim

I have the freeware UK2000 EGKK. I am attaching an AFCAD view of the 8R end. If the AI and you were taxiing on the end taxiway J, that hold short point is quite aways from the runway center line. The red circle is called the hold short limit radius. The FS rules for AI to my knowledge state that the hold short limit radius must touch the runway area. If not, FS might not release AI for runway clearance. I wonder if FS was taxiing aircraft for take-off to entries further upwind holding up the AI in front of you.From the AFCAD fault finder pop-up but this applies to FS9 as well:HOLD-SHORT NODE too far from runway.If this is a taxiway entrance that AI might use to enter a runway for takeoff then the hold-short node must be within 225 feet (68.6m) of the edge of the runway. AI aircraft will permanently stop if the final hold-short node before entering the runway is too far away. This is only critical for hold-short nodes where AI aircraft actually enter the runway for takeoff, usually the taxiway junction nearest the end of the runway. Also, this only applies to the active runway, the longest runway at the airport that is open for takeoffs. FS2002 will essentially ignore all other hold-short nodes, including taxiways that cross inactive runways, and in those cases the node distance from the runway is not critical.The circles show a 225 foot radius.I also expect RC4 would consider you too far from the runway as well if you are waiting for take-off clearance from RC with nothing in front.In general to avoid the mad rush of AI into the take-off queue and also arriving shortly thereafter in a large clump when loading a flight there are a couple of things you can do:Download from the file library here under FSX utilities called AI Smooth version 1.2. (This runs in FS9 as well as FSX. listed as aismooth_v120.zip. Install it and adjust AI separation to a bit longer than default. I recommend turning off respond to user aircraft so it doesn't freeze landing AI when you are near the runway. Also turn off the ATC Speak and Text options.If able you can set in FSUIPC a hot key to toggle AI on and off so you can refresh them. I'm not sure this is available in the RC registered version but is in as user registered version. See the docs for FSUIPC. Some users find relief when not using FS ATC to disable it via FSUIPC. This will not disable AI. In the general section of FSUIPC.ini after backing it up enter:RemoveATC=yesLets see what happens after checking things out.