Sign in to follow this  
Guest The masterBaker

Opposite Direction

Recommended Posts

Why is RC4 telling me to go in exactly the opposite direction from a flight plan compiled by FSBuild?For example I leave Edinburgh to go south to Bristol (using the TLA 6D SID) on a heading of 184 and RC4 keeps telling me to fly 005. I'm flying VNav and all the instruments are showing the correct course and the a/c is following the magenta line.Any ideas please?Regards,Paul

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

Paul,You missed a filed checkpoint. You must get credit for each checkpoint. 2m for DPs, 5m enroute. RC's telling you to "go back and get credit".You can always request your next checkpoint to get around this but that's sort of a poor work-around if you're just starting out.

Share this post


Link to post
Share on other sites

>Paul,>You missed a filed checkpoint. You must get credit for each>checkpoint. 2m for DPs, 5m enroute. RC's telling you to "go>back and get credit".>>You can always request your next checkpoint to get around this>but that's sort of a poor work-around if you're just starting>out.but wouldnt you do that in real life? Surely you wouldnt do a u-turn just to fly over a checkpoint?

Share this post


Link to post
Share on other sites

I think this brings up a good point. Never having been a real IFR pilot, would this ever really happen that a controller would order you back to a waypoint??? "Getting credit" for hitting a waypoint is a very "gameish" aspect that I wouldn't expect from any serious FS add-on. The RC warning about drifting off course would seem more appropriate in this circumstance. Don't get me wrong, RC has completely replaced the default ATC for me. This is just one little aspect that, for me, needs to be fixed. Mike

Share this post


Link to post
Share on other sites

I am a real IFR pilot and Instrument Instructor. While I've neverbeen told to make a u-turn just to cross a checkpoint, I've certainlygotten an earful when I didn't follow the course I was supposed tobe on. One time early in my career, I was assigned a SID coming out of White Plains. Got overloaded in some pretty dense airspace and missed a turn toward a fix. And the friendly Tracon controller let me know about it too.I agree, going back to pick up a missed fix is not very realistic. However, missing fixes is not something you can do routinely in the real world IFR system without ramifications.Walt

Share this post


Link to post
Share on other sites

Tkx Walt, and this is the dilemma... by allowing users to miss checkpoints, what's the point of checkpoints? Theoretically, one could file 30 checkpoints but when airborne, fly direct...? You filed it; fly it. There's a purpose.At work, yes I see this but absolutely not often. RW pilots (especially those in the FLs) are pretty sharp. I personally give 'em no more than 4m grace, every C's different I suppose. When one does miss a checkpoint and after asking if they're having nav trouble, I make point to let them know it hasn't gone un-noticed. Depending on the pilot, things progress from there ;-).One difference between ZME and RC is, RC doesn't slam you as quickly as I would at work. What is it, 20m past a checkpoint b4 RC yells...? That one reason RC try to turn you around (no, I'd not do that).I'll make note; can't say what we'll do with it at this point. I'll have to ponder this one. Maybe some embarassing critique }( :) ?

Share this post


Link to post
Share on other sites

Thanks for this reply, Doug. It confirms what I thought should be a better response from RC: ream the pilot out for missing the waypoint. If that's what happens when controllers such as yourself see this happen, then that should be what RC tries to simulate. I have one plane I use that has a bug when swtiching from manual to autopilot that sometimes causes some large vertical speed excursions. I get yelled at by RC. Annoying since I'm dealing with a buggy add-on, but understandable from RC's point of view and I wouldn't want it changed. Mike

Share this post


Link to post
Share on other sites

until we change it in the future, don't miss a checkpoint, and there won't be a problem :-)that was a joke!jd

Share this post


Link to post
Share on other sites

Thanks very much for the replies.I'll have to re read the manual as I don't even know what "credits" are!!:-( Anyway, apart from RC not warning of other aircraft when taxying, it is a first rate addon and thank you to the developers!!Regards,Paul

Share this post


Link to post
Share on other sites

>>I'll have to re read the manual as I don't even know what>"credits" are!!:-( >You gain credits for flying over each waypoint filed in your flightplan within a certain distance.These credits are then stored on the RC4 server. When you have accumulated 250 credits you get access to the secret RC5 server where you download a secret copy of version 5. Shhhhhhhhh!!Well, thats what my manual doesnt say :)Graham

Share this post


Link to post
Share on other sites

>until we change it in the future, don't miss a checkpoint,>and there won't be a problem :-)>>that was a joke!>>jd"Doc, it hurts when I do this...""Well, then don't do that!":) :) :)

Share this post


Link to post
Share on other sites

Ok. This has happend to me a couple times too. Now I use the PMDG with a FMC. I dont miss waypoints usually. lol BUT.... say I file a flightplan and load it into the fmc. By the time I'm doing this RC is already running with a flightplan loaded. NOW....Ground gives me a differnt rwy than the 1 in my plan. For 1 reason or another I decide to take it. Now from here I make the changes in the FMC. But RC still has the original plan. Can this be the reason? And if so, what am I doing wrong? Do I need to change the Plan loaded into RC?

Share this post


Link to post
Share on other sites

The reason you have differing departure runway is because you have filed a plan to depart from eg 9L when in FS2004 the wind is a tail on that runway, hence you being instructed to use 27R.Are you using ASV for your weather? Best to check the weather first for your departure airport and select your runway based on that.Or you could use FSBuild which will do it for you, as long as you have external weather program refreshed with current weatherRegardsGraham

