Hi all!I just got my RC4.3 a few weeks ago. Seems like a great addon, and I'm really enjoying it, altough I'm having some issues with it. Until this moment I wasn't able to find answers to these problems on the manual.:1. Conflicting weather data. I use FSX own weather system, Real World Weather with updates every 15 min. When I click "ATIS" on RC main screen I can hear both ATIS: FS's ATIS and RC's ATIS. Also, weather data differs sometimes drastically (from calm winds to 10kts, and temperatures discrepancy of 5 degrees). 2. During many of my flights I get the ATC telling me to turn back until "receive suitable for navigation", altough I'm flying my FP just as filed. It keeps doing this all the time, the only way I have to stop it is by requesting DIRCT TO next waypoint. I use FSBuild to make my FP and export them to FSX and PMDG folders.3. There seems to be some planes that are not beeing controlled by RC, and I'm able to hear FSX ATC controlling them. I don't know if it's related, but I think it results in poor vectoring: I see go arounds all the time.Does anyone have this problem? Ideas of how to fix it? I'm afraid I might be doing something really wrong...I also wanna apologize for my poor English, still learning!Thanks in advance,Bruno

Hi all!I just got my RC4.3 a few weeks ago. Seems like a great addon, and I'm really enjoying it, altough I'm having some issues with it. Until this moment I wasn't able to find answers to these problems on the manual.:1. Conflicting weather data. I use FSX own weather system, Real World Weather with updates every 15 min. When I click "ATIS" on RC main screen I can hear both ATIS: FS's ATIS and RC's ATIS. Also, weather data differs sometimes drastically (from calm winds to 10kts, and temperatures discrepancy of 5 degrees). 2. During many of my flights I get the ATC telling me to turn back until "receive suitable for navigation", altough I'm flying my FP just as filed. It keeps doing this all the time, the only way I have to stop it is by requesting DIRCT TO next waypoint. I use FSBuild to make my FP and export them to FSX and PMDG folders.3. There seems to be some planes that are not beeing controlled by RC, and I'm able to hear FSX ATC controlling them. I don't know if it's related, but I think it results in poor vectoring: I see go arounds all the time.Does anyone have this problem? Ideas of how to fix it? I'm afraid I might be doing something really wrong...I also wanna apologize for my poor English, still learning!Thanks in advance,Bruno

1) http://www.jdtllc.com/FAQ.htm#17 - just turn the ms atc volume to 0. don't disable it.2) you probably missed a checkpoint. pay particular attention if you have a departure procedure. that is a checkpoint inside 30 miles. listen to the clearance. does he say "...via departure procedure...". does tower give you heading to fly? if not, you have a departure procedure. you may need to read the manual on how to fly departure procedures.3) rc doesn't really control ai. except on final when i move them out of the way. so if there are a lot of go arounds, there are a lot of go arounds.

1) http://www.jdtllc.com/FAQ.htm#17 - just turn the ms atc volume to 0. don't disable it.2) you probably missed a checkpoint. pay particular attention if you have a departure procedure. that is a checkpoint inside 30 miles. listen to the clearance. does he say "...via departure procedure...". does tower give you heading to fly? if not, you have a departure procedure. you may need to read the manual on how to fly departure procedures.3) rc doesn't really control ai. except on final when i move them out of the way. so if there are a lot of go arounds, there are a lot of go arounds.

JD, thanks for you support!About points 2 and 3, I think that's settled then. But... what weather should I trust? The temperature I get from the ATIS and the winds are not the same I get from the real FS world... Should I just trust RC ATIS and go with it?

JD, thanks for you support!About points 2 and 3, I think that's settled then. But... what weather should I trust? The temperature I get from the ATIS and the winds are not the same I get from the real FS world... Should I just trust RC ATIS and go with it?

where are you getting the fs world temp and winds?rc get's the weather from fs via fsuipc.if they don't agree, do this...tell me what version of fsuipc do you have?are you actually letting fs run as the weather is being set, before you looks at the fs weather?make a log, instructions pinned to the top of the forum.duplicate the problem with differing winds and temps, save the log and send it to me. also tell me what you think the winds and temps should be.jd

But... what weather should I trust? The temperature I get from the ATIS and the winds are not the same I get from the real FS world... Should I just trust RC ATIS and go with it?

As well as what JD said, note that the ATIS weather is the weather at the Weather station dialled in for ATIS reception, not the weather at the aircraft. They can certainly be different.Pete

