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

I'm looking at the Clacton-Dover departure chart (SID) for EGGW. LUT is an NDB just a few miles miles NE of the departure end of the NE runway and then an almost ninety degree turn to VOR BPK. Both are within the 30 nm airport radius. This automatically means RC expects you to navigate your own SID crossing the waypoints indicated. Chances are your FMC is using a predictive 90 degree turn at LUT which takes the aircraft outside of the 2 nm radius RC allows during departure so you did not get credit for it.Did the flightplan waypoints given to RC and your FMC departure waypoints agree (if you were using the FMC terminal database)? If not that could be the problem.On a tight turn during the restrictive waypoint allowed radius if you miss it just go to the extended menu option, request a direct-to, and select the next waypoint in your flight plan. The other option is to use the MCP HDG control or hand steer the aircraft so you get close enough to LUT in this case. There is also a soft waypoint (not charted) turn about 15 nm past BPK turning to DET that your FMC might follow. RC expects a direct route so you might get an off flightpath warning from RC.Without you posting your route I'm just guessing here. Remember, RC ATC rules, not the FMC. I guess your departure waypoints are LUT BPK DET and then to your transition on the airway.I'm not familiar with your A319 model or FMC. If you do have a waypoint synchronization problem you might have the option of using a flight planner that exports to both FS and your A319 FMC and then do not use the A319 terminal database. The planner would on export expand the SID into individual waypoints so RC and your FMC would be in sync.UK charts are available without registration here:http://www.nats-uk.ead-it.com/public/index.php%3Foption=com_content&task=blogcategory&id=6&Itemid=13.htmlThis thread http://forum.avsim.net/topic/293156-difference-between-visual-and-vector-approach/ shows you how to log in to Eurocontrol to get charts, including Spain, to help you navigate. Registration is required but it is free access.

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,

