TonyButler

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

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

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,Thank you Ron and Ray for your responses. I remember a single waypoint HEN at the top of the RC4 window and a predictive turn missing a waypoint. In concentrating on HEN remaining in the window and no other waypoint indicated I have obviously confused the turn at COMPTON as being at HEN. I apologise for the misinformation. So that leaves me even more perplexed. Why did RC4 track passing the waypoints up to HENTON? And since COMPTON is beyond the 30 mile range it has the 5 mile latitude which the turn should have been well inside.With the other problems encountered, is this a sign that RC4 is struggling to keep up on my setup? I have a 3GByte Duo core with 4GB of RAM and GeForce 8800 GTX (768MB) running Windows 7 (64bit) Pro. FSX doesn't seem to perform as well as it did under Windows XP (32bit) Pro despite checking there are no other none essential background tasks running. I won't rant on about Windows 7 as this isn't the place to do it, but I will mention that using DX10 on my machine is definitely a no,no. With DXT10 flying the Cessna at Seattle I was getting around 5-7FPS, switch back to DX9 and it shot up to 25-30FPS. As well as RC4 and the Feelthere A319 PIC I have Ultimate Traffic 2 running which inserts AI traffic through the FSX interface instead of using the default AI BGL. This last flight also had ActiveSky running as well, but even without it the time it takes for the RC4 window to respond is very slow. Enroute I responded to ATC with keypresses before the window had displayed the key options (trying to break into the 'turn around-ack cycle') and think that is why I ended up with an EMERGENCY declared. I wonder if the FSX interface is a bottleneck restricting the response of RC4? However, I most probably wouldn't have run into so many problems in the last flight had control accepted my DIRECT TO request.So the solution seems to be as you suggest Ron. Edit the FS flightplan to create a separate flightplan for RC4 without the SID waypoints. Barcelona, here I come again!Tony

