ronzie

I forgot to mention that for smaller aircraft an option is available in RC to request a shorter down wind to to turn to base. Whether this would be applicable depends on the terrain obstacles

The best way to handle airports in mountainous territory is to use charts. At 40 nm out after approach assigns a runway you can request an IAP approach which disables vectors. RC will not monitor you until on final. You then navigate on your own according the the approach charts. US/FAA charts (current) are free from flightaware.com. UK charts on line free are available from: http://www.nats-uk.ead-it.com/public/index.php%3Foption=com_content&task=blogcategory&id=165&Itemid=3.html no registration required. Eurozone free on line charts are available from: http://ead-website.ead-it.com/publicuser/public/pu/login.jsp registration required. Learn their query system. If you have AIRAC database compatible flight planners and navgear get a one-off subscription to AIRAC data from either Aerosoft (NAVDATA PRO) or Navigraph's FMC package.

Follow the procedures in the pinned help file. Send your original registered e-mail address and user name plus product ident code, updated e-mail address in the posted format to jd@jdtllc.com subject update user information for registration. Include a screenshot of the registration dialog if you wish. If nothing has changed then manually format as indicated the message sending to register@jdtllc.com. The format is critical.

If you send jd your original e-mail address, registered user name, and any order information available you can request a download link (if you need to update your version) and also that the automated registration user database be updated so you can take advantage of the automatic keycode generator. The last RC4 release is 4.3.3845.

One error is using /u for the command line. /u is uninstall. Did your confirmation state for sure it was registered? A Win 10 user might catch this post. Are you also running RC by right clicking on the rcv4.exe and selecting run as admin (even though you are logged in as an admin)?

RC plays via your Win WAV slider on the Win mixer. I think it was FSX that has a way to redirect your pilot headsets to a separate output so check that.

Be sure to update fsuipc and makerwys to insure it works with SE again after install. You will find the path to FSX flight plans slightly different. http://forum.simflight.com/topic/80977-updated-modules/ http://forum.simflight.com/topic/66136-useful-additional-programs/

If you navigate on your own you still may need to get credit for listed waypoints. To skip them go to the extended menu at the appropriate time and choose the direct to option which will allow you to go direct from your present position to the next waypoint you choose. Just try using the common waypoints to all runways in your flight plan. Center will expect you to hit those. Please read the manual regarding the three choices of departure options. Points beyond the 30 nm boundary will fall within the center jurisdiction - no deviation available.

RC ATC is coded for deparure radar finishing just after the 30 nm boundary with the last vector pointing the first waypoint after 30 nm. Your flightplan sent to RC must be in waypoint sync with your navigation system waypoints including the terminal data base. Using NOTAMS may help where commands become advisory. Waypoints STAKR and beyond must be in your flightplan sent to RC. This works here because STAKR is common to all runway departures. Note that in the departure options you choose from three options for vectors within those 30 nm such as no vectors, vectors with altitudes, or vectors with no altitudes. Since the runway is dynamically assigned, you can choose no vectors and then load into your aircraft nav gear the correct departure from its terminal database. My planner database is in sync with my aircraft terminal database data. Sections of this document can apply to any AIRC updated database flight planner. https://www.dropbox.com/s/owuz7p2ohx7y7st/fsb%20tips%20and%20update.pdf?dl=0 You can also after approach contacts you use the IAP option where you'll be responsible for navigating the last 35 nm or so. A third option is to load your entire flight plan including the approach waypoints into your aircraft nav system.

You mean turned off the back course option?

By default, FS9 stock airports have back courses enabled and maybe this was carried over to the UK2000 scenery. When the ILS frequency is the same on both ends of the runway you'll only get the correct one within two degrees of the extended center llne. I recommend you use Airport Design Editor, not AFCAD due to its limitations, to open the AF type file (afcad type) for the UK2K airport. You want the one that shows the runways and taxiways. Once that file is open, choose from the menu bar List Navaids. Click the line for each ILS and then in its properties disable the back course. Then save the file as a project and if no errors compile the new .bgl to replace the one you just edited. To disable the original just change the extension to .bgh so you can restore it if necessary. Start FS and let it reindex. Be sure your new .bgl has priority. Airport Design Editor is freeware from: http://www.scruffyduck.org/ Be sure to also check out the tutorial download section. To open the specific af type file Use File Open Direct from .bgl. In the rare chance that UK2000 is using the stock default afcad, then use Open Stock Airport and edit that which will create a new af type bgl. To see which af type file UK2000 is using try this free tool: http://www.scruffyduck.org/simple-airport-scanner/4584282795 which will search all of your active scenery to create its database. I think it leaves out defaults. After the database is complete enter EGJB into the filter and check the entries left. Most likely there will be one in the UK2000 EGJB folder and that is the one you should edit. When you open it it should have the runways and taxiways. The file that has priority is the last in the list for that airport.

