Hi there,I hope this isn't in a FAQ somewhere....I looked around but didn't find anything.I did a flight yesterday with RC 3.10 and FS9.1 in the LDS767 from KDEN to KSTL. I used FSBuild 2.2 to create the flight plans for all three items. RC seemed to work just fine coming out of Denver and across Kansas (pointing out traffic and giving frequency changes), but it never told me when to descend (even when only 90 miles from STL), and it never picked up with vectors to the runway. There are a few things I did which may have confused RC...any idea if any of these are the culprit?(1) I have upgraded FSBuild and the LDS FMC with the latest AIRAC (0504). I did not however update the RC database (didn't think to do that).(2) I wanted to "file" a normal route, but the AIRAC has a bad point in what it thinks is the ANX.TRAKE8 STAR...it had a waypoint COORS that was 7000 miles away, so instead of using its version of the TRAKE8, I programmed my own as follows: ANX ANX105065 TRAKE KAYLA FTZ AUGST SNYDR. Notice the one oddball, ANX105065, which is where the ANX 105 radial (at 65 DME) intersects the FTZ 265 radial. FSBuild seemed to put this in about the right point, and the LDS FMC flew this properly, but I was wondering if this point confused RC?(3) I had FSBuild build an RCV2xx.apl flight plan, as I didn't see a 3.xx version, and this is what I loaded. This morning when thinking about it, I wondered if maybe I should have used the FS200x.pln file instead. When I loaded the .apl, the RC window showed: KDEN to KSTL @ 39000 (Alt1-, Alt2-)/, whereas when I load the .pln I get that plus the route: EXTAN.TXC.GLD.HLC.SLOWR.CATTS.MCI.ANX.05065.KAYLA.FTZ.AUGST.SNYDR. Again I see my intersection, but now it has a funny name (05065).(4) After I reached SNYDR, I decided to vector myself onto downwind, since I figured RC had given up, since I had been given no descent and no vectors. I flew a long downwind (20+ miles), and when I turned base RC then gave me a vector which would have taken my back onto the downwind. At that point it also started complaining about my altitude, since I was descending below the minimum I could request (10,000), so RC was still very much alive, but didn't seem to want to take me to STL.Any help would be appreciated.Thanks in advance,Keith

I think it has something to do with FSBuild and the RC .apl plans it exports. I flew a KBOS to EGLL and got to a point near Cornwall where the next waypoint was listed as over 2000nm away... Course, I wouldn't expect vectors at that point ;) Having FSBuild export to FS2002/4 and using FSNavigator to make an RC .apl (or reading the FS2002/4 file) seems to work better. Anyone else with FSBuild having problems?

when you have a choice of saving a flight plan in .pln (fs format), do it. it is much more useful than the old .apl file formatmake sure there is a vor/ndb/intersection near the arrival airport..pln and something near the airport - give those things a try and see what happensjd