ATIS lags weather updates from any source including FS weather when you first load a flight. After the first initial weather update while you are parked try advancing the FS time one minute to force an immediate weather and ATIS update. This will also restart the AI so they conform to the initial updated weather for runway selection. Again, this only applies to the first weather update.Regarding exported FS and FMC plans from FS Build, do you export the the STAR and SID data from FS Build as well? If so, even with attempting to keep the FMC and FSB AIRAC data synchronized between the two, you probably find the FMC SID/STAR data different then SID/STAR data in the FS Build database. I tend not to use the SID/STAR database of the FMC but the full FMC imported FS Build plan for the FMC which matches the plan for FSX and RC. That way they are all in sync. The only thing I bring up from the DEP/ARR arrival section is the specific runway procedure (from the right side of the arrival page) for situational awareness in flying the destination airport pattern in seeing the extended runway center line and waypoints on the final approach. This helps with localizer and ILS merges including late altitude adjustments.AIRAC updates for FS Build are downloadable from www.fsbuild.com at no charge. Free PMDG AIRAC updates for about 65 US airports are created by Dan Downs and are available from AVSIM.com. Search for that name or ddowns. A few European countries centering about the UK are available at no charge from planepath.com. For the FMC mostly worldwide you can subscribe to navigraph.com for terminal procedures. That payware system offers you at one price for each period as many FMC formats that it has without additional charge.Regarding communications if you have Interact with AI checked in RC options you should here the results of FS controlling AI on your current frequency. RC regenerates this and you should have as jd stated the FS ATC sound turned down.To reduce go-arounds and also allow reduction of take off queues look at this freeware utility:aismv120.zip available from flightsim.com (AI Smooth version 1.20) alllows you to specify separation of aircraft on final approach and some other details by puting AI in holding patterns. It works via FSUIPC for both FS9 and FSX. You can try AVSIM as well.

Hello,Thanks everyone for helping. It took me a while to answer, so sorry about that!First of all: the problem with route waypoints and all I was able to fix. Anyway, just requesting direct-to next waypoint is not a big deal for me.What's bothering me is the weather problem and the AI wierd situations. I'll describe some of them here, and I also took 3 screenshots to show you what's happening.By the way, I'm using and unregistered version of FSUIPC 4.57 JD, The log will be ready for you tomorrow.Some things I noticed on my last flight:1- I'm never being told to takeoff from the same runway that the other AI planes are using for takeoff. In KSLC, everyone was taking off from 34R, and the RC4 ATIS was saying "departing runway 35" and I was the only one directed to runway 35.2- When I'm holding short at the runway and there's an AI plane on final, the Tower tells me to "Position and hold". The landing airplane always go around, without tower comunication or go around order.3- I was cleared for takeoff while there was an airplane that had just landed still about to exit the runway. Now, to the screenshots:The first one was an "cleared for takeoff" instruction on KLAS. There was an AI plane landing from the other side. He went go around, again with no tower comms. At the second shot, you can see in the TCAS: there is a role line of landing planes comming from the other side to land at the same runway I was taking off. That's in KLAS, also.It's like if there was two ATCs working giving completely diferent orders!This one shows the TAT as atested from my MD-11: -1

Hello,Thanks everyone for helping. It took me a while to answer, so sorry about that!First of all: the problem with route waypoints and all I was able to fix. Anyway, just requesting direct-to next waypoint is not a big deal for me.What's bothering me is the weather problem and the AI wierd situations. I'll describe some of them here, and I also took 3 screenshots to show you what's happening.By the way, I'm using and unregistered version of FSUIPC 4.57 JD, The log will be ready for you tomorrow.Some things I noticed on my last flight:1- I'm never being told to takeoff from the same runway that the other AI planes are using for takeoff. In KSLC, everyone was taking off from 34R, and the RC4 ATIS was saying "departing runway 35" and I was the only one directed to runway 35.2- When I'm holding short at the runway and there's an AI plane on final, the Tower tells me to "Position and hold". The landing airplane always go around, without tower comunication or go around order.3- I was cleared for takeoff while there was an airplane that had just landed still about to exit the runway. Now, to the screenshots:The first one was an "cleared for takeoff" instruction on KLAS. There was an AI plane landing from the other side. He went go around, again with no tower comms. At the second shot, you can see in the TCAS: there is a role line of landing planes comming from the other side to land at the same runway I was taking off. That's in KLAS, also.It's like if there was two ATCs working giving completely diferent orders!This one shows the TAT as atested from my MD-11: -1

if you get your taxi instructions before the ai start taxiing, you may get a different runway than they do.have you clicked the "rebuild rc scenery database" in rc? what version of makerwys.exe is in the root directory of fs?

With regard to your query regarding AI. AI is controlled only by Fs9 ATC. Both Radar Contact and PFE "listen in" and if you're lucky(if your RC or PFE programme has been configured to do so) you will hear their ATC version give an instruction to an AI aircraft. I use PFE and the instructions I hear are usually out of sinc!As for which rwy to take off and land on. That's quite easily solved by using afcad and designating parallel rwys either for take of or landing as is done in the real world. Fs9 ATC declares all rwys open to anybody from any direction. So that is why you must make the additional adjustments in afcad. It is probably the same in RC but I also have to tell PFE to do the same even after having run makerwys.exe. It's tedious but at least it means everybody is singing from the same hymn sheet!Vololiberista