Since you are doing everything your self, have RC set to auto-tune your com radios. Then for that function you can use the combination ack and contact, forgot the menu key at the moment,

You enable the debug log before you hit the Start button in RC. After the problem occurs use the alt-tab method to bring up the full RC window and press the Quit button. You now can shut down FS and follow the instructions I gave about sending it in.

Does this happen with any flight plan? Does it happen with any of the tutorial flights? What flight planner are you using. What version of Windows, FS, are you using. Paste your flight plan into a reply here. To force RC to Quit, alt-tab until the RC window opens. If RC is running, the Start button now is labeled Quit. Do this if you wish to create a log to end in for analysis. Using the task manager to force RC to quit will not save a log to send in. To create a log to send in, load up RC with your aircraft loaded in FS. Click the Debug button. Load your plan. Go through the procedures until you encounter the delivery problem. When the delivery looping begins, wait a couple of cycles, then alt-tab to get to the full RC screen and then press the Quit button. (This is the only way to stop RC and save a log.) You can then stop FS. Go into your your rc folder, Right click on rcv4.log and check that its modified date-time is current. Rename your rcv4.log file to something else so it does not get over written.Zip it up and send it as an attachment to an e-mail explaining the problem to jd@jdtllc.com. jd can then analyze what is going on and perhaps find a solution. See the if you need help topic for other contacts. Be sure you have run the current makerwys.exe from; http://forum.simflight.com/topic/66136-useful-additional-programs/ which is used in the scenery rebuild function. Also be sure you are using the current fsuipc.exe from: http://forum.simflight.com/topic/80977-updated-modules/

First check that your key assignments are correct by looking at the keyboard table in RC. Next check just running RC with a simple default aircraft and FS with no other add-on running to see if there is a key assignment conflict. "Spamming" a key to RC could get things out of order. What I do during clearance delivery is have a piece of notepaper handy ready to jot down just the numbers such as altitude and in abbreviated fashion first waypoint or vector, speed, etc., and then acknowledge. Remember that with the pilot wav option on you will hear the pilot read back the clearance to ATC. Do not use co-pilot auto-reply/comms In RC until you are proficient. it is important to acknowledge in order each instruction. Waiting too long can cause RC to hang. Also be sure you are not holding down any key too long so that it is not repeated (a setting in your PC).

You also need to make sure you are running RC in administrator mode so it properly executes makerwys.exe in your FS folder. If you are not on an RC pc operating as a client to a networked FS host, be sure to answer No when prompted if you are on a network so RC executes makerwys. Here is a work around if it is a path access problem. You basically follow the network procedure even though RC and FS may reside on the same computer. Run makerws.exe first in your FS folder. Check to see if you get the dialog procedure countdowns from makerwys. Get the date and time from the rcv5 properties in that folder and make sure they are current. Now start RC with run as admin and run the scenery rebuild insuring your path to FS9 is correct when prompted. RC should give the progress of copying r5.csv in your FS folder to rcv4\data (as rcv4). OK that and then you should get the message rebuilding a4.csv. OK that and when it finishes OK again. Wait a minute for the HD to catch up before shutting down RC and restarting it. (In this method you have run makerwys.exe directly first.) RC has copied r5.csv to it it owen data folder as r4.csv. Check that file's date and time and it should only be a few seconds later. The date and time ofa4.csv should be just a few seconds after that. What we have done is insure makerwys has performed correctly and then RC has copied r5.csv as r4.csv to its data folder and then built a4.csv. What operating system are you running? http://forum.simflight.com/topic/66136-useful-additional-programs/ is the link to current makerwys.exe to install in your FS folder. Of note: "4.697 prevents interruption during the final second or two whilst files are written"

It might be worth trying Airport Design Editor freeware: http://www.scruffyduck.org/ It was created with knowledge of the FS9 SDK which was not published when AFCAD was designed. ADE is more compatible with freeware and commercial software that follows the SDK rules. In ADE you first edit in a project environment, test, and if OK, compile to a .bgl. If you need to change your design you edit the project items and then compile again. ADE has facilities for opening an airport direct from a .bgl (including default stock), importing separate items from a scenery .bgl into your project, and other needs. AFCAD is known not to import many types of scenery items that ADE will handle. Perhaps that is where some of your problems lie, Give it a try by skimming the manual, importing from stock or your scenery, modifying items, and then checking the runway properties for elevation, surface type, etc. Another type of problem that affects layers is the rounding of elevation parameters. Some airport designers lay down a base surface layer polygon and then create the runway at a slightly higher elevation over that. Skim the ADE tutorials to get an idea of the procedures and see if the expanded tools fit your needs.