I find i get the problem u mention,,,rarely say once in every 10 flights,,,,i always presumed it was because radar contact had missed u flying over a waypoint,,,so to work around it all i do is is press either 0 or 9,,not to sure cos im not infront of fsx,,,but u are then aloud to fly direct to a way point,,,i choose the next waypointAndrew

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 want to comment on a couple of waypoints in this plan. These are highlighted by >>>>>>>>>>>>>EGGW-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, The are known as the "soft" waypoints not assigned an intersection or navaid label in charts. They are turns in a path denoted by usually a distance measurement of some kind as in the sample SID I referred to in a previous post. (They exist in digital database sources that planner developers subscribe to as AIRAC information.) The problem is that the labels are only unique for that airport and may be duplicated outside of the airport facility. In FSBuild when using auto-route followed by a build it may have chosen the wrong one resulting in an irregular path.I am pasting below a document I created regarding FSBuild hints that can help:---------------------------FSB tips:1. Include this line in FSbuild.cfg:NAVCHKDUPDIST=100This decreases the chance of using the wrong duplicate named local (to the airport) waypiont from a nearby airport. Local waypoint names are not exclusive. It decreases the database search when it is named in the route to within a 100 nm radius of your airport. You will find these in terminal procedures such as "D" number something within a SID or STAR to define a merge or turning point.2. When doing a Auto Generate (Route) be sure the SR (Stored Route) button next to it is "up" that is not highlighted. Auto Generate will use a stored route if found by default and most are out of date with old waypoints and terminal procedures. Having Stored Routes off forces it to search a path with fresh data.3. Take advantage of the frequent AIRAC updates at the FSBuild site for the greatest possibility of matching current charts and real world flight plan procedures and waypoints.4. Where an airport uses specific runways for different terminal procedures select the runway using an estimate based on weather and if the runway fits your aircraft requirements before doing the Auto Generate. This helps select the correct SID and STAR for the runway and direction of departure and arrival.5. After the Auto Generate and/or first build look at the map created to spot any obvious errors. In the route grid look for any sudden non-sensible changes in direction or extremely long legs not in the correct direction creating a zig-zag in the map. (See item 6 following to correct).6. Be aware there is an option you can set for each session titled "Build Route from Grid Table". It does not stick between sessions. This lets you build from an edited route grid that you may have modified without recreating the table with the same error on your next build/export. For example you might wish to drop an errant waypoint when proofing the map and rebuilding.7. Sometimes the name of a procedure (SID/STAR) does not match the name exactly in a published route and the procedure will not expand into its plan waypoints in the grid table. You can click on the arrow in the SID/STAR box to see what close name is in the FSB database. (Another reason to keep up with AIRACS.) For example KMSP has a current real such as this one:http://flightaware.com/resources/airport/KMSP/DP/WAUKON+TWObut the FSB database only has UKN2. (It does have UKN3 now with the latest available AIRAC update). If so in the route line just change UKN3 to UKN2 so it will expand. Here's a real route from flightaware.com for KMSP to KMDW:KMSP UKN3 DBQ CVA MOTIF3 KMDWthat can be pasted into the FSB route line. If UKN3 or MOTIF3 does not expand in the route grid to individual way points look in the upper part of FSB in the airport section dropping down the SID or STAR box to get the available version and substitute that label in the route line and rebuild.8. Sometimes it takes a second build to get the map to move and/or magnify. The mouse scroll wheel lets you magnify. Just click on the portion of the map you want to center on and scroll to magnify.9. If you click on a line in the route grid table to highlight it, the waypoint on the map will turn red. This is useful for finding errant waypoints that cause an error in the path. That line can then be edited or deleted and a rebuild accomplished with the build option to build from the route grid table.10. If you are running a weather program such as active sky, first build the route in FSB exporting to FS9 using an anticipated cruise altitude and specify the nearest aircraft profile. In AS get the weather you wish to use. (I always get the weather for the zulu time of the departure in FS since time of day affects weather characteristics). Import the plan into AS via the new route button, check the altitude and choose an appropriate true airspeed in knots (this is your no wind ground speed). Process the route. When it is finished click the button to print a hard copy of all. Use this AS navlog for METAR data at both ends and winds aloft and temperature aloft that can be used for FMC data. (You'll also get your estimated average wind at your specified altitude - handy for FMC data.) Leave AS running. Now go back to FSB and your chosen aircraft profile. Enter the surface temperature from your departure METAR, then estimated total taxi time, hold time, and extra time (sometimes called discretionary fuel). Now turn on again your FS9 export along with any FMC export you might use. Rebuild and you'll see the messages regarding the export completion. On the route selection on the left which brings up your route window select the navlog tab and click the .pdf to save the navlog in a file or the print button to get a hard copy so you can easily reference the estimated fuel and other data. This estimated fuel has now taken into account your winds aloft data - no need to enter it in FSB. Now that you have the hard copy and exported your route, you can first optionally save the plan by selecting flightplan window, then clicking the category tab, then select user category. Now click file, save from the menu bar. The name you might want to embellish. Click Save Route To User Flight Plans. For another session, you can recall this working plan and just build.11. If you are using an aircraft with nav equipment that has its own terminal data procedures in its nav equipment (think FMC) you might wish to use step 6 above to take out the waypoints of the terminal procedures keeping just the transition points and build and export with just them. This easily in most cases lets you select the SID and STAR assigned by ATC on your nav equipment by providing a clean legs list in your nav equipment. If you need ATC to monitor the waypoints of the terminal procedure than just export all. To keep ATC and you nav equipment in sync, you might consider importing the full plan into your nav equipment and not using your nav equipment procedure database.This is kind of long but through experience I've described some tricks I've used watching out for any pitfalls.There is a later update for 2.3 not linked from simmarket. From the fsbuild forum that link is:http://www.fsbuild.com/dl/Fsbuild2376_2Upd.exeInstall that if you have a lower version number after your 2.3 update from Simmarket.---------------------------------------

