First off, I am using the AIRAC that came with FSB 2.4 and there is an error in the AIRAC file departure from runway 12 after LUKEP in both PPN2G and PPN1H if not more. The AIRAC txt in LLBA for runways 10 and 12 look like they after LUKEP use a fly over BLV and then head east again which is not correct. I am waiting for Aerosoft support to find out why a one time update I purchased this month does not work in that I can not login into the server. Regardless, the first leg is the same in your posted images.

 

In your first set you used PPN2G and your second PPN1H but you do not have that error.

 

Your heading to LUKEP are the same that I display and RC matches what I have.

 

The difference is like me you appear to be parked at the terminal north of the runway centerline and that is the cause I think of the error. What is your heading shown by RC when you are at the runway thresholds for the easterly runways. I used runway 12 and the heading is 118 as shown in the plan. You navgear and RC will show the heading from where you are (present position) and for a six mile first leg your heading will change a bit as you taxi to the runway.

 

The fact that my GPS and your navgear heading reading and RC agree means that nothing is wrong with those components jn that they match. There also might be an error in the airport location or that of LUKEP that can cause such a discrepancy. RC and my GPS use the coordinates from the flightplan but that does appear OK because it matches the real world SID. It is the location of the aircraft that seems to be different and you need to check for the heading when on the runway as the terminal parking areas are a few degrees counter clockwise when a heading is taken from them.

 

I think you are OK. I have had this effect at most airports until the aircraft is correctly placed on the runway for departure. RC just reads your aircraft location via FSUIPC and your navgear uses whatever method (PMDG FS9 versions also use FSUIPC but its FMC did not like the plan for some reason so I used the Saab.)

 

So always use a runway location to check these items since parking is not in line with them but to either side.

 

Again, if RC and your GPS/FMC navgear read the same heading all is OK.

 

If I have time I'll place an aircraft on runway 12 and see what I get.

 

Now in FSBuild the AIRAC digital database occasionally has local "soft" waypoints added to help define curves are instructions on an intercept point to create a soft waypoint intersection or merge. For the PPN2G I have, those are missing but are apparently in what you have. That does not affect right now what is being discussed.

 

In summary, only use the guidance of RC when you are on course such as on the runway to get to your first waypoint.

 

Another tip is if there is VOR or NDB really close or on the airport, unless you tend to fly over it and we estimate it won't be close enough fo RC credit, eliminate it from the plan sent to RC unless you are using it to reverse course direction.

 

This tip sheet has this information for FSBuild.

 

 

 

 

 

More detail on the bearing difference:

 

I parked on the threshold of RWY 12, loaded the plan in the Saab GPS and RC. Here is what displays:

 

 

 

so the difference was minimal from where I parked at the terminal.

 

Now I checked the FS9 location I have for the airport:

 

 

 

which converts to N43d 18' 04" W002d 54' 38" FSB has the airport at N43d 18' 03" W002d 54' 38". Real world N43d 10' 04" W002d 54' 38" so all is in accord. RC computes the airport center based on runways at N43d 18' 06" W002d 55' 04" which is close enough as noted by the RC heading advisory and the GPS.

 

The coordinates for LUKEP match within 01 sec which is within tolerance (reference FSB rout display against PPN2G SID chart).

 

Now the SID chart shows that first leg at 118d as does the FSB chart. Now if you use a weather app FSB adjusts the mag heading for weather effects I believe based on the last weather snapshot. Here is the last Active Sky METAR I have stored:

 

LEBB 080500Z 13003KT 100V200 8000 -SHRA FEW015 SCT025TCU BKN040 04/04 Q1018 TEMPO 4000 SHRA SCT025TCU

 

so basically it was low speed and about straight down the runway heading so no change there.

 

I can see a three degree difference but not six degrees. However I can tell you following the navgear indications RC has not complained fully crediting the waypoints as crossed which within the thirty nm departure zone is a 2 nm radius difference allowance.

 

I also opened LEBB stock in ADE9X which let me in approach view mode look at waypoints. LUKEP was not named but did show and it true heading from the threshold center was 117.4 true and 120.4 magnetic. This would be used in the default FS9 GPS. The coordinates are for the unnamed are close to the chart coordinates.

 

