Since starting to use RC I have noticed some variations in quoted course headings.For example:Using FSNav to make a flight plan I might have the ILS approach to rwy 14 at Leeds EGNM given as 110.9 / 142 degrees.RC quotes for the same runway 11090 / 140.I also noted when returning from Moscow UUDD to Stansted EGSS that runway 27 was given by FSNav as xxxxx / 331 degrees - which is obviously VERY wrong!I also sometimes use a unility/guage which I have incorporated into various panels "RunwayInfo" and have now noticed there are variations shown with that also!!!I have not, so far, done a comparison with the Map feature in FS as to what that might give for the above examples.The question is..........Which course heading should be used where there is a variation?Why is there a variation?Does it really matter?

have you done a "rebuild rc scenery database" on your machine?142=140 - i round. you won't ever see 142. you'll see 140 or 145 in the menu displayi don't even show a runway 27 at egss in my database. is this an add on scenery file (even more reason to rebuild the rc scenery database)also make sure that all the headings you're looking at are all magnetic or all true. or figure in the magnetic variation into them so that you are comparing true with true, or magnetic with magneticjd

FWIW:In the scenery code I believe the ILS course is written as true, not sure. I do know that there are some scenery add-ons that (in error) modify the magnetic deviation data in FS. I know that in the BASE scenery folder that magdec.bgl contains the default magnetic deviations and according to posts some scenery installs mess with it. Check the properties of this file just to insure it matches the other default .bgls in that file. This would not affect your runways list, however.For EGSS both as an add-on I have and default I only show runways 5 and 23. The true course for the 23 ILS is 222.840.I would guess that there is a messed up scenery somewhere.From the AVSIM libraries download the free utility AFCAD v2.21 (if you are using FS9). If using FSX I believe there is a similar freeware utility that has just arrived. If you do have FS9 run AFCAD and do an open airport. In the search box put EGSS.A list of layers should open. The bottom layer is stock. The upper layer is dominant if present. Double-click to open the highest layer. Do lists/runways and check those runway properties if you wish. Then do lists/navaids and check the properties of the ILS in question. If either are incorrect, then you have a defective scenery. If you do File/properties it will get you the path and name of the scenery file being examined.

>have you done a "rebuild rc scenery database" on your>machine?>>142=140 - i round. you won't ever see 142. you'll see 140 or>145 in the menu display>>i don't even show a runway 27 at egss in my database. is this>an add on scenery file (even more reason to rebuild the rc>scenery database)>>also make sure that all the headings you're looking at are all>magnetic or all true. or figure in the magnetic variation into>them so that you are comparing true with true, or magnetic>with magnetic>>jdHi jd,yes - did a rebuild on initial installation of RC and again after installing my latest add-on (VTBS_).Re Stansted - sorry, my mistake - it was/is rwy 23 not 27 as previously stated. However the course is given in my FSNav flight plan as 331 - a very obvious mistake; possibly 231.The main reason for asking the question was relevant to ILS landings where I would set both Nav radios to xxxx and dial the course heading as indicated. If, as you say, you "round" in "fives" if I dial-in your course heading which could then vary by 2 to 3 degrees then that may explain why it has been necessary for me to take manual control of landings which seems to be the case more than I had to do previously. Then again, since installing RC I have done more "flying" than I did previously!It was a genuine query borne out of a very healthy interest in the excellent RC and the said variations.I note the reply from Ronzie who has alluded to magnetic -vs- true.Thanks for the prompt response.I have become quite evangelical about RC not least of all the support offered and the speed with which the support is dealt with.Suffice to say, I have now recanted my sins of the "dark side" :-sae(on-line flying) and have become a total convert to RC and all that it offers.:-bigangel

>FWIW:>>In the scenery code I believe the ILS course is written as>true, not sure. I do know that there are some scenery add-ons>that >(in error) modify the magnetic deviation data in FS. I know>that in the BASE scenery folder that magdec.bgl contains the>default magnetic deviations and according to posts some>scenery installs mess with it. Check the properties of this>file just to insure it matches the other default .bgls in that>file. This would not affect your runways list, however.>>For EGSS both as an add-on I have and default I only show>runways 5 and 23. The true course for the 23 ILS is 222.840.>>I would guess that there is a messed up scenery somewhere.>>From the AVSIM libraries download the free utility AFCAD v2.21>(if you are using FS9). If using FSX I believe there is a>similar freeware utility that has just arrived. If you do have>FS9 run AFCAD and do an open airport. In the search box put>EGSS.>>A list of layers should open. The bottom layer is stock. The>upper layer is dominant if present. Double-click to open the>highest layer. Do lists/runways and check those runway>properties if you wish. Then do lists/navaids and check the>properties of the ILS in question. If either are incorrect,>then you have a defective scenery. If you do File/properties>it will get you the path and name of the scenery file being>examined.>Wow!Sorry - my mistake re EGSS. It is 23 (not 27) but still shown as course 331 in my FSNav flight plan!In addition to the FS9 default scenery I use all of Gary Summons' sceneries for the UK airports to the extent of updating earlier versions to the newest Xtreme series. I shall take a look at the AFCAD utility as you describe and see what happens.Thanks for your interest.

FYI:On a properly modeled nav radio the dialed in course should not affect the accuracy of centering on a localizer beam. I was -ahem- corrected on the PMDG forum. If you are on a LOC/APP frequency, which differ from the range of VOR frequecies, the indicator only pays attention to the two modulated signals (90 and 150 Hz) which are directed left and right of centerline. A strength comparison between the two drives the indicator.Once on the LOC try moving your course selector and it should have no affect.This is why if heading outbound on an LOC for a procedure turn or using a back course approach changing the course selector by 180 degrees will not get rid of the reverse sensing. Only an A/P equipped with a REVerse mode coupling can fly a raw data (localizer) coupled back course approach.The glideslope (if present) similarly operates.If you are doing a VOR approach then the course selector must be set correctly.It still is a good idea to enter the course into the selector even on an ILS approach as a reminder of the inbound heading.