I have flown 2 flights so far and this was btw a upgrade from RC3,flight 1 was from KLAX to KSFO VTU5 RZS J501 BSR BSR2.I was given atc heading as I was approaching RZS as atc said I was not on my assigned route of flight.I had the route programmed into the fmc as I was using Level-D 767.The heading given was 150 degrees from my route of flight.My 2ed flight was yesterday and was flying from KLAX to KDEN LOOP4 DAG J146 HBU POWDR5,I was on a heading of 052 on path to DAG was told to fly heading of 152 degrees as I was off my assigned route.I am on my route and the program keeps jumping on me for doing what I am suppose to be doing.I am setting everything up per the manual and still keep getting these messages,what can I do about this? JeffG

are you progressing the checkpoints? that would account for 180 degree off course problemswhat version of fsuipc are you running. don't say latest version. the current version is 3.521directions on how to get it, are pinned at the top of the forum.jd

Hi Jeff,If this happens always check the top line of the RC menu which tells you the wp RC wants you to fly to.If RC hasn't credited you with passing a wp it will still appear in this line.All the best,John

>Hi Jeff,>>If this happens always check the top line of the RC menu which>tells you the wp RC wants you to fly to.>>If RC hasn't credited you with passing a wp it will still>appear in this line.>>All the best,>>JohnJeff,When the condition that John outlined occurs, you can request "DIRECT Checkpoint" and select the waypoint you want to fly to. RC will ack your request and then you and RC will be back in sync.-michael

I am using the latest version of fsupic.I will refly the klax-kden flight today to see if I missed a waypoint and will let you know. JeffG

what is the version number? i always hear the latest version, and sometimes, not always, but sometimes, it's not currentjd

I've had similar problems and have attributed them to RC not caring what my filed flight path was at the moment. I think this happens on the first checkpoint after departure with the first waypoint well away from the airport. RC handles the departure then vectors me direct to the far off waypoint and states "resume own navigation". I resume my own navigation by making a turn to intercept my GPS/plan flight path which often isn't too far away. RC then complains I am off my (its) flight path. What seems to be expected is a direct flight to the next waypoint then resume own navigation. I guess a turn to my flight route would be OK as long as it was within 5mi of RC's flight path.

>I've had similar problems and have attributed them to RC not>caring what my filed flight path was at the moment. >I think>this happens on the first checkpoint after departure with the>first waypoint well away from the airport.The only time that RC does not monitor (it always cares! ;-)) the manner in which you proceed from checkpoint to checkpoint is when you are flying a published departure procedure with waypoints in departure airspace (~30 nm radius from the departure airport). RC expects that you will proceed direct from present position to the first waypoint outside of depature airspace. RC will consider you off your filed route if, once you are in center airspace, not flying direct to the next waypoint.In this case RC will NOT tell you to resume own navigation because you have been flying the entire depature using your own navigation.>RC handles the>departure then vectors me direct to the far off waypoint and>states "resume own navigation". When not flying departure procedures, RC will assign you an initial heading and vector you "towards" the first waypoint. >I resume my own navigation by>making a turn to intercept my GPS/plan flight path which often>isn't too far away. Ah - that is not what RC expects you to do. When told to "resume own navigation" you are to fly DIRECT TO the next waypoint.>RC then complains I am off my (its) flight>path. >What seems to be expected is a direct flight to the next>waypoint then resume own navigation. When told to resume own navigation you are expected to both:1) fly direct to the next waypoint, and then, 2) continue to fly your route as filed. Note that in real-world operations, if ATC does not expect you to fly a DIRECT TO route, they will say something like "fly heading XXX to join the transition ...", or "fly heading XXX to intercept Jxxx..." "... THEN resume own navigation".Also note that should you ever request deviation left/right of course due to weather, when RC4 says "I need you to proceed back on course" you are expected to fly from present position DIRECT TO the next waypoint. You are not to fly an intercept heading to join your filed flight *path*.-michael

>When told to resume own navigation you are expected to 1) fly>direct to the next waypoint, and then 2) continue to fly your>route as filed; doing so is part of "resuming own navigation".> >>Note that in real-world operations, if ATC does not expect you>to fly a DIRECT TO route, they will say something like "fly>heading XXX to join the transition ...", or "fly heading XXX>to intercept Jxxx..." "... THEN resume own navigation".>>Also note that should you ever request deviation left/right of>course due to weather, when ATC says "I need you to proceed>back on course" you are expected to fly from present position>DIRECT TO the next waypoint. You are not to fly an intercept>heading to join your filed flight *path*.>>-michael >I was getting the same thing, and didn't realize that you had to do a direct to rather than join previous flight path.. Thanks for the tip....