Anyway we end up with a four degree difference in calculations which is acceptable for that short distance. The airport scenery might be very slightly off center.

 

Best I can do.

 

 

 

 

 

Ronzie, all I can say is I wish all sopport teams would be as competent as you are! You deserve more then a 10! My cudos to you Ronzie!

 

Ok, you have made it quite clear and I understand how this works now and of course we don´t live in a perfect world. Iam greatful you took your time to explain all this to me, and hope this gives reference to others. I appreciate much your help and time Ronzie!

 

Thanks for the tips regarding FSB!

 

One last thing, this is a easy one lol! Which I think you missed...which is the best or proper way to shut down RC?

 

Iam happy to say aim a proud and satisfied owner of Radar Contact and there support team!

 

May you have a wonderful weekend Ronzie!

 

My best to you,

 

Mike

Hi Mike,

 

Followed your exchanges with Ron in great detail.

 

Ron is a great source of information on this forum.

 

I usually close down RC when after exiting the runway and contacting ground you get the option in the RC box of closing down RC by pressing 3.

 

Works very well!

Hi Mike,

 

Followed your exchanges with Ron in great detail.

 

Ron is a great source of information on this forum.

 

I usually close down RC when after exiting the runway and contacting ground you get the option in the RC box of closing down RC by pressing 3.

 

Works very well!

Howdy Norman!

 

Thank you for your advice, will do!

 

I agree, Ron knows his chops! He is of great help Indeed!

 

The thing is that I bought RC (apart from working great and it´s fun), so I could practise ATC proceedings, so it be more realistic and so when I go online I don´t make a fool of myself.  Since aim in the practise stage and when I do something wrong, I do tend to quit the flight in mid air, frustration comes upon me LOL!  So I don´t always make it to ground :lol:

 

What aim doing now is stop RC and afterwards end flight. Don´t know if that´s correct in a situation as explained above.

 

BTW Norman, a bit off-topic here. You might like to check out MCE, it´s a add-on with voice recognition for copilot, ground and RC. You wont fly alone anymore! Check out some vids at YouTube, David Herky is an ace and uses MCE and RC, he has plenty of vids on YT, or type in FSX MCE.

 

Again, thanks for your guidence Norman and enjoy your weekend!

 

May you have safe flights.

 

Care,

 

Mike

If FS closes before RC, RC4 will hang and you need to shut it down with the Win task manager. If you wish to shutdown RC at any point in the flight, just alt-tab to it and press Quit. Option 3 (Terminate Radar or ATC Services) only shows up in the final stages as I recall or may be on the extended menu (9).

 

If I am using the log function and wish to close RC prematurely I use the alt-tab Quit method to insure the log is retained which may not happen on an RC crash.

Ok, thanks Ronzie!

 

Quit, is that the "escape" (Esc) key? Sorry aim on a Spanish keyboard.

Once you have pressed the START button after your flight has been loaded into FS, the RC app is minimized. That button is replaced by a QUIT button after you reopen/maximize  the RC app window with alt-tab.

Once you have pressed the START button after your flight has been loaded into FS, the RC app is minimized. That button is replaced by a QUIT button after you reopen/maximize  the RC app window with alt-tab.

Oh, ok Ronzie I get you now!

 

Sorry, I bought three add-ons this month, OpusFSX, RC and FSB and I think aim a bit saturated with info!

 

Ok got it, all clear now. That´s the way I was doing it.

 

Thank you Ronzie!

 

Good care,

 

Mike

Hi Mike,

 

I cannot get MCE to work for me despite the best efforts of Gerald etc.

 

I fly online with Vatsim,once a week ,and off line with RC the other three flights !Unless ,my cabin crew decide to quit!

A previous user stated there is a special .cfg setting to get MCE top work with RC.

 

Since, Norman, you are on Win 7 for RC, you should have a shortcut to RC and right click on it to have its security set to run as admin, a program, not user level, setting. I don't know about MCE but you could check.

 

Other settings would be to bypass RC and MCE in any security apps as trusted and/or excluded applications.

 

Alt-tab if necessary to look for any blocked error dialog pop-ups.