Regarding the problems in trying to select a menu item when comms are busy be sure to just use AI chatter and not prerecorded chatter. Prerecorded chatter just slows down RC response. Interact with AI should also be selected. This can also cause late audio regarding AI reporting.The direct-to option is in the expanded menu brought up by (9).RC can be stalled by lack of an ack or in some cases not reaching an assigned altitude soon enough. When given a change in altitude even a relatively small/slow climb or descent rate can satisfy RC that you are responding but RC does not indicate whether or not you'll reach the goal in time. When your climb or descent falls below a certain rate it will then check your altitude for compliance. Be sure you read the manual regarding the differences between altitude expressed in feet and flight levels. Do not use the "B" key in FS to set altimeter reference pressure as it is hard coded to 18,000 feet for a transition level as used by the FAA and that is not an international standard.It is also recommended not to use the Display Text option in RC as that slows RC performance.

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

When given a change in altitude even a relatively small/slow climb or descent rate can satisfy RC that you are responding but RC does not indicate whether or not you'll reach the goal in time. When your climb or descent falls below a certain rate it will then check your altitude for compliance.

For info RC4 is happy with a climb rate of 50fpm or greater from my flights with Concorde during the cruise-climb phase. I can't imagine the descent rate is much different.

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,

A general relief for this within the first 30 nm is on the Controller page to choose Alt Restrictions or No Alt Restrictions probably already chosen for you if the first waypoint is within 30 nm. In the plan sent to RC remove the waypoints within 30 nm and choose one of these two DP options and your headings and credits will not be monitored. You will be expected to cross the 30 nm or later waypoint. Your FMC or other nav device can then fly your aircraft anywhere it wants within the 30 nm radius and there are no waypoint restrictions/credits to consider.You'll have to insure your nav device has the same plan waypoints for the rest of the SID.Since the rest of the waypoints will be outside of the 30 nm departure range you'll have the 5 nm limit around the rest of the route waypoints until arrival.Airliners generally limit their bank rate to 15 degrees for passenger comfort (G forces increase with bank angle). If you are required to use less of a predictive curve to meet a waypoint restriction you can reduce speed or allow the bank limit to increase (less chance of a stall at the higher speed).At EGGW and other London airports a lot of weaving around the other airport traffic patterns and restricted areas might be required and you'll find perhaps restricted airspeeds which might help with the turn radius.FWIW our RC beta tester team of ATC controllers (active and retired) advise us to stick with the two mile radius restriction on departure waypoints. I think two or three are in the UK and I can tell you one is active at EGLC. He contributed EGLC movement videos to You Tube.

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.

Tony,The attached Compton SID from EGGW shows that the route to HEN involves no sharp turns when approaching that waypoint so I'm perplexed as to why you're not crossing it. How far before HEN is your CDU/FMC switching to the next waypoint? To me that is key to your problem.Your heading as you approach HEN should be 258. In your plan what is your heading as you approach it? RC4 is certainly capable of crediting waypoints as shown in the official SID.

I do not see an extreme turn until CPT which is more than 30 nm out at about 37 nm out and has a 5 nm hit radius. That one could be iffy but a direct-to should be available.FS Build grid extract and plot attached.

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,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.

Hi Tony,Now that we know HEN is not the issue we can concentrate on why you are not being credited for passing CPT. There is another waypoint - RODNI - in your plan. Are you receiving credit for passing that. There's an option in RC4 to ping when you pass a waypoint. It might be worth enabling that and keeping an eye on the active waypoint in the RC4 display. I have encountered problems when you have a waypoint too soon after a big turn that cannot be flown over but RODNI should be far enough away for it not to be a problem. If you continue to experience this problem make a log and post it to JD. Instructions pinned to top of forum.

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.

Your PC - in DX9 mode - is more than capable of running FSX, RC4 and ActiveSky. RC4 is very light on resources. Try flying this route with clear skies to keep your frame rates as high as possible for a test flight. I would also suggest you enable auto-comms so any instructions are ack'd straight away rather than relying on your response. If you delay too long it can occasionally mean you don't get credited passing a waypoint. Once your more experienced with RC4 switch back to manual comms. The workload straight after take-off is high so if you're not useed to RC4 some help is useful.

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!

If real-world aircraft are capable of flying a SID then it should be possible in FS. I'd be inclined to keep the SID waypoints in your plan and monitor your speed during large turns to ensure you don't overshoot a waypoint. Satisfying the RC4 rules for overflying CPT should not be a problem providing RODNI was credited.