Hi,I have just flown the Luton to Barcelona flight again but was directed to depart from RWY 26 instead of RWY 08 due to the weather conditions. Likewise, landing was at RWY ILS25R at LEBL. Once again RC4 missed the waypoint at HEN on a predictive turn (see the flightplan below). RC4 progressed from take off and D0351 through to D345E okay but then missed HEN. It seems RC4 is happy as long as there are no sharp changes in direction. I tried to DIRECT TO a waypoint beyond my position but was told it was not possible at the time and to wait 4 minutes. I kept trying but by the time I could get back into the DIRECT TO command I was then in the scenario where I was constantly being redirected back to HEN and back in the "you're off route turn around" (and stupid comments about driving skills) - acknowledge - "you're off route turn around" - acknowledge loop, and the DIRECT TO was no longer a menu option. I was by this time over France, and in trying to acknowledge the change in direction and concurrently acknowledging the request to change frequency I think RC4 got confused with my keystrokes as an emergency was declared. I didn't accept any of the airports offered and waited. Eventually I was asked to contact another centre and the normal screen appeared but with LEBL as the next waypoint some 200 to 300 miles ahead. I then came up against another problem. Control kept asking me to change frequency to another centre but would respond to key 1 with a buzzer and N/A in the window. It would respond to key 7 but that was not what was required and control kept nag, nag, nag. This went on for ages and I was getting very frustrated and frayed around the edges. I then hit on the idea of handing comms over to the co-pilot. That did the trick and everything carried on to the point of vectoring and landing. One of the annoying outcomes of being unable to change frequencies via RC4 (I did it manually but the frequency change wasn't recognised by RC4) was that I was locked at FL230 for most of the journey. In the end I climbed to FL370 but got kicked back down to FL330 and then up to FL370 again after the co-pilot got the ATC back. I know the problem with RC4 missing waypoints as a result of predictive turns can be resolved by creating a flightplan with gentle changes in direction. But I want to use SIDs and not have to have a flightplan doctored for RC4. Reading the manual it says RC4 will treat any checkpoint within 30 miles as a departure procedure checkpoint and you must fly within 2 miles of the checkpoint. Outside the 30 mile range from the airport is considered to be enroute and the checkpoint tolerance is 5 miles. I find it annoying that the tolerance is tighter in the part of the route in which you are more likely to get sharp changes in direction (the SID) and where predictive turning has to be used or the aircraft will overshoot and end up swinging to and fro hunting to get back on the route. The tolerance is greater enroute where there are more gentle turns. I don't know if RC4 was designed to be like this to represent the real world of ATC, but the Flight Simulator autopliot has a lot of retrictions preventing aircraft from behaving the same as an actual aircraft. Perhaps the tolerance on DPs is too tight for RC4 when used with FS. It wouldn't be so bad if ATC had accepted a DIRECT TO so RC4 can be resynchronised with FS, instead it rejected the request. Is there a way of changing the tolerance to be a bit more accomodating?Regards,Tony[flightplan]title=EGGW to LEBLdescription=EGGW, LEBLtype=IFRroutetype=3cruising_altitude=37000departure_id=EGGW, N51* 52.29', W000* 22.06',+000526.00departure_position=26destination_id=LEBL, N41* 17.49', E002* 04.42',+000014.00departure_name=LUTONdestination_name=BARCELONAwaypoint.0=EGGW, A, N51* 52.29', W000* 22.06', +000000.00, waypoint.1=D035I, I, N51* 51.09', W000* 25.12', +01000.00, waypoint.2=D035G, I, N51* 49.28', W000* 26.56', +01000.00, waypoint.3=D345E, I, N51* 47.44', W000* 35.07', +03000.00, waypoint.4=HEN, N, N51* 45.34', W000* 47.25', +05000.00, waypoint.5=RODNI, I, N51* 42.56', W000* 51.42', +06000.00, waypoint.6=CPT, V, N51* 29.30', W001* 13.10', +12000.00, N859waypoint.7=VAPID, I, N51* 15.14', W001* 02.41', +16000.00, N859waypoint.8=GWC, V, N50* 51.18', W000* 45.24', +24000.00, N859waypoint.9=GWC06, I, N50* 46.26', W000* 40.10', +26000.00, N859waypoint.10=GWC15, I, N50* 38.53', W000* 32.09', +28000.00, N859waypoint.11=DRAKE, I, N50* 12.33', W000* 04.33', +37000.00, UA34waypoint.12=SITET, I, N50* 06.00', E000* 00.00', +37000.00, UN859waypoint.13=ETRAT, I, N49* 40.59', E000* 09.47', +37000.00, UN859waypoint.14=DVL, V, N49* 18.38', E000* 18.45', +37000.00, UN859waypoint.15=LGL, V, N48* 47.26', E000* 31.49', +37000.00, UN859waypoint.16=SORAP, I, N48* 31.19', E000* 38.07', +37000.00, UN859waypoint.17=BENAR, I, N48* 15.11', E000* 44.39', +37000.00, UN859waypoint.18=VANAD, I, N47* 50.13', E000* 54.25', +37000.00, UN859waypoint.19=AMB, V, N47* 25.44', E001* 03.51', +37000.00, UN859waypoint.20=BALAN, I, N46* 30.57', E001* 01.59', +37000.00, UN859waypoint.21=BEBIX, I, N45* 56.57', E001* 23.58', +37000.00, UN859waypoint.22=OBUBA, I, N45* 34.45', E001* 28.46', +37000.00, UN859waypoint.23=TUGLI, I, N45* 22.37', E001* 31.27', +37000.00, UN859waypoint.24=TUSAK, I, N44* 39.02', E001* 40.33', +37000.00, UN859waypoint.25=NARAK, I, N44* 17.43', E001* 44.56', +37000.00, UN859waypoint.26=GAI, V, N43* 57.14', E001* 49.27', +37000.00, UN859waypoint.27=LOMRA, I, N43* 20.39', E001* 52.59', +37000.00, UN859waypoint.28=ROCAN, I, N42* 40.23', E001* 56.48', +35000.00, UN859waypoint.29=PUMAL, I, N42* 22.00', E002* 00.30', +27000.00, waypoint.30=BERGA, I, N42* 10.17', E002* 01.55', +22000.00, waypoint.31=D356Y, I, N41* 56.07', E002* 03.37', +16000.00, waypoint.32=D356J, I, N41* 41.09', E002* 05.24', +10000.00, waypoint.33=SLL, V, N41* 31.11', E002* 06.35', +06000.00, waypoint.34=LEBL, A, N41* 17.49', E002* 04.42', +000000.00,