Share this post


Link to post
Share on other sites

HiJust to know: Does FSBuild allow you, while making a flightplan, choose the runway according the wind?Because this is really what it matters in the initial phase of the flight, the correct runway. I know that AI planes have odd ways, but adding a more realistic way makes one feels like a real pilot, doesn't it?I'm a new user of RC(4) & just recently bought AS6.ThanksEduardo

Share this post


Link to post
Share on other sites

I do use FSBuild. And I have The Winds Aloft checked in FS Build. When I look at the Navlog FSB creates all the wind info is there. But yet almost half the time the runways differ. But anyway, I realize I need more time and instruction on proper flight planning. Something I was never too concerned with before RCv4. I guess what my question here is: If for ANY reason you need to make changes to your flightplan AFTER RC is loaded, Do I need to change the plan in RC? And is that even possible after RC is loaded and running? Rich

Share this post


Link to post
Share on other sites

if your .pln is changed, you need to quit rc, and restart, and load the new .plnjd

Share this post


Link to post
Share on other sites

Been using RC4 for a few weeks and noticed missing waypoints even when copilot was flying the flightplan (exported from FSNav). Then I noticed that if there is radio communication going on, the aircraft position does not update on the display window, the "ping" doesn't sound when flying over the waypoint, and by the time the radio chatter finishes, plane has already gone over the waypoint and co-pilot already turning the plane back. Typical situation is flying in busy airspace (e.g. southern Germany) with heavy AI (80%, from Traffic2005) so there is a lot of radio chatter as well as ATC communications. Flying from EGCC to LMML last night (copilot flying), missed waypoint several times, every miss was related to radio communication when passing waypoints. Anyone noticed this? Any workround (apart from requesting a direct to chkpt), or is this my setup (RC4.2, Traffic2005, ActiveSky6, FS Realtime)?

Share this post


Link to post
Share on other sites

Try this to reduce sound congestion.Use only AI chatter, not the additional phony pilot wavs (Options).Make sure audio in AS6 flightwatch is off.Try turning off the waypoint acknowledge "ding" in RC options.Are you using motherboard audio or a seperate sound card.

Share this post


Link to post
Share on other sites

also fly at 1x as you approach checkpointsjd

Share this post


Link to post
Share on other sites

Doug,May I make a suggestion. I have had this happen to me a few times and when I checked the problem I realised it was happening when the first checkpoint was the the depature airports navaid, and my flight path after take off was to turn and make a standard 30 degree intercept of the depature track without overflying the aid. Could not a parameter be put into the program that ignores the first FPL checkpoint if it id the departure navaid? And/or, alternatively on radar contact be instructed to '.... track direct to (waypoint) resume own navigation.'?My RW ATC experience would never have a pilot overfly the departure navaid unless the turn after take off naturally resulted in this. Normally in a non radar environment the procedure is to intercept the departure track within 5 nm. In the radar environment, as instructed by ATC.NeilYPAD

Share this post


Link to post
Share on other sites

The extended RC menu (9) has an option to select the next waypoint in effect skipping a problem one.The problem of the first waypoint occurs in some instances when initial tight waypoints are included in external plans such as inclusions of SIDs being converted to individual waypoints in the exported flight plan. This is often for the benefit of importing into an FMC as opposed to using the FMC's internal database. However, the same waypoints are exported to FS9 so RC gets them as well.I'm an FSBuild and PMDG user. In FSB if a SID is included it is converted to waypoints in the route grid. These waypoints can be deleted there before export. You pick the first waypoint you want RC to recognize and delete any before those in the grid.On the FMC you can choose to enter the FMC's SID from its database and clean up the LEGS page so no waypoints are duplicated. This gets you LNAV or at least navigation display of close in departure waypoints that you can steer toward using HDG or yoke control before you get to the mandatory RC waypoints. It is a bit of work on the FMC but does solve the problem of necessary accreditation of close-in initial waypoints (sometimes referred to as soft waypoints because they exist for departure turns and allow more deviation).

Share this post


Link to post
Share on other sites

>also fly at 1x as you approach checkpoints>>jdThanks Ron and jd, but these are not permanent solutions. In all instances I observed, it is not the plane which misses the checkpoint, but RC failing to recognise the plane passing the checkpoint because of concurrent radio communication. I missed one again during the last flight because shortly before the checkpoint ATC instruction came to ask for frequency change. As per Ron's suggestion I turned off everything (and I am using on-board soundcard), including all AI chatter so the only radio communication is ATC. Any plans to work round this in a future update?Not meant to be a criticism - just feedback for you guys to make it even better. In all other aspects I enjoyed this fantastic addon tremendously, and have not flown any flights without it ever since I bought it several weeks ago.

Share this post


Link to post
Share on other sites

Hi,one thing, normally we have to choose and start to follow a STAR between 40 to 60nm. but RC didn't provide us the info on the "expected runway approach" as compare with default FS9 ATC, at least 80nm we know which runway is to be used. RC only informed us at 30nm, which i feel not correct. hope can improved on this.RegardsShaheedan

Share this post


Link to post
Share on other sites

I too think it would be good to receive runway inforamation earlier than we do now.In UK at least inbound IFR traffic gets told pretty early on,like 150 miles!However,I plan mine from the weather in AS6 and tell ATC the one I want.It always seem to be accepted.

Share this post


Link to post
Share on other sites

why not remove the bad checkpoint in the .pln?jd

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this