While on the ground, communication between RC4 and pilot is fine. But after a while in the air, there is as much as a 60 sec delay between the controller command and the pilot's response. What could be causing this?I just did a flight where I had this delay problem, along with RC4 thinking I was off course, but I was actually on course. Also, there was a delay in keyboard response. The key assignments worked, but there was a long delay for them to work.RC4 had me so frustrated, I had to kill it and continue the flight using the default ATC. These problems do not happen all the time, but it is happening enough to really make me want to give up on RC4.jps

can you send me a .log? instructions are posted at the top of the forumdo you have recorded chatter checked? try unchecking it.this isn't the experience you should be having, so there must be something else going onhave you defragged your disks? both the disks that rc and fs are onis this widefs installation?what os?what anti virus program are you runningwhat kind of sound card? or is it motherboard sound?jd

after looking at the log you sent, it looks like you have autosave running. in case others might search for this topic in the future, i'll delve further into thiseverytime autosave kicks off, and saves a .flt/.wx file, rc also dumps all of it info into a .rcd filethis can be time consuming, especially in center, when a lot of other stuff goes on.so i would change the interval autosave kicks offon the off course thing. you probably missed a checkpoint. the fsuipc/rc display shows the next checkpoint rc is expecting you to be flying towardsif you have a departure procedure, you're expected to fly less than 2 miles from each checkpoint.if this was a departure procedure, there is a tutorial on that, maybe read it, and fly it.if this was non departure procedure, don't be to quick to fly direct to the next checkpoint in your plan. you still have to fly the headings tower and departure give you. only when you hear resume own navigation, can you fly direct the next checkpoint. (that does not mean turn 90 degrees, so you can get on the little green/pink/blue/color de jeur line, on your fmc)jd

Thanks for your help jd. It looks like the ride is smooth now.I installed RC4 4.3.3845 and it made a big difference. I also checked my autosave cfg. file and it was saving every 60 sec. I changed it to every five minutes and now all keys are functioning correctly with no delay and also sometimes, just a bit of delay in response between controller and pilot, but nothing like before. Also, I have not had the "off course" problem yet either. I am very pleased with the results!Many Thanks jps

I spoke too soon. After four flight with few problems, the old problems are back again.Long response time between pilot and controller and keyboard commands with long lag time.I think it is time to give RC4 a rest.jps

why, you know it works. rc doesn't get tired and stop working.why not delete the autosave dll.what changed between the time it was working, and now?can you send me a .log, with these long delays again?jd

I don't want to start a new topic, and it's close enough to this one that I'll post here.I've noticed that when I'm getting vectors to final, I get told to turn my intercept course when I'm almost on top of the localizer or even past it sometimes. The heading it gives is one that would be correct as far as a 30 degree difference from the localizer heading, but it gives it to me a bit late. I've also noticed traffic calls are often late - I'll see a plane at 2 o'clock and then I'll get a traffic call for it at 2 o'clock, but by the time the traffic call comes it's at 6 or 7 o'clock.My setup is running RC4.3 via WideFS running in a vmware guest on a Macbook Pro. Which could account for some of the slowness, if not be the entire problem. I haven't tried it on the FSX machine yet, because I attempt to run everything off-machine if I can.Would a log help?Thanks,-stefan

try it on the fsx machine. let's eliminate the obvious culprit.jd

OK, ran it on the FSX machine today for a flight from KORD-KLAX in the LDS 767. Got turned to a heading of 280 for runway 24R and altitude of 3200 when I was nearly on top of the localizer. I had been at a heading of 230, altitude 5000 which makes it extra puzzling. STAR was HEC.RIIVR1I didn't make a log, but got turned from 230 to 280 at approximately PALAC.-stefan

without a log, i'm blind to what is happeningjd

Running on a virtual OS can really slow things down. You have network delay, passing of the wav. files via the virtual OS to the MAC OS to its audio drivers, and you have an integrated sound chip on the mobo, I believe. You are also a bit slower on disk access that concatenates the .wav files for the chatter because of all the virtual to actual disk access stuff.I do not think the Macbook Pro is Intel based. If it were you could boot Windows on it with a dual boot and have its own partition I believe.

No, it's the good intel-based one. I have boot camp installed on it but I prefer to run it in the vmware window so I don't have to reboot. But, the delay was there even taking that computer out of the question. The FSX computer is a Intel Core 2 Duo E8400 with 4GB RAM, Windows XP Pro SP2, and an ATI Radeon X1900XTX. Should be enough.I'll try to do a short flight and make a log for you guys sometime soon.-stefan

Any resolution on this? I have the same problem constantly. When I press 2 to get ATIS there is a full minute delay before audio. Then when I press 1 for clearance there is a full minute before I ask for clearance. Then another full minute before I get the "on request" message. Then a full minute before I get the menu option for 7 to acknowledge. This lag continues for the entire session. Uunusable, so I turn it off and fly without ATC. Very frustrating as I LOVE flying with RC4. XP Home, FS9.1, Maddog... Aeroworx King Air... even the default Cessna, ASV6Any ideas? I wanna play! Thanks, EddieKABQ

do you have display text checked on the options page?jd

No sir. I have unchecked AI chatter and that makes no difference either.