About 25 miles out and after receiving ILS approach clearance and vectors to final to RWY 4L at KCSS (AFB) in my C17 from KCHS, Approach directs a heading of 310. Aircraft turned to heading 310. Panel directional gyro/heading indicator shows 310, GPS shows 310. Magnetic compass verifies 310. FSX Map verifies heading is 310. Continue to receive: "I say again, fly heading 310." Attempts to turn left or right to adjust for possible error does not help. After about 10 pronouncements, Approach provides the final ILS capture heading for the runway. How to fix this problem, other than just ignore instruction and receive a bad admonishment. At 73 years of age, I posses a commerical, multi-engine, instrument ticket and lots of hours, but an expired medical certification <smile>. I write code so just need to know how to fix this. John

There are actually scenery issues that can cause this problem at specific airports. Some sceneries modify the magdec.bgl (?) which can goof up instrument and course data returns.

 

I did not have KCSS in my external flight planner data base nor did I find any information on the web. Where is it located and how long was your flight path from Charleston. It is not in my FS9 RC airport database.

 

What is the heading stated in the status area of the RC in flight window? Actually for vectors that may not help. Also, by this time, you should be not using any FS flight time acceleration. With RC generally 1x for departure and approach and maybe 2x enroute if your PC is up to the performance.

 

In the mean time here are some items you can use:

 

1. Check out the use of the NOTAMS feature in the manual that can be declared for your departure and destination airports. This places RC in an advisory capacity which should stop the badgering of the controller.

 

2. If an approach is difficult and you wish to not take vectors you can navigate on your own by in flight request for an IAP. To get this after your destination runway is issued and you ack your first vector you will find it by going to the extended menus (9) to request an IAP and then select your runway.

 

3. Not recommended but you can in RC general options increase your heading tolerance. That may solve some magdec problems.

 

4. Unless a waypoint is fast approaching wait on an ack until the aircraft has responded to the commanded change to avoid controller impatience.

 

Try a default aircraft and scenery to see if it is a scenery issue.

 

For this specific flight as soon as you start RC start the debug option to create a log See the pinned log topic. It can pinpoint what RC is seeing from FS. If it is a long flight before you get to 150 nm out alt-tab to RC and then start the debug procedure. These files can be huge.

 

You are a new user I believe. After a successful RC install you need to update fsuipc and makerwys.

http://forum.simflight.com/topic/66139-updated-modules/

http://forum.simflight.com/topic/66136-useful-additional-programs/

 

With the updated makerwys installed run the RC scenery database rebuild once more. This takes care of some scenery priority issues.

 

Just to get used to RC have you tried some of the tutorial flights in the manual?

Ronzie: Not a new user of RC4, been a JD supporter since 2007, but recently updated desktop to Win7(64) Ultimate SP1 from Win Vista(64) Ultimate.

 

KSSC is an Air Force Base in Sumter, SC, as is KCHS (joint use) in Charleston, SC. I was a military Jockey <smile> and had to rebuild both KCHS and KSSC to correct FSX errors. Additionally both bases of mine have AI aircraft for each of the actuals ones stationed there (with flight plans assigned). The C-17 I simfly is a copy of an actual one stationed at KCHS.

 

I know about the 30 mile VOR rule flying GPS to Europe.

 

IFR Flight Plan = KCHS ->CH (335*) 5.9m ->VAN (337*) 34.7m ->PINIE (350*) 22.9m ->KSSC (042*) 8.8m on ILS RWy 4L and flown at 6K in C17 for 37 min using GPS and VOR.

 

Problem starts destination side of VAN and prior to PINIE, ATC directs switch to Shaw AFB Approach who directs Heading change to 310* and descent to 4K with vectors to ILS and nag starts until 23m out and vector to intercept ILS.

 

Except for KCLT to EDDF in an A330-300 across The Pond, I always fly without accelleration (what is the fun with accelleration anyway?)

 

fsuipc and makerwys are always up to date <smile> and I have been used to RC for 5 years now <grin> This started after my upgrade, so I will check out your default aircraft and stock airport, NOTAM and debug suggestion. Thanks John

sorry you are having problems. send me a log, i'll tell you what the problem is. instructions pinned to the top of the forum. make sure you click debug before loading the plan

 

jd

Hey there JD, I thought you were taking time with your loved one.<smile> Here is what I have tried on my desktop and it seems to work, because I think the problem is the switchover to Shaw AFB Approach and the fact that RC4, after the switch, shows no further mention of Vance VOR (VAN) and none of the next waypoint (IAF) PINIE which is the start of the ILS approach and the point of the nag start is more than 30 miles out from KSSC. On my Desktop, I inserted a standard SID from Charleston AFB (KCHS) to Waypoint MLTRE-->VAN and after the switch to Shaw Approach and first instructions to Heading 310, I placed a Waypoint (H310) and added that waypoint to my FSX flight plan and just to be safe, at the instruction to heading 010 (which is to intercept the ILS) I placed another Waypoint (H010) and added that to my flight plan, listing Waypoint PINIE as the final Waypoint on the ILS 4L Approach Chart. Having the Waypoint H010 in the flight plan appears to satify RC4, but I don't see how as it is not displayed in the RC4 window. It seems to work on the Desktop and I need to try it on the Laptop. If not, I will send you a log from the Laptop, where this all started. Thanks for the reply and get back to what you were doing. You never know about an "Alienware" laptop. <grin> John

JD: Did not work on laptop. Sent you a log, which shows C-17 is on Heading 310. It has to do with the Shaw Approach controller and that the IAF PINIE for ILS 4L no longer appears in the RC4 window and I believe KSSC and RWY 4L are too far out at the turn given by the controller. At the controller's heading 010 command, supposedly at "23 miles from the marker" and "cleared to ...", that heading will miss the IAF and the localizer and the glide slope, as, from that point, a heading of 044 is required for intercept. If the turn command came at my placement of Waypoint (H010), the heading for the localizer would be 042, which is what shows in the RC4 window for ILS RWY 4L and heading 010 would intercept IAF PINIE. It must be either in the flight plan, or the distance from the marker, or whatever solution you come up with. <smile> John

JD: Thanks for the mail. The answer was simple: "Don't let my 50 year old son fly on my laptop and change the default deviation allowances!" It had to do with the heading deviation allowance set to 90 degrees, instead of the default 15 degrees. It got the approach controller all upset, just like the tower when my son forgot to put down the gear. <grin> Thanks again for all you do. John

JD: Thanks for the mail. The answer was simple: "Don't let my 50 year old son fly on my laptop and change the default deviation allowances!" It had to do with the heading deviation allowance set to 90 degrees, instead of the default 15 degrees. It got the approach controller all upset, just like the tower when my son forgot to put down the gear. <grin> Thanks again for all you do. John

 

mbscjohnp, did you want it at 90 degrees or at the defatult (15 degrees)? Did your 50 year old son changed it from the default to 90, or from your custom setting of 90 degrees to default 15 degrees?

 

Thanks,

Dirk.

Dirk: The entire problem was the change made from the default 15* to the custom setting of 90* and, during my problem solving, I didn't figure on the fact that the default had been changed. John

I've used 25 degrees with no problem. It is extreme numbers approaching 90 that can cause it, probably 45 or more. I only used 25 for very long legs in FS9 due to the way spherical navigation (great circle) is not used in FS9 rendering but is in FSX and had no problems.