A two fold question:1) How far out do I turn on the APP for the ILS approach? I have turned it on when it appears on the screen and last night when I was on approach at KMSY and was about 15m out and turned it on it took me off course and like just went it circles. 2) When I arrived at KAUS and was taxing to the gate and on the taxiway they cleared a AI to taxi to the runway causing it to come right to me. I had to turn onto another ramp exit. Also I was taxing for takeoff at KMSY and they cleared American to taxi to the ramp on the same taxiway I was on to the runway causing me to have to turn off the taxiway and deture back to the taxiway otherwise it would had been a headon accident. Is this normal for RC to give these instructions?

1. KMSY runways 28 and 10, 19 and 1, each pair share the same localizer frequencies at both ends. In FS, both ends are simultaneously active and it is possible to easily lock on to the wrong one. Many times until you are within two degrees of the centerline you will notice the wrong LOC ident on your nav instrument. Wait until you get the the correct ident before engaging APP. As the LOC indicator centers (using HDG mode to do the merge and intially turn inbound) the correct ident should appear. By default FS has all LOCs with backcourse turned on. This is especially damaging where each runway end has the same frequency. Download AFCAD 2.21 from the utility library here, go into airports with the shared LOC frequency at each end, and turn off the backcourse in the LOC/ILS properties and then save your file. You should then start FS and let it reindex the scenery and then shut it down. Start RC and rebuild the scenery database.2. RC does not control ground AI except to keep them from encroaching on the runway when you are on short final. FS itself should be stopping ai from crashing into you but will not direct ai around you. The RC ATC you hear taling to ai is in most cases just reiterating what FS chatter is telling ai. Improving RC control and interaction with ground ai is a goal of the next or later version of RC still about a year from release.

Thanks for your reply. Another question. WHen I fly from KMSY to KJAX they gave me expect ILS vector runway 7. The took me down to 3K. Then they took me over 70 miles out across the Atlantic never giving me a heading back to runway 7 for the landing. The last time befoe this they gave me runway 25 still taking me way out across the Atlantic. Is this normal for ATC to do this or do they just sometimes forget about you? I ended up terminating the flight.

you shouldn't go more than 20 milesi'd have to see a log of this happening.somehow i think you missed the turn to basejd

Also where in AFCAD is the LOC/ILS properties? I have looked all thru the toolbar and cant find it even clicking on the end of the runway bringing that info up. I really need to turn it off because I just tried to land again on rwy 10 and got 4 miles on final turned on APP and it was on the right one IMSY and still turned decended from 1800 and crashed. I can hit the localizer and land without RC. But also again it took me out into the GOM about 50 miles and I asked for an ILS approach and it put me on a heading back toward the airport. But when I got 4 miles on final put on APP it turned quickly and crashed. I will try to DEBUG the next flight and email it to JD so maybe he can see what is going on.

It is easiest to use the various lists to get to runway and navaid properties.On the AFCAD menu bar click lists, then on navaids. The list of all navaids attached to the airport will open. Click on the ILS in question and click on properties. Look for the check box Back Course Enabled and if checked click on it to disable. Then OK to close the window and click on file, save.Note there are some airports where scenery designers have renumbered runways and updated approaches. This may present additional problems. Any AFCAD I get that needs to supersede in priority goes into a folder I have called AFCD2Sscenery that has a very high priority (lower number toward the top) in the FS scenery library. As always if changing any scenery priority or scenery elements, run FS to index the scenery, then close it, open RC, and run the Scenery Rebuild utility to update RC's data.Regarding getting out of position when taking vectors from RC, insure you (if not on pilot auto-reply) promptly acknowledge any ATC commands so RC will give the next command in a timely fashion. Make sure you have met your altitude crossing restriction. If you are flying under arrival NOTAMS RC will disregard any navigation errors and could let you fly past various boundaries.If you are flying a medium to large aircraft an ILS merge at four miles out is highly unusual and in most cases except in very unusual conditions much too close. RC will usually give you a vector to get you the intercept from seven to twelve miles out.For FAA airports I recommend you go to www.flightaware.com, key in the destination airport and click on airport information. Then download the bundle of charts (in one .pdf file) for that airport and look at the approaches. Keep in mind that these are current charts and may differ from the scenery elements in FS which are determined at the time of the scenery build.In the approach chart note the altitude and position of the LOC/GS intercept indicated by the "X" or other mark. That should be the minimum distance from the threshold of the intercept at which you are lined up.Last, Otto (your RC copilot) should not be flying the aircraft in the approach.

Ok thanks for all your help. I do have the CoPilot on even up to landing. The reason for this is I thought the pilot had over ride of the Co pilot actions. I put the headings in and speed ect. He just handle the radio. I do not have it on pilot auto-reply. I know Ctl + Shift + K activates the CoP. So what do I use to deactivate it?

ctrl-shift-k to switch the copilot to comms, ctrl-shift-k to switch the comms back to youjust because the copilot has the comms, you still have to fly the plane, and make the heading and altitude changes.ctrl-shift-m switches the flying from you to the co-pilot and back. but that only works if the plane has a standard ms autopilot setupjd

I have tried to land at 3 different airports and I will get my vectors to final, runway to land on ect. I use FSNavigator as my planner. RC will not let me fly my planner. It will tell me to decend sooner that the plan call for, take me off my track. When it does this I can watch the plane fly on the map. Instead of it taking me to line up with the runway to land, it still takes me around it. LAst night when I flew from KMSY to KBHM it gave me to land on runway 6 which is from the E. It took me off track to the N toward Ga. for about 50 miles from the airport. I finally asked for a ILS approach which the ATC began to give me a different heading back E. then SE finally back toward the NW. As I was looking on the map and using my GSP it again took me past the runway which was to my left. I sent jd my debug but for some reason nothing was in the attachment. I opened it up and read it just fine. I like RC but with all these problems i'm beginning to think that the MS ATC is better. If someone can give me more ideas that will be just fine.

your .pln is a just a flight .pln, departure, center and approach are going to do what they need to do, to make your flight safe, and accurate.rc doesn't care what your .pln has for altitudes. it cares about your cruise altitude, otherwise, it will assign altitudes in a way that mimics the real worldit is odd that you're approaches are messed up. if everyone's approaches were like yours, no one would buy radar contact. the reviews would be terrible. neither is the case.so there is something unique about your installation, or your flying that is causing the problem.as explained earlier, i have to see a .log file to tell what is going wrong with your flights. so far, you have forgotten to turn on debug, or your .log files are empty.i emailed you specific instructions on how to make a .log, please follow them, duplicate the problem, and send me a .log - so i can see what is going wrong in your flightsjd

Ok I flew the same .pln again. This time after I had to go missed it finally took me to the runway to land. Will try to send the .log file. It's 18M and on dial up will take some time.

You can compress the log file with a zip utility and attach it to your e-mail. That should cut the size to one third of the original or more.You can use the built in folder compression utility in Windows XP. Look in the Windows help section for "zip" or "compressed folders".

everything looked fine.You made your crossing restriction, you were told to descend and maintain 9000, fly heading 350Then you were told to fly heading 235Then you were told to descend and maintain 4000 when you were abeam of the field on downwindYou were told to turn to base and maintain 3000You were told to fly heading 25, descend to 2700. Is this where you think you were forgotten? There are no further vectors at this point. It is up to you to turn from the intercept heading to the runway/ils heading. Did you fly through the localizer? You should have turned and joined it. that is approach