Pre-recorded chatter is not recommended as it introduces lots of chatter not relevant to your flight such as general low altitude chatter when you are flying in the upper ATC strata. This loads down your audio card unnecessarily. The chatter you really need is produced by the presence of AI which affects traffic. You do not have the performance capability of an added audio card, even a simple one, unless your "hi-rez settings" you are referring to are on an added card. FS and RC do not use surround, just stereo but the L-R channels are duplicates. Some cards emulate 5.1 or 7.1 from stereo which adds overhead and sometimes interfere with RC audio channel distribution. Just some added information for future reference. Your reference to 192000 Hz probably is a typo and is probably 19200 Hz. since the human audible range decays rapidly after after about 20000 Hz. Some say they can sense a quality difference using 22000Hz limits but that would be very unusual.

Never use Excel or other database/spreadsheet file. It will corrupt an rc .csv file. To open in Wordpad or other text editor, right click on r5.csv and select open with. Directly editing r5.csv is temporary only and it must preserve the format. Your change will be wiped out on the next running of makerwys.exe direct or via the RC scenery rebuild. To change an ILS frequency you need to run the freeware ADE (Airport Design Editor) or payware AFX. Do NOT use AFCAD. Airport sdesign Editor is here: http://www.scruffyduck.org/ First make a safe copy of your EDDF scenery folder as a restoration backup. In your FS folder there is a large file called runways.txt, a log of the data it collected. Open it with Wordpad. Search for Airport EDDF. After the default you'll eventually find a deletion section and a section with runway data. Keep repeating the search until you are at the last folder which has priority. The path displayed in that last section will point to the af type file you need to edit. Make a note of that path. See if the description of the runways includes the ILS data for the runway you want to edit. If so, continue. For ADE after you set it up with options you choose you would use File, Open Direct From BGL. Navigate to the EDDF scenery folder using the path you noted and the file name noted. Selecting that file should open a diagram of the airport. In the ADE menu bar List, Navaids. You can now edit the frequency of the ILS by double clicking on it. Save your changes. Then File Save Project and note any errors. If no errors choose File Compile and you will get a .bgl file you can use to replace the original file by renaming the original to EDFxxxx.bak to it won't be recognized and copy the new bgl in place. Now in the FS9 Aerosoft Airports collection for Germany I have, there is no .bgl file recognized by ADE. The runway diagram does not even show the localizer symbols. They must have used a special overlay non-standard that is recognized. No runway navaids were shown in the runways.txt file. I suspect makerwys is using a default stock airport for that data. You can try using ADE to open the stock EDDF and make changes as I described and save/compile that airport and add that new folder to your scenery database at a priority lower (not at the top) than the Aerosoft EDDF folder. Start FS to create a new index and than run the RC scenery rebuild again. See what happens. Here from my FS9 default EDDF is an extract showing runways data with ILS information: Airport EDDF :N50:01:59.9958 E008:34:13.9995 364ft Country Name="Germany" State Name="" City Name="Frankfurt-Main" Airport Name="Frankfurt-Main" in file: Scenery\EURW\scenery\AP950140.BGL Runway 26L/8R centre: N50:01:53.2254 E008:33:01.9290 364ft Runway 8R closed for landing and take-off Start 26L: N50:02:06.7014 E008:33:58.4664 364ft Hdg: 249.6T, Length 8189ft Computed start 26L: Lat 50.035362 Long 8.566926 Hdg: 249.620 true (MagVar 0.000), Concrete, 8189 x 148 ft Primary ILS ID = IFWL Primary ILS: IFWL 111.35 Hdg: 249.6 , Flags: GS DME BC "ILS/DME 26L" *** Runway *** EDDF0261 Lat 50.035362 Long 8.566926 Alt 364 Hdg 250 Len 8189 Wid 148 ILS 111.35, Flags: GS DME BC and here is the FS9 Aerosoft EDDF data showing lack of ILS information: aerosoft\EDDF_2005\scenery\AF2_EDDF_Gap-Team_Full_with_Custom_AI.bgl ============================================================================= Airport EDDF :N50:01:59.9958 E008:34:13.9995 364ft Country Name="Germany" State Name="Hesse" City Name="Frankfurt-Main" Airport Name="Frankfurt-Main" in file: aerosoft\EDDF_2005\scenery\AF2_EDDF_Gap-Team_Full_with_Custom_AI.bgl Runway 7L/25R centre: N50:02:19.9183 E008:33:38.9001 364ft Start 7L: N50:01:57.9549 E008:32:07.0735 364ft Hdg: 69.6T, Length 13099ft Computed start 7L: Lat 50.032612 Long 8.534585 Start 25R: N50:02:41.0070 E008:35:07.1685 364ft Hdg: 249.6T, Length 13099ft Computed start 25R: Lat 50.045124 Long 8.587026 Hdg: 69.620 true (MagVar 0.000), Concrete, 13099 x 197 ft *** Runway *** EDDF0071 Lat 50.032612 Long 8.534585 Alt 364 Hdg 70 Len 13099 Wid 197 *** Runway *** EDDF0252 Lat 50.045124 Long 8.587026 Alt 364 Hdg 250 Len 13099 Wid 197 Runway 7R/25L centre: N50:02:01.6479 E008:33:37.2697 364ft Start 7R: N50:01:39.7169 E008:32:05.4223 364ft Hdg: 69.6T, Length 13101ft Computed start 7R: Lat 50.027534 Long 8.534131 Start 25L: N50:02:22.8662 E008:35:06.1673 364ft Hdg: 249.6T, Length 13101ft Computed start 25L: Lat 50.040047 Long 8.586574 Hdg: 69.620 true (MagVar 0.000), Concrete, 13101 x 148 ft *** Runway *** EDDF0072 Lat 50.027534 Long 8.534130 Alt 364 Hdg 70 Len 13101 Wid 148 *** Runway *** EDDF0251 Lat 50.040047 Long 8.586575 Alt 364 Hdg 250 Len 13101 Wid 148 Runway 18 /36 centre: N50:00:59.4184 E008:31:33.8136 364ft Runway 18 closed for landing Runway 36 closed for landing Start 18 : N50:02:02.1986 E008:31:33.1781 364ft Hdg: 179.5T, Length 13110ft Computed start 18 : Lat 50.034485 Long 8.525888 Start 36 : N49:59:56.1847 E008:31:34.4059 364ft Hdg: 0.0T, Length 13110ft Computed start 36 : Lat 49.998528 Long 8.526230 Hdg: 179.650 true (MagVar 0.000), Concrete, 13110 x 148 ft *** Runway *** EDDF0180 Lat 50.034485 Long 8.525888 Alt 364 Hdg 180 Len 13110 Wid 148 *** Runway *** EDDF0360 Lat 49.998528 Long 8.526230 Alt 364 Hdg 360 Len 13110 Wid 148

