Hi Ray,I have just flown the DVR SID from RWY 08 at EGGW again as the wind had changed direction again. This time I handed the comms over to the co-pilot and RC4 tracked the SID (including LUT) as the aircraft flew it. The whole flight was uneventful this time, apart from the co-pilot acknowledging two calls from the ATC which were not announced. I'll have to give the RWY 26 departure another go, hopefully I'll get the same result which would point to RC4 polling for an acknowlegment keystroke and slowing down it's tracking response.Although nothing to do with RC4, I thought I would mention that today the landing and departing runway was 08 and I and other aircraft taking off and landing were directed to 08, one aircraft decided to land on RWY26. I wonder if this was caused by a wind update from ActiveSky switching direction?Thanks for you input, appreciated.Tony

Hi Guys,Have followed this thread with some interest.I use the Wilco airbus vol 1 with a payware update to the panel and other gauge logic from eric marciano. This update helps the FMC logic and may help to get rid of the problems which Tony encounters .Due to time constraints I will not be able to test it out by flying the route out of Luton until Thursday evening.I will let you know what happens.BTW Wilco are producing are further service pack/update for Vol 1 with some input from Eric.I do not have any other info.Norman Bowman

Hi Ray,I have just flown the DVR SID from RWY 08 at EGGW again as the wind had changed direction again. This time I handed the comms over to the co-pilot and RC4 tracked the SID (including LUT) as the aircraft flew it. The whole flight was uneventful this time, apart from the co-pilot acknowledging two calls from the ATC which were not announced. I'll have to give the RWY 26 departure another go, hopefully I'll get the same result which would point to RC4 polling for an acknowlegment keystroke and slowing down it's tracking response.

That's encouraging Tony. If you fail to ack an instruction (or even a TCAS advisory) it can prevent RC from crediting you for passing waypoints. I'd be interested to hear how you fare on the 26 CPT departure out of EGGW.

Although nothing to do with RC4, I thought I would mention that today the landing and departing runway was 08 and I and other aircraft taking off and landing were directed to 08, one aircraft decided to land on RWY26. I wonder if this was caused by a wind update from ActiveSky switching direction?

That's a difficult one to answer and probably needs a log to JD but replicating the scenario may be difficult.

Thanks for the post Norman. I'll keep an eye out for any update that Wilco may release.Tony

Hi all,I flew the EDDW RWY26 to LEBL again today. As with the previous flight from RWY05, I handed over comms to the co-pilot just before take off. And lo and behold RC4 tracked the SID okay. It was a bit sluggish responding to some of the waypoints and updated sometimes after the waypoint had been passed. I also noticed on a few occasions that the co-pilot responded to commands that had not been spoken by the ATC. So it would seem that the problems I experienced were due to timing. Handing the comms over to the co-pilot allows the acknowlegdment to the controller to take place immediately as soon as RC4 is able to accept the response. When doing it manually I would press the 1 or 7 and it would be a while before the reply kicked in. What made it worse most probably is that sometimes I would adust the autopilot settings as the controller was speaking and this could have introduced a slight delay before hitting the keypad. If RC4 was polling for a response it could be missing the passing of a waypoint as it doesn't take long in an Airbus to travel 2 miles past the waypoint and beyond the allowable tolerance for a credit. Hopefully I won't experience any repeated tracking problems now that I have seemed to found an acceptable work-around.Thanks for all the input guys,Tony

That's good to hear Tony. All the conditions you describe are symptomatic of a PC struggling to keep up with the demands placed on it. My guess is the panel for your aircraft and FSX in general. But using your workarounds you should be able to enjoy RC4.

Hi Tony,Flew the flight to LEBL and found that the aircraft followed the Sid but,like you the RC responses are slow to say the least.Things improve if you turn off AI chatter.I also tried by allocating a specific core to the main programs and that produced a near normal response rate from RC 4.3.The bottom line is that with some addons in FSX RC4.3 is struggling for its share of the computer resources at any given time.For example the QW 757 is another aircraft which causes a slow RC response.Using FSX I have found that the best results come when I allocate cores to specific programs.FSX core 1 RC4.3 core 4 and ASE to core 3.Norman Bowman

Hi Tony,Flew the flight to LEBL and found that the aircraft followed the Sid but,like you the RC responses are slow to say the least.Things improve if you turn off AI chatter.I also tried by allocating a specific core to the main programs and that produced a near normal response rate from RC 4.3.The bottom line is that with some addons in FSX RC4.3 is struggling for its share of the computer resources at any given time.For example the QW 757 is another aircraft which causes a slow RC response.Using FSX I have found that the best results come when I allocate cores to specific programs.FSX core 1 RC4.3 core 4 and ASE to core 3.Norman Bowman

send me a log, instructions pinned to the top of the forum. duplicate the problem, making notes of where things are slow, and what was happening (pan am 101 said this, or southwest did this). then zip up the log and send it to me, with the "what happened" items in the email. i'll see what was going on. also make sure you click debug before you load your planjd

Hi jd,I will be unable to make a log until next week sometime.Perhaps Tony might be able to help as he is also running into thses problems.I will still do a log and send it to you.Norman Bowman