Up until now, I was reluctant to try RC, mainly due to it's lack of ground control. I tend to fly to many different airports, which I'm not familiar with and don't have charts for, and have always relied on FS ATC to direct me on the ground, I'm going to miss that in RC! That being said, after the many raves from the community, I finally decided to try it, and have just completed my first flight in my LDS 767 with it, and I have to say, it's everything everybody says it is! I do have a coupe of issues to report though! My flight was between KMCO and KDFW, after departure I was vectored on a course of 255. When I got to 12000 ft, I was directed to continue of 255 and then at or above 16000, cleared direct to PIE (My first way point on my flightplan) and continue normal nav from there, (Nice touch by the way!!) I switched to LNAV at 16500, which put me on a coarse direct to PIE. After a few moments though (Before I reached PIE), it reprimanded me told me I was off course and to go back to 255, which I did, and shortly after sent me back on direct. At the end of my flight, the Flight Critique feature dinged me for navigational error of which that was the only one ATC complained about. The other issue is as others I have seen reported, there is a lot fewer AI communication then I'm used to with Default ATC. (I don't use the canned chatter) On the ground it seems ok, but once in the air it's few and far between. I flew from Orlando, all the way to the middle of Georgia before there was an AI call for traffic with my aircraft, then after there was only 1 AI call to center all the way to DFW. On approach there was some more, but not as much as I would expect at DFW. Other than those 2 issues, ATC directed me for a perfect ILS approach to Runway 17L Then I was left to fend for myself, to find Gate A38! (never did). Ah well, I guess you got to take the good with the bad!!

i'm not sure what happened. nothing comes to mind as a newbie mistake that would have caused that.if you think you can duplicate it, follow the directions pinned at the top of the forum, on how to generate a .logbe sure to click debug before you load the .plnas far as the ai chatter, the ai have to be on the same frequency for you to hear a conversation with you. enroute, you have to be in the same sector and/or center and stratum as you.on approach, i only talk to the ai that are landing on the same runway as you. otherwise we found early on, it was radio congestion.if you do the .log, and you think there is an ai that i should be talking to, make note of the call sign, and i can look at that toojd

Thanks, I'll have to try the log feature! Last night, I flew a flight between SEA and SFO, and same thing happened. On departure RC was talking to some AI, not sure about all, as it looked like there were more active AI taxiing then RC was talking too. Once I was switched to center, I didn't here a pep until on the approach to sfo! This morning was a little more definitive and I have a theory on what may be happening. Let me know if I'm all wet! On taxi to the runway there was a delta 757 in front of me, and after switching to tower frequency, I heard the call for it to position and hold, followed by clearance to takeoff! As it was taking off I was cleared to position to hold followed by takeoff clearance. I listened though, and the Delta in front of me never was switched to departure frequency, and was never heard from again. After I took off and switched to departure shortly after the next plane to takeoff an AirTran 737 was heard contacting departure. So my question is it possible that the default AI is switching the frequencies of the AI aircraft before RC gets the chance to talk to them? If so is there a way to prevent it from doing that. I should ad this is with the FSX RC! I haven't tried FS2004.

hard to sayonly a log, and a list of ai callsigns in question will answer those questionsjd

>hard to say>>only a log, and a list of ai callsigns in question will answer>those questions>>jdI think I figured out what's missing! RC is handling ground AI through takeoff. It also handles change to center, traffic conflicts and final approach well. What's missing, is the ascent and descent calls for AI aircraft, which makes up a good amount of calls FSX default ATC handles. Of course those calls are handled for the players aircraft. Also missing is enroute heading calls for AI, but I would expect that, as it's more realistic for commercial aircraft, to follow their own navigation, another thing that default doesn't do well.

I assume the LDS 763 FMC works like the 737 FMC.When you assumed direct navigation to PIE did you update the PIE waypoint from your present position on LEGS page 1? You do that by punching LSKL1 twice (PIE will appear in the scratchpad on the first punch and on the second it will calculate the direct course. You then EXE it followed by an LNAV engage. If you do not do this the aircraft will return to your current flightpath.Regarding traffic, I assume you have Interact with AI enabled and Use Prerecorded chatter off. RC will regenerate chatter of AI present and on the same frequency. It depends what AI are in your area and on the same controller's jurisdiction. Enroute are generally light consisting of mostly traffic caution recognition so your AI content and flight plans would affect the amount of activity. This includes density, routing, and scheduling. I use Ultimate Traffic at 100% and at dense US Airports I hear quite a bit of chatter in their vicinity. It is possible that AI and RC may be using different frequencies especially at departure and approach since there often are multiple frequencies for AI to use.

>I assume the LDS 763 FMC works like the 737 FMC.>>When you assumed direct navigation to PIE did you update the>PIE waypoint from your present position on LEGS page 1? You do>that by punching LSKL1 twice (PIE will appear in the>scratchpad on the first punch and on the second it will>calculate the direct course. You then EXE it followed by an>LNAV engage. If you do not do this the aircraft will return to>your current flightpath.Thanks, I do know about updating the first waypoint this way, and did do just that! I have to admit though I didn't reverify the course once I switched to LNAV so maybe it didn't take for some reason! I flew another flight earlier today and got this same call but this time there was no nav error recorded. Somehow it must have been me!>>Regarding traffic, I assume you have Interact with AI enabled>and Use Prerecorded chatter off. RC will regenerate chatter of>AI present and on the same frequency. It depends what AI are>in your area and on the same controller's jurisdiction.>Enroute are generally light consisting of mostly traffic>caution recognition so your AI content and flight plans would>affect the amount of activity. This includes density, routing,>and scheduling. I use Ultimate Traffic at 100% and at dense US>Airports I hear quite a bit of chatter in their vicinity. It>is possible that AI and RC may be using different frequencies>especially at departure and approach since there often are>multiple frequencies for AI to use.>>>I've flown 5 flights so far, I did create a log for one, so I'll send that to JD. I turned in the sound for FSX default, and in every case there was a ascent or descent call in FSX default (So I know they were on the same frequency I was!) RC was silent. It's hard to point to a specific case, because it was all. Next flight I'll run a log and listen to default ATC for some callsigns JD can look at, but the problem seems to be global! The longest RC flight I have taken so far has been from EGCC to KMCO, which routed me toward the Boston area, then toward New York and down the eastern US seaboard, and all through the flight no one other than me climbed or descent.

If you had a flight with extremely long distance between waypoints, perhaps greater than 200 nm, there might have been a difference between great circle navigation heading calculations and direct to waypoint ones. I do not know if that was changed in RC to correct for this. Does that apply to the leg you had difficulty with?>Thanks, I do know about updating the first waypoint this way,>and did do just that! I have to admit though I didn't reverify>the course once I switched to LNAV so maybe it didn't take for>some reason! I flew another flight earlier today and got this>same call but this time there was no nav error recorded.>Somehow it must have been me!>

i think that was fixed in 4.2 or 4.3jd