ronzie

Please see your PM. I forwarded a message from jd.

https://www.dropbox.com/s/jbptsqeal6ht4d3/default%20GA%20flightplans%20V2.zip?dl=0
 
is a zip file that contains a Traffic GA bgl file, the concatenated flight plan text files into the flightplans.txt file, an airports.txt file made from the default, and an aircraft.txt file made from the default. I only included modern GA and I did not include the DC-3. The Piper only flies in North America and the others globally.
 
I did not test this. You can unzip to a folder you create and copy the bgl to the usual FS9\scenery\Word\scenery folder to activate. Rename the original default bgl as previously stated to disable it. Read the flightplans.txt folder in Wordpad to see the global areas covered.
 
Credit goes to James Whitaker for creating the source files in default_ga_flightplans_v2.zip.
 
airports.txt and aircraft.txt were decompiled from the default traffic file traffic030528.bgl provided with FS9 using AIFP3. flightplans.txt was made by copying/pasting the modern aircraft flight plans in default_ga_flightplans_v2.zip.
 
The bgl file was compiled by AIFP version 3 AI Flight Planner - © 2008-2015 - Don Grovestine available here:
 
http://stuff4fs.com/open.asp?Folder=AIFP&JS=TRUE
 
Let me know how it works.
 
Disclaimer:
 
This bgl file should not cause any damage to FS files or your computer. I do not take any responsibility for any damages. The .bgl file was scanned by Norton AV and found clear.

You should include your old email address and registered user name as well so jd can easily locate you in the user database from your original purchase.
 
After reinstalling RC (if you update it) and getting the registration working  be sure to update fsuipc full and interim versions from:
http://forum.simflight.com/topic/66139-updated-modules/
and get makerws from:
http://forum.simflight.com/topic/66136-useful-additional-programs/
so the distribution versions are updated.
 
After all is updated rerun the RC scenery rebuild again.

NOTAMS allows you to deviate from altitudes through pre-approach and approach without reprimand. Crossing restrictions at about 40 nm  out must be met and this occurs before the approach phase. The crossing restriction command starts with "I need you down to (altitude) in xxxxx  or less." There also is a statement that you are responsible for obstacle clearance but altitudes as advisories are given when using NOTAMS.

Two things to note:
 
1. RC does not know about VOR, NDB, or RNAV approaches.
2. It should have assigned a runway by wind direction but if an ai was flying in a different direction then that has first priority.
 
LGKR has no ILS approaches. (I used the information from DEC-2012 from Eurocontrol.) All are VOR.
 
What you need to do after accepting the first vector is go to the extended menu (9) and choose IAP. You'll be able to do this at about 35 nm out. Choose the runway at this point and type of approach that is closest to your needs. In an IAP RC will not monitor you until on close final when tower will contact you. You can fly your approach by GPS or FMC RNAV, or whatever means you use to follow the published procedure.
 
This information also applies if you need to do an NDB approach or a procedure turn or circling approach.
 
While real world there is some faction of approach radar I recommend you choose the IAP method because of the significant difference of about 4000 feet in the MSA based on arrival direction and topology and just concur with the published charts.

The only emergency option in this case is post collision as described starting on page 59 of the RC43 manual if the collision occurred (and you can continue flying your damaged aircraft).
 
There is no post deviation option to advise RC. RC will not quit your plan but you'll get a caution in your critique. RC will see you start to get back on course/altitude and should not nag unless your recovery start is delayed quite a while.
 
You are probably running as advised with the RC option interact with ai as a prelude to ai chatter. RC will attempt to change the course of ai but not in all circumstances such as ai climbing to your altitude.
 
As in real world in order of priority, fly the aircraft, navigate, communicate. It takes too long to request an altitude change in your instance. I keep an eye on the TCAS display and when the ai cursor changes to a caution and indicates a trend before it gets to the RA state I sometimes have enough time to request a different altitude if that provides a resolution.