Thanks for the tips Ron. I have the latest FSBuild and AIRACs but there are a number of things you mentioned that I hadn't considered, been aware of, or didn't know how to overcome. This was very useful information and should be added as an addendum to the RC4 manual as I expect many other people have experienced problems that your tips will help eliminate.Thanks again,Tony

Hi Andrew,I found that I was unable to get a response to 0 or 9. I presummed that once RC4 tried to get me to turn around it was locked in a cycle of ATC telling me to turn around, acknowledge, you're not doing as you are told, turn around, acknowledge. Any other keypresses seem to be ignored. Next time I'll try to remember to look and make sure the next waypoint in RC4 matches the one in FSX, if not try to take steps to do a direct to. Thanks for letting me know I am not alone in experiencing this. The flights I tend to get this happen to most frequently are from Luton, UK, which seems to confirm it is RC4 not detecting the LUT waypoint of a SID has been passed.Regards,Tony

I think you are right in your analysis Ronzie. I flew the Feelthere PIC A319 from the Airbus Series 1 and used FSBuild to generate the flightplan and export to FS2004 (for RC4), FSX XML (for FSX), and Wilco/Feelthere A320 (for the A319). I have tried attaching the flightplans using the Forums Flash Uploader but get the message "You aren't permitted to upload this kind of file". I also tried the single "Attach this file" after I zipped them up and got the same message. So I have copied the FS2004 flightplan to below along with the RC4 file contents.Anyway, it would appear that RC4 missed the LUT waypoint because, as you pointed out, the autopilot uses predictive turning before the waypoint. What was surprising was that RC4 waited until I was under Paris control and half way down France before it tried to force me back to LUT. I don't recall seeing the option in the RC4 windows "for a direct to", only requests for flight level changes or get weather. I tried option "0" for the Main menu but all I kept getting was the nagging "You are off course..." and 7 to acknowledge. It wasn't until I was near Barcelona that the ATC realised I was near the destination. RC4 then vectored me away from the STAR and on to final approach "because of the density of traffic".As I mentioned previously, this has happened a few times before on other routes and I think the reason is as you state. Once again, it is after I am well into the route before ATC wakes up to the fact a waypoint has been missed. I will look out for the "Direct to" option the next time I fly and use it to sychronise with FSX. Thanks for pointing this out.Regards,TonyEGGW-LEBL.PLN[flightplan]title=EGGW to LEBLdescription=EGGW, LEBLtype=IFRroutetype=3cruising_altitude=37000departure_id=EGGW, N51* 52.29', W000* 22.06',+000526.00departure_position=08destination_id=LEBL, N41* 17.49', E002* 04.42',+000014.00departure_name=LUTONdestination_name=BARCELONAwaypoint.0=EGGW, A, N51* 52.29', W000* 22.06', +000000.00, waypoint.1=LUT, N, N51* 53.40', W000* 15.09', +01000.00, waypoint.2=D337F, I, N51* 50.23', W000* 10.32', +03000.00, waypoint.3=D337C, I, N51* 47.39', W000* 08.24', +03000.00, waypoint.4=BPK, V, N51* 44.58', W000* 06.24', +04000.00, waypoint.5=D099G, I, N51* 44.10', E000* 04.47', +06000.00, waypoint.6=D099N, I, N51* 43.20', E000* 16.00', +08000.00, waypoint.7=DET, V, N51* 18.14', E000* 35.49', +16000.00, waypoint.8=ETRAT, I, N49* 40.59', E000* 09.47', +37000.00, UN859waypoint.9=DVL, V, N49* 18.38', E000* 18.45', +37000.00, UN859waypoint.10=LGL, V, N48* 47.26', E000* 31.49', +37000.00, UN859waypoint.11=SORAP, I, N48* 31.19', E000* 38.07', +37000.00, UN859waypoint.12=BENAR, I, N48* 15.11', E000* 44.39', +37000.00, UN859waypoint.13=VANAD, I, N47* 50.13', E000* 54.25', +37000.00, UN859waypoint.14=AMB, V, N47* 25.44', E001* 03.51', +37000.00, UN859waypoint.15=BALAN, I, N46* 30.57', E001* 01.59', +37000.00, UN859waypoint.16=BEBIX, I, N45* 56.57', E001* 23.58', +37000.00, UN859waypoint.17=OBUBA, I, N45* 34.45', E001* 28.46', +37000.00, UN859waypoint.18=TUGLI, I, N45* 22.37', E001* 31.27', +37000.00, UN859waypoint.19=TUSAK, I, N44* 39.02', E001* 40.33', +37000.00, UN859waypoint.20=NARAK, I, N44* 17.43', E001* 44.56', +37000.00, UN859waypoint.21=GAI, V, N43* 57.14', E001* 49.27', +37000.00, UN859waypoint.22=LOMRA, I, N43* 20.39', E001* 52.59', +37000.00, UN859waypoint.23=ROCAN, I, N42* 40.23', E001* 56.48', +35000.00, UN859waypoint.24=PUMAL, I, N42* 22.00', E002* 00.30', +27000.00, waypoint.25=BERGA, I, N42* 10.17', E002* 01.55', +22000.00, waypoint.26=D356Y, I, N41* 56.07', E002* 03.37', +16000.00, waypoint.27=D356J, I, N41* 41.09', E002* 05.24', +10000.00, waypoint.28=SLL, V, N41* 31.11', E002* 06.35', +06000.00, waypoint.29=LEBL, A, N41* 17.49', E002* 04.42', +000000.00, EGGW-LEBL.rc4, 0 , 1 , 0 , 600 , 1800 , 600 , 3700 ,,,, 0 , 0 , 0 , 1 , 0 **,0,DVL, 0 , 0 , 0 , 0 , 0 ,0,0,LGL, 0 , 0 , 0 , 0 , 0 ,0,0,SORAP, 0 , 0 , 0 , 0 , 0 ,0,0,BENAR, 0 , 0 , 0 , 0 , 0 ,0,0,VANAD, 0 , 0 , 0 , 0 , 0 ,0,0,AMB, 0 , 0 , 0 , 0 , 0 ,0,0,BALAN, 0 , 0 , 0 , 0 , 0 ,0,0,BEBIX, 0 , 0 , 0 , 0 , 0 ,0,0,OBUBA, 0 , 0 , 0 , 0 , 0 ,0,0,TUGLI, 0 , 0 , 0 , 0 , 0 ,0,0,TUSAK, 0 , 0 , 0 , 0 , 0 ,0,0,NARAK, 0 , 0 , 0 , 0 , 0 ,0,0,GAI, 0 , 0 , 0 , 0 , 0 ,0,0,LOMRA, 0 , 0 , 0 , 0 , 0 ,0,0,ROCAN, 0 , 0 , 0 , 0 , 0 ,0,0,PUMAL, 0 , 0 , 0 , 0 , 0 ,0,0,BERGA, 0 , 0 , 0 , 0 , 0 ,0,0,D356Y, 0 , 0 , 0 , 0 , 0 ,0,0,D356J, 0 , 0 , 0 , 0 , 0 ,0,0,SLL, 0 , 0 , 0 , 0 , 0 ,0,

Hi,A few times ATC tells me I am off course and tries to redirect me to 180 degrees from the direction I am travelling (and should be). The autopilot is following the correct course and I have checked that not only is the FMC progressing correctly but the FSX default GPS is also on course and displaying the correct next waypoint. RC4 knows where it is as it hands over to succesive ATCs on route, but keeps nagging that I am off course and to turn around back along the route. Today I flew an Easyjet A319 flight from Luton to Barcelona and everything was fine until half way across France when I was rerouted back along the route. The FMC was on route for the next correct waypoint and I opened up the FSX GPS to double check that the aircraft was progessing through the waypoints correctly. I noticed that the waypoint in the RC4 window was showing LUT and the direction and distance to it. Is RC4 sometimes getting out of synch with the FS flight plan and trying to route me back to a waypoint it thinks I have missed? It there a way to resynchronise RC4 to FS so that the next RC4 waypoint matches the next FS waypoint?Regards,Tony