...>When told to resume own navigation you are expected to both:>1) fly direct to the next waypoint, and then, >2) continue to fly your route as filed. >Yeah - that's the conclusion I came to after a while... I just like to get back on the GPS flight path ASAP so I can click the NAV button and doze off!The whole DP/SID <--> RC interaction thing is confusing. The selections on the General tab just add to the confusion. Perhaps you (as a beta tester) could suggest some tooltip wording that would help one make a choice. Or maybe a context min-help button that would describe the options better. I suppose it is documented somewhere in the manual.

after reading pages 109, 110, 111 in the manual, does it still not make sense?jd

>...>>When told to resume own navigation you are expected to both:>>1) fly direct to the next waypoint, and then, >>2) continue to fly your route as filed. >>>>Yeah - that's the conclusion I came to after a while... I>just like to get back on the GPS flight path ASAP so I can>click the NAV button and doze off!Don't forget that at some point - you must actually fly the plane! ;-)>The whole DP/SID <--> RC interaction thing is confusing. The>selections on the General tab just add to the confusion.>Perhaps you (as a beta tester) could suggest some tooltip>wording that would help one make a choice. Or maybe a context>min-help button that would describe the options better. I>suppose it is documented somewhere in the manual.The key things to remember:1. No departure procedure means that RC4 will provide you a heading to fly when cleared for takeoff and then will vector you to your first waypoint. For the other two options you are expected to fly a SID as published.2. RC4 will *automatically* select No Departure Procedure if your first waypoint is at least 30 miles from the departure airport. If your first waypoint is within 30 miles then RC4 expects you to fly a published departure.The implications of #2 is this: RC4 does not actually know that you are flying a DP - it *assumes* you are flying a SID if you have a waypoint that is within 30nm of the departure airport.For case 2 - you will NOT receive a heading on takeoff and you will NOT receive vectors to your first waypoint.3. The above is the default RC4 processing. However, at any time up to takeoff, you can manually override the RC4 selections. For example, I am familiar with the real world standard vectoring for departures from KORD 22L. Sometimes, even though my first waypoint is 65 nm away (meaning that RC4 will give me an initial heading and then vectors to my first waypoint), I will click Departure Procedures so that RC4 will NOT give me vectors. I then fly my departure as it is done in the real world. It is a neat little work-around when you want to fly a prescribed route that is not necessarily a published departure.Hope this helps - if not, ask away! ;-)-michael

The manual helped some but IMO the manual has a lot of inside baseball banter going on. There is an assumption that the audience is experienced RC users. How things were done in the last release is not important to a new user.I read the manual pages but I am still baffled by the prompts on the screen - maybe its just me.The GUI prompts may mean more to the programmers than to the user. Also no need to document in the user manual how RC determines which option to pre-select.How about something like this:

---Departure----------------------------------------|.O  Published SID |...O SID altitudes|...O RC altitudes||.O  RC vectors and altitudes|-----------------------------------------------------or---Departure----------------------------------------|.O  Published SID (or wing it!)|...._|...|_| RC altitudes||.O  RC vectors and altitudes

The manual could document what to expect:e.g.If you use 'Published SID' Tower {or whatever is correct} will direct you to "fly the procedure as filed...." At 30 miles out Departure will pick you up{hand you off?}. In the mean time you are trusted to fly the procedure. RC will not enforce the SID unless you document the SID waypoints on your fight plan. If you'd rather not be bothered with the SID waypoints just fly direct to your first waypoint. If you check 'RC altitudes' Departure will assign altitudes but still not tell you where to fly.If you use 'RC Vector and Alts' Tower will hand you off to Departure and they will vector you and assign altitudes to reach your first waypoint. If you use this option your first waypoint should be xxx miles from the airport. {perhaps this is not a true restriction but a practical suggestion since you don't want waypoints that are hard to reach because they are too close in for safe maneuvering}RC considers waypoints within 30 miles to be SID waypoints and those past 30 to be enroute waypoints. RC expects you to pass within 2 miles of any SID waypoints and within 5 miles of your enroute waypoints and on the flight path between them.