With regard to your query regarding AI. AI is controlled only by Fs9 ATC. Both Radar Contact and PFE "listen in" and if you're lucky(if your RC or PFE programme has been configured to do so) you will hear their ATC version give an instruction to an AI aircraft. I use PFE and the instructions I hear are usually out of sinc!As for which rwy to take off and land on. That's quite easily solved by using afcad and designating parallel rwys either for take of or landing as is done in the real world. Fs9 ATC declares all rwys open to anybody from any direction. So that is why you must make the additional adjustments in afcad. It is probably the same in RC but I also have to tell PFE to do the same even after having run makerwys.exe. It's tedious but at least it means everybody is singing from the same hymn sheet!Vololiberista

i've never touched an afcad, and my runway selections are in sync with the ai. you just have to give the ai a chance to start up and get their taxi instructions.if you don't rebuild the rc scenery database, you may be at the end of the runway that you see, but the lat/long you're at may not be close enough to the data in the database, so i don't know where you are on the taxi way. if the distance from the end of the runway according to the database and where the ai is, may lead to a different distance than in flight sim. if i think the ai is 8 miles out, i might tell you to taxi into position and hold. but he might really be 4 miles out, and i shouldn't clear you on to the runway.in summary, it's really simple. don't jump straight to clearance and straight to ground. do your checklists, let the ai start going, get the weather, check your charts, call clearance and then ground. and alway rebuild the rc scenery database after changing the scenery. either by adding a new traffic program or after adding new scenery files.

i've never touched an afcad

But Fs9 ATC "does" use the info supplied by the afcad file to control AI and user movements. Particularly with regard to rwy length, orientation, closed for landing/take-off etc. As well as inclusion of radio facilities and their position. Makerwys.exe examines the relevant files in the sim including afcads. (that is why it is important to run makerwys.exe every time one has a new add-on airport or a material change is made to an existing one.)Vololiberista

But Fs9 ATC "does" use the info supplied by the afcad file to control AI and user movements. Particularly with regard to rwy length, orientation, closed for landing/take-off etc. As well as inclusion of radio facilities and their position. Makerwys.exe examines the relevant files in the sim including afcads. (that is why it is important to run makerwys.exe every time one has a new add-on airport or a material change is made to an existing one.)Vololiberista

it doesn't matter what fs9 atc does. the fs9 atc sound should be turned down to 0. you shouldn't even hear it.this is sort of a tangent from the original post. if you want to control what the ai are doing, runway wise, then yes you have to modify the afcad.but for rc to pick the right runway, based on what the ai are doing, you don't have to modify any afcad file. i'll know what they are doing as soon as they start moving.and if you don't like the runway choice rc has made, you can always request a different one. and if you know what runway you want before you start rc, you can choose the runway within rc before you start (the danger there is you may be oppposite what the ai are doing).jd

it doesn't matter what fs9 atc does. the fs9 atc sound should be turned down to 0. you shouldn't even hear it.this is sort of a tangent from the original post. if you want to control what the ai are doing, runway wise, then yes you have to modify the afcad.but for rc to pick the right runway, based on what the ai are doing, you don't have to modify any afcad file. i'll know what they are doing as soon as they start moving.and if you don't like the runway choice rc has made, you can always request a different one. and if you know what runway you want before you start rc, you can choose the runway within rc before you start (the danger there is you may be oppposite what the ai are doing).jd

Yes, that's the point. If you set up the afcad and RC to do the same thing then AI is less likely to do something surprising.Vololiberista

Yes, that's the point. If you set up the afcad and RC to do the same thing then AI is less likely to do something surprising.Vololiberista

you do not have to modify afcad files. rc will follow what the ai are doing.i want to make this perfectly clear for those reading this and getting confused, and believing that afcad files have to be modified to make rc work with ai. that is not necessary. under no situation do you have to modify an afcad file after purchasing radar contact. once you click "rebuild rc scenery database" rc knows where the airports, runways, gates, etc are in terms of lat/long in your scenery files.rc will be able to watch the ai, and follow them, either taxiing to the departure runway or picking an arrival runway.jd

I have modified all the airports I use regularly by using AFCAD.usually the complex ones with parallel runways like LAX,LAS,SLC,Tokyo,Hongkong etc.This is merely to make the traffic behave more as it does in real life like LAX where they tend to use the inners for take off and the outers for landing.I managed to get the runway usage at EGCC to resemble real life(not using 23L for landings for example)but it took a few goes.Likewise Gatwick (EGKK)and Auckland where FS has 2 runways but one is hardly ever used.Once altered the AI seem to adopt this for the most part and so RC tends to follow suit.The crucial thing does seem to be to let the AI settle down as suggested by JD and Ronzie.I still seem to get strange goings on at SFO.I'm not there very often in real life but do they ever use 10L/R for landings and take offs and 01 L/R for landings?There are some RNAV/SID procedures for 10L/R in the books I have.