Been having a problem recently with RC4.Tried to fly from EGLL to DAAG twice on different flight plans in two different aircraft (PMDG 737 and Captain Sim 757) and both times the same problem has happened.Fly the flight fine, definitely don't miss any waypoints or anything, but ATC just seem to forget about me, and give me no instructions to descend or anything, and I'm left flying past the airport at FL33.Also, the "Pause at distance" feature has seemed to stop working too, I don't know if this gives any clues?Any help is greatly appreciated.I also have MeatWater's voice packs include if this makes any difference.

Need more details:At what stage of flight did ATC stop communicating.Were you or your co-pilot in aircraft command and comms.Did RC continue to respond to menu commands. Are you using any add-on that might be causing key conflicts. One is enabling keyboard capture in an FMC.FS version, FSUIPC version, makerwys.exe version.On the RC menu were there any outstanding acks for you to do. Not doing this can cause RC to stall.You state only a recent problem. Any new add-ons installed?I recall a problem with the original DAAG afcad in FS9 that was corrected from a specific download from their site. Is this a specific problem with DAAG as your destination?You also need to alt-tab out of the FS window to see if it is covering an error pop-up.Last, if nothing immediate comes to mind, you'll have to submit a log as shown at the pinned forum at the top.

Hey, thanks for your swift response.ATC communicated throughout the flight, and still continued to hand me over to other centres up until the final destination, but gave no descent clearance.Definitely no outstanding acks, however, just tried a flight from TNCM to EGLL and this worked fine, so I would assume it was something to do with DAAG.I will try the recommended download and hope for the best. It is an add on DAAG, I can't remember who by, but I will look.Thanks again

I had trouble with the FS9 download afcad version of DAAG. I looked at it and there are two layers besides the default. To insure RC is getting the correct data be sure you are using makerwys.exe version 4.1 or better in your FS folder. Update it from the link at the forum top and then from within RC run te scenery rebuild. 4.41 takes care of some scenery library priority issues particularly with scenery layers in the same scenery folder.There is a 2007 newer version here (not the older version I am using):http://riadg.free.fr/You can check on the runway data RC has. Go into your rc4\data folder and make a safe copy of r4.csv. Then open r4.csv in Notepad (not Excel) and search for DAAG. You should get four lines like this:DAAG,0050,36.694267,3.220511,82,54.400,11300,0,197,-1.000,36.703506,3.236030,0,,CLDAAG,0090,36.691734,3.169776,82,92.200,11769,108.50BG,148,-1.000,36.691395,3.189902,0,CT,DAAG,0230,36.712746,3.251549,82,234.400,11300,110.30BDG,197,-1.000,36.703506,3.236030,0,CT,DAAG,0270,36.691055,3.210027,82,272.200,11769,0,148,-1.000,36.691395,3.189902,0,,CLRunways 9 (0090) and 23 (0230) have LOC, ILS only and are intended for landing. Each is closed at one end for takeoff and 5 and 27 closed for landing. Unfortunately AI in FS9 only pay attention when the same runway privileges exist at both ends of the same runway. RC4 does not use this information.On approach RC will suggest a runway for you. If it is not 9 or 23 then select one of these nearest the same direction of the RC recommended runway to avoid AI conflicts.I got the corrected afcad from the forum of the DAAG design site after I notified them of a problem. This was from an older version of their scenery. If you need this send me a PM with your e-mail address and I'll send you the version I have. Just rename the extension of your current version and install this one if needed, and then start FS so it reindexes your scenery, stop it, and then from within RC again run the scenery rebuild.