All I can tell you is that RC uses the scenery data pulled by makerwys.exe. Open in wordpad in your FS folder (do no use Excel or other data base app) and search in r5.csv (renamed to r4.csv in your rcv4 data folder) and search for entries for EDDF. You'll find the ILS frequency with letters like DG for glideslope and dme. Do those match your 747 values?

I always burn my downloaded install file and a text copy of my license information to a CD/DVD. Most systems have this drive. If not, consider a large USB "stick" drive which can be updated up to 500 times or more. I have on my Win 7 64 system a 32 GB thumb drive available for this purpose. This way updated installs can be overwritten or accommodated as I wish. This avoids having to download again a time consuming large file like for RC.

Here is a technique for making non-parallel runways simultaneously active: http://www.fsdeveloper.com/forum/threads/seeking-clarification-on-crosswind-runway-technique-star.15432/ The tutorial referred to is not posted but there is enough information in this thread to give you the idea.

The GUI is a bit intricate overall for ASE. You can pull down archived weather. After ASE first initializes, click on historical. As I test I set one hour back from my current Z time (of 0733) to 0600 Z (archives are to nearest hour). It took about three minutes with no apparent activity with the completion message then occurring. You can also search the archives for a specific weather condition.

http://www.avsim.com/topic/489360-update-rc43-to-match-the-actual-existing-runways/ Please go through that thread. Make sure you have updated makerwys.exe from: http://forum.simflight.com/topic/66136-useful-additional-programs/ Using Wordpad go through the runways.txt file in your FS9 folder. Search on airport EHAM. first will come the default. Search again and you'll come upon a deletion section for EHAM and check the scenery path in that section. Next (not necessarily addjacent) will come a section with runway data, etc. Check that scenery path. Keep searching until the last Airport EHAM. That has priority. Be sure the runway data shows. Next in the FS9 folder examine r5.csv for EHAM. There should be a line for each EHAM runway. (The r4.csv in FS9 is not used in rvc4 build 3845. the last release.) Look at the date and time of the r5.csv. (right click, proprties, detail). Go into your rcv4/data folder. Repeat the steps for r4.csv and also the date time is very close to the one you checked on r5.csv. Now check the date-time for a4.csv which should be a few seconds later then r5.csv. Browse a4.csv for EHAM information regarding the calculated airport center coordinates and other information. See if it is all there.

...deleted...