Hi,There is only one thing that makes my flights with RC4 not so exicting. Unfortunately, RC allows to contact Tower within 4-6 nm from rnwy threshold only. Unfortunately, this is very short distance especially in those cases where there is a single rnwy in use (such as KDCA). This often results in go-arounds. Is there any way to increase the distance in which user may contact Tower, for example 8-10nm?ThanksDmitriy

Hi,There is only one thing that makes my flights with RC4 not so exicting. Unfortunately, RC allows to contact Tower within 4-6 nm from rnwy threshold only. Unfortunately, this is very short distance especially in those cases where there is a single rnwy in use (such as KDCA). This often results in go-arounds. Is there any way to increase the distance in which user may contact Tower, for example 8-10nm?ThanksDmitriy

Hi Dmitriy,The distance at which you're handed over to Tower is not adjustable. If you're having problems with other aircraft landing ahead of you and not clearing the runway quickly enough thus causing you to G/A then AiSmooth may help you. This spreads out the aircraft further out than the area RC4 controls so should lessen the chance of a G/A.AiSmooth is freeware and is probably available in the AvSim Library.

A utility within fs9cfg16.zip here in the avsim libraries used judiciously can expedite AI taxiing and exiting the runway. Don't speed them up too much. It is only for FS9.aismooth_v120.zip as Ray recommends is the latest version to use here in the avsim library. I recommend setting to User Plane Response disabled just in case it interferes with RC ground and final AI control and just set it up for the spacing out landing AI. It places them into holding patterns. It also allows reduction in the take-off queue since departing AI can be interleaved with landing AI. This works in both FS9 and FSX and this version includes a manual.

Hi Dmitriy,The distance at which you're handed over to Tower is not adjustable. If you're having problems with other aircraft landing ahead of you and not clearing the runway quickly enough thus causing you to G/A then AiSmooth may help you. This spreads out the aircraft further out than the area RC4 controls so should lessen the chance of a G/A.AiSmooth is freeware and is probably available in the AvSim Library.

Thanks guys,I have both AISmooth and FS9configurator with taxi speed adjusted. My biggest concern are NOT landing or exiting planes, but planes that begin its taxiing into position at the same moment when I receive landing clearance. It's worse than FS9 default ATC where Tower is usually contact you immediately after vectors to final are received. Again - this issue only relates to those airports that SINGLE rnwy is in use - KDCA, EGKK, RJGG, ENBR...

Thanks guys,I have both AISmooth and FS9configurator with taxi speed adjusted. My biggest concern are NOT landing or exiting planes, but planes that begin its taxiing into position at the same moment when I receive landing clearance. It's worse than FS9 default ATC where Tower is usually contact you immediately after vectors to final are received. Again - this issue only relates to those airports that SINGLE rnwy is in use - KDCA, EGKK, RJGG, ENBR...

Hi Dmitriy,If this is a regular problem at single runway airports then something is clearly amiss. It's not something that I've experienced and it's not been reported that much to us.If you feel you can replicate the problem follow the instructions pinned to the forum to produce a log and send it to JD with details of what was happening.Do you keep your RC database up to date with MakeRunways? If not it might be worthwhile doing so. You can get the latest beta here http://fsuipc.simflight.com/beta/MakeRunways_441.zip.

Perhaps, I said it wrong. There is the list of assumption in priority order.1. RC ALWAYS provides option to Contact Tower within maximum distance of 7nm from rnwy threshold. Normal occurence is 4-6nm.2. Those airports that have rnwys used for both t\o and lndg are affected, since RC does not prevent AI from taxing into position, because landing clerance is issuing TOO LATE.And yes, I have option "Communicate with AI" checked.

Perhaps, I said it wrong. There is the list of assumption in priority order.1. RC ALWAYS provides option to Contact Tower within maximum distance of 7nm from rnwy threshold. Normal occurence is 4-6nm.2. Those airports that have rnwys used for both t\o and lndg are affected, since RC does not prevent AI from taxing into position, because landing clerance is issuing TOO LATE.

have you done a rebuild of the rc scenery database? if not, that might help. i may not think an ai is near a runway, and he lines up without my permission.if you've done that, make a log and send it to me. i'd like to see why ai are lining up after you contact tower. only planes that have already lined up, and allowed to takeoff and get out of your way. all other ai are frozen to keep them from lining up.if the ai in front of you has not vacated the runway fast enough, then the previously mentioned utility to speed up the ai taxi speed would help.if this is still an issue, make a log, and let me look at it. i would think that if this was a systemic issue, many others would have reported before you. that's why i lean towards the scenery database rebuild or the utility.just curious, what is your ground speed when you contact tower?jd

RC is supposed to freeze ground AI to prevent runway incursion when you are about five miles out. You must be on tower frequency. Be sure all comms are promptly acked. Make sure your FSUIPC is current, links at the forum top or use this for a later beta version:FSUIPC interim update version 3.947 http://fsuipc.simflight.com/beta/FSUIPC3947.zip---- Install the full release, 3.93, first: available from http://www.schiratti.com .Ray mentioned the makerwys update insuring that RC sees your aircraft and AI locations in reference to your installed scenery. As always, run everything through the RC UI Scenery Rebuild.Also try AISmooth with User Plane Response both OFF (recommended by me) and on. AISmooth should also have its ATC audio and window options turned off.

Perhaps, I said it wrong. There is the list of assumption in priority order.1. RC ALWAYS provides option to Contact Tower within maximum distance of 7nm from rnwy threshold. Normal occurence is 4-6nm.2. Those airports that have rnwys used for both t\o and lndg are affected, since RC does not prevent AI from taxing into position, because landing clerance is issuing TOO LATE.And yes, I have option "Communicate with AI" checked.

I may have to defer to JD on this. If it was a case of landing clearance being issued too late that was causing departing aircraft to taxi onto the runway it would be affecting everyone and that isn't happening.What's your approach speed? What aircraft are you flying? Does it happen with all aircraft types or only a few.. or one? Sorry for all the questions but I'm struggling to see what is causing these problems.RC will prevent aircraft taxiing onto your landing runway but JD will need details of when it happens and a log is the best way of analysing it.

1. I'm doing Scenery Rebuild each time when I changed AFCADS. I have a couple of my own set-ups for complicated airports such as KORD, EHAM and LEMD and I always use AFCAD file that is appropriate for particular wind. Then, I run RC Scenery Rebuild.2. I fly PMDG and LDS birds only.3. Latest FSUIPS versions are registered4. MR version 4.41 installed and run each time with Scenery Rebuild.5. Approach speeds = 180 before GS capture and 160 after GS capture with gradual decrease to Vref30+5 according to FMC.Again, If I'm lucky enough to get landing clearance within 3-4nm, AI freezes - no problem and RC does its best according to manual. However, it's not happens that often, since RC response is late.I'll send the log later tomorrow, but I don't think there is a bug or whatever. Something fundamentally is wrong, but I don't know what. Perhaps Ron is right and if I turn on Tower Frequency manually before RC actually ask to do that, this would help (I hope).

Okay, looking through that list nothing looks out of place. You can't switch to TWR until so directed but you could try turning on auto-comms (CTRL+SHIFT+K) and see if that changes anything. Personally I don't think it will but it's worth trying.v4 was extensively beta tested and has been out for a couple of years. If we got something like this fundamentally wrong we'd be swamped with complaints. I don't doubt you're experiencing problems but it must be down to something that few other people have set.Maybe you have two Ai traffic packages and an unusually high number of aircraft? If all else fails then the log will reveal everything to JD.

Two things slow down RC response:1. Prerecorded chatter (not AI Chatter).2. Display Text Option.See if these are not selected on the General page.

Nope - nothing wrong with AI. I'm AI- maniac by myself and compile everything manually after scrupulous checking each and every FP via AITM and ACA2007.

Two things slow down RC response:1. Prerecorded chatter (not AI Chatter).2. Display Text Option.See if these are not selected on the General page.

Both disabled.I'm about to fly RJAA - RKSI tonight with PMDG MD11, Overland custom sceneries for both airports and custom-made AFCADs+extenstive AI Traffic (all done by myself). I will report upon landing. Cruise phase of the flight will be done with 4x acceleration.

Unless you need it you can also shut down the FS comm services since RC provides this for you. This does not affect AI flight control.Put in the General section of FSUIPC.ini the following (after making a backup):RemoveATC=YesThis has actually also prevented some problems when using another ATC application.

OK, here is the recap.1). RC authorized vectors to final RKSI rnwy 15L within 17nm from rnwy thrshld - OK2) RC asked me to contact RKSI Tower withing 8nm from rnwy thrshd. My speed was 165kts, GS was captured, ILS landing was in progress.3) RC issued clearance to land within 4nm from rnwy thrshld. At the same time AIA B747 began its taxing to rnwy 15L for T/O.The result = RC issued go-around for me. That's why I'm saying that speed-up of this process could solve the issue. Default ATC handles situation like these much faster. Why there is such large time gap between vectors to final authorization and Tower contact? The elimination of this gap could be very helpful.Best Regards