HIFor some unknown reason everytime I load a flight plan in RC4 and then click the button to run RC4 my aircraft suddenly loses the landing gear and crashes on its belly and also moves to a different spot at the airport. I have MY Traffic installed which includes several bgls for many airports in a scenery file that is selected in FSX. Could it be that when I hit the Rebuild scenery DB it did not pick up these airport bgls in the MYtraffic scenery file which is now causing RC4 to crash my aircraft.Don

HIFor some unknown reason everytime I load a flight plan in RC4 and then click the button to run RC4 my aircraft suddenly loses the landing gear and crashes on its belly and also moves to a different spot at the airport. I have MY Traffic installed which includes several bgls for many airports in a scenery file that is selected in FSX. Could it be that when I hit the Rebuild scenery DB it did not pick up these airport bgls in the MYtraffic scenery file which is now causing RC4 to crash my aircraft.Don

get the latest makerwys.exe and install it in the root of fsxclick the rebuild rc scenery databasesee what happensi'm guessing this doesn't happen at default airports?jd

get the latest makerwys.exe and install it in the root of fsxclick the rebuild rc scenery databasesee what happensi'm guessing this doesn't happen at default airports?jd

Hi JdThe only version I have of makerwys.exe is version 4.0 and it is already in the root of fsx. I have tried re buid the database with unfortunately the same result afterwards. And you are right it seems to be not happening at the default airports. using XP I had no problem using these airport sceneries with MYtraffic and Radar Contact together with fsx. For some strange reason Im getting this now using windows 7 -64. Im going to experiment a little here to try and narrow down what might be the culprit. If you have any ideas please advise thanksDon

Get MakeRunways 4.41 from here:http://www.schiratti.com/dowson.htmland put it in your FS route folder. Although it is in the FS9 section it is for FSX as well. FSUIPC v4.41 fixed an issue with its reading of scenery priorities and running 4.0 does not address that. The result of running your current version of 4.0 is probably causing an error with some add-on sceneries and data RC uses.Also get the current version of FSUIPC (v4.60 for FSX and 3.98 for FS9) from that same page for your version of FS. Unzip FSUIPC into a temporary folder. Run the FSUIPC installer and make sure it places it in your FS folder. If you have a problem with FS folder detection eventually it will let you browse to it. To run the installer you must be logged in as an admin and run the installer set to run as admin.Be sure you are logged in as an admin as well as running the RC as an admin. It needs both. You also must correctly put in the full path to your FS folder each time you run the rebuild.As the rebuild runs you should see a pop-up box from makerwys waiting for an OK, then a counting up of airports and runways, then a pop-up saying makerwys is complete. After an OK an RC box pops-up about copying r5.csv, then a pop-up stating building a4.csv or similar pop-ups. A minute after you OK the finished building a4.csv box you can close RC.Now go into the data folder under your rcv4 folder using Explorer or My Computer. Go to a detailed view of the file list and check the date and times of r4.csv and a4.csv to make sure they are current and all the processes worked.FSUIPC reports the position of your aircraft to RC which then compares it to its scenery database files. If it is too far off RC will move your aircraft to what RC thinks is within your aircraft boundaries. This makes me think either a position reporting discrepancy or a scenery database discrepancy is happening.Finally just a couple of checks:Be sure you are loading a flightplan that starts at the same airport as where your aircraft is parked. (Don't laugh - it has happened.) Also, be sure you started the scenery database rebuild from within RC.Some Win 7 users have also stated they needed to reinput the FS and FLT-WXR paths each time they ran RC just in case that is an issue.

Get MakeRunways 4.41 from here:http://www.schiratti.com/dowson.htmland put it in your FS route folder. Although it is in the FS9 section it is for FSX as well. FSUIPC v4.41 fixed an issue with its reading of scenery priorities and running 4.0 does not address that. The result of running your current version of 4.0 is probably causing an error with some add-on sceneries and data RC uses.Also get the current version of FSUIPC (v4.60 for FSX and 3.98 for FS9) from that same page for your version of FS. Unzip FSUIPC into a temporary folder. Run the FSUIPC installer and make sure it places it in your FS folder. If you have a problem with FS folder detection eventually it will let you browse to it. To run the installer you must be logged in as an admin and run the installer set to run as admin.Be sure you are logged in as an admin as well as running the RC as an admin. It needs both. You also must correctly put in the full path to your FS folder each time you run the rebuild.As the rebuild runs you should see a pop-up box from makerwys waiting for an OK, then a counting up of airports and runways, then a pop-up saying makerwys is complete. After an OK an RC box pops-up about copying r5.csv, then a pop-up stating building a4.csv or similar pop-ups. A minute after you OK the finished building a4.csv box you can close RC.Now go into the data folder under your rcv4 folder using Explorer or My Computer. Go to a detailed view of the file list and check the date and times of r4.csv and a4.csv to make sure they are current and all the processes worked.FSUIPC reports the position of your aircraft to RC which then compares it to its scenery database files. If it is too far off RC will move your aircraft to what RC thinks is within your aircraft boundaries. This makes me think either a position reporting discrepancy or a scenery database discrepancy is happening.Finally just a couple of checks:Be sure you are loading a flightplan that starts at the same airport as where your aircraft is parked. (Don't laugh - it has happened.) Also, be sure you started the scenery database rebuild from within RC.Some Win 7 users have also stated they needed to reinput the FS and FLT-WXR paths each time they ran RC just in case that is an issue.

HiThanks for the indepth reply. However I have done all of the above except for updating the makerwys exe file which I will do. However there seems to be distinct difference with windows 7 with respect to the scenery cfg file. Apparently the scenery cfg file in the root of FSX does not update itself when adding scenery to FSX such as airports and Mytraffic. The scenery.cfg file that gets updated is located in the ProgramData/Microsoft/FSX sub-directory, not the scenery.cfg file contained in the FSX root directory. So my question is this. Where does makerwys get its scenery cfg info from to compile its list of runways etc from FSX? If it gets it from the scenery cfg file in the root of FSX there is definately a problem.Don

HiThanks for the indepth reply. However I have done all of the above except for updating the makerwys exe file which I will do. However there seems to be distinct difference with windows 7 with respect to the scenery cfg file. Apparently the scenery cfg file in the root of FSX does not update itself when adding scenery to FSX such as airports and Mytraffic. The scenery.cfg file that gets updated is located in the ProgramData/Microsoft/FSX sub-directory, not the scenery.cfg file contained in the FSX root directory. So my question is this. Where does makerwys get its scenery cfg info from to compile its list of runways etc from FSX? If it gets it from the scenery cfg file in the root of FSX there is definately a problem.Don

Hi Don,Do make sure that the scenery updates in the FSX scenery files,as with many add ons you need to do this asa manual task.My traffic used to have in its instructions details about how to install it into FSX in the correct manner.Some of these files reside within the FSX library as seperate entries.Worth checking out.Norman Bowman

Hi Don,Do make sure that the scenery updates in the FSX scenery files,as with many add ons you need to do this asa manual task.My traffic used to have in its instructions details about how to install it into FSX in the correct manner.Some of these files reside within the FSX library as seperate entries.Worth checking out.Norman Bowman

HiI updated the makerwys exe file and sure enough it found the proper scenry cfg file and for the first time i saw it include my addon areas. Then I noticed that all my saved flight plans were read only so I changed the attributes for this file folder and deleted the saved plns inside. I then made a new flight plan starting at ksfo and ran FSX as admin, when sitting a the gate i then ran RC4 as admin also and selected the same flight plan and as soon as I hit the start RC4 button my plane suddenly changed position and crashed without any gear. I have to admit I am getting a little frustrated. I have no other programs running just FSX and RC4. I do have other airport scenerys running that are part of mytraffic. I will unselect the mytraffic airport scenerys in FSX and re run RC4 database builder and then run fsx again with RC4 and see what happens.PS I should add that everything I have installed including the scenery files all ran perfectly with rc4 in XP and I never had this problem until I install FSX into Windows 7Don

"The scenery.cfg file that gets updated is located in the ProgramData/Microsoft/FSX sub-directory, not the scenery.cfg file contained in the FSX root directory." When we talk of the FSX root directory we mean "x:/ProgramFiles/Microsoft Games/FSX/". I don't think the Win 7 install is any different nor is the FSX default install folder from FS9. You can install FS in the folder of your choice.VISTA and more so Win 7 have high complex security accesses on any disk partition for any applications and their files stored under a Program Files tree structure, which is why the business of having elevated user and and program admin rights is necessary. This applies to FSX and any add-ons accessing FSX and its folders. It also applies to scenery installs such .exe and .bat files which need those elevated privileges for their installs. Because of this many support contributors on various FS conferences have suggested avoiding selecting a default install of FSX or FS9 or add-on utility under any Program Files folder for these operating systems.What flight planner are you using? FSX can use both FS9 format and FSX XML format flans. RC had one problem with a planner that inserted an extra comma in its FS9 format file that caused a relocation of aircraft as I recall.Create a file of type .txt with notepad, etc., naming it KSFO.txt. In another instance of that text editor open the .pln file of your KSFO departure and copy the first few lines to the first waypoint then paste it into KSFO.txt. Close the .pln file in the second text editor without saving. Now open a4.csv in that second text editor instance, search for KSFO, and copy that comma delimited line then pasting into KSFO.txt. In the second editor close a4.csv without saving.Now with that second editor open the file runways.txt in your FSX folder. That is large file and takes a few seconds to open. It is a log file of what the makerwys.exe did as part of the scenery rebuild process. Each instance of an airport scenery including afd afcad equivalent files is read in order of priority. In my FS9 the first instance of KSFO is the default as the following extract shows:Airport KSFO :N37:37:08.2908 W122:22:29.5987 13ft City Name="San Francisco" Airport Name="San Francisco Intl" in file: Scenery\NAMW\scenery\AP915180.BGL Runway 10L/28R centre: N37:37:16.0655 W122:22:30.9490 13ft Start 10L: N37:37:42.6288 W122:23:34.3853 13ft Hdg: 117.9 true Computed start 10L: Lat 37.628731 Long -122.393423 Start 28R: N37:36:49.5021 W122:21:27.5128 13ft Hdg: 297.9 true Computed start 28R: Lat 37.613525 Long -122.357111 Hdg: 117.870 true (MagVar 15.600), ASPHALT, 11861 x 200 ft Secondary ILS ID = IGWQ Secondary ILS: IGWQ 111.70 Hdg: 297.9 , Flags: GS DME BC "CAT III ILS/DME 28R" *** Runway *** KSFO0101 Lat 37.628731 Long -122.393425 Alt 13 Hdg 102 Len 11861 Wid 200 *** Runway *** KSFO0282 Lat 37.613525 Long -122.357109 Alt 13 Hdg 282 Len 11861 Wid 200 ILS 111.70, Flags: GS DME BC Runway 10R/28L centre: N37:37:06.5739 W122:22:28.3000 13ft Start 10R: N37:37:30.2218 W122:23:24.7602 13ft Hdg: 117.9 true Computed start 10R: Lat 37.625286 Long -122.390741 Start 28L: N37:36:42.8937 W122:21:31.8386 13ft Hdg: 297.9 true Computed start 28L: Lat 37.611698 Long -122.358313 Hdg: 117.880 true (MagVar 15.600), ASPHALT, 10594 x 200 ft Secondary ILS ID = ISFO Secondary ILS: ISFO 109.55 Hdg: 297.9 , Flags: GS DME BC "ILS/DME 28L" *** Runway *** KSFO0102 Lat 37.625286 Long -122.390739 Alt 13 Hdg 102 Len 10594 Wid 200 *** Runway *** KSFO0281 Lat 37.611698 Long -122.358315 Alt 13 Hdg 282 Len 10594 Wid 200 ILS 109.55, Flags: GS DME BC Runway 1R/19L centre: N37:37:02.3303 W122:22:25.4998 13ft Start 1R: N37:36:26.0162 W122:22:49.6077 13ft Hdg: 27.7 true Computed start 1R: Lat 37.606808 Long -122.380723 Offset Threshold primary: 238 feet Start 19L: N37:37:38.6443 W122:22:01.3907 13ft Hdg: 207.7 true Computed start 19L: Lat 37.627819 Long -122.366774 Hdg: 27.740 true (MagVar 15.600), ASPHALT, 8654 x 200 ft Secondary ILS ID = ISIA Secondary ILS: ISIA 108.90 Hdg: 207.7 , Flags: GS DME BC "ILS/DME 19L" *** Runway *** KSFO0012 Lat 37.606808 Long -122.380722 Alt 13 Hdg 12 Len 8654 Wid 200 *** Runway *** KSFO0191 Lat 37.627819 Long -122.366776 Alt 13 Hdg 192 Len 8654 Wid 200 ILS 108.90, Flags: GS DME BC Runway 1L/19R centre: N37:37:05.1486 W122:22:34.1790 13ft Start 1L: N37:36:33.8233 W122:22:54.9601 13ft Hdg: 27.7 true Computed start 1L: Lat 37.608986 Long -122.382208 Offset Threshold primary: 491 feet Start 19R: N37:37:36.4415 W122:22:13.3978 13ft Hdg: 207.7 true Computed start 19R: Lat 37.627205 Long -122.370111 Hdg: 27.740 true (MagVar 15.600), ASPHALT, 7505 x 200 ft *** Runway *** KSFO0011 Lat 37.608986 Long -122.382210 Alt 13 Hdg 12 Len 7505 Wid 200 *** Runway *** KSFO0192 Lat 37.627205 Long -122.370110 Alt 13 Hdg 192 Len 7505 Wid 200-----------------------------------------------end extract-------------------------------Move your cursor down until you hit the next airport section and then search again to find an instance of KSFO. The next instance I have is Fly Tampa's FS9 older add-on for KSFO:=============================================================================Area.177 "US-Airports-SanFrancisco" (Layer=178)Local=aerosoft\U.S. Airports\SanFrancisco=============================================================================aerosoft\U.S. Airports\SanFrancisco\scenery\af2_flytampa_ksfo.bgl=============================================================================Deletions check for Airport KSFO: Delete all taxiways! Delete all runways and starts! *** DelBth *** KSFO0011 Lat 37.608986 Long -122.382210 Alt 13 Hdg 12 Len 7505 Wid 200 *** DelBth *** KSFO0012 Lat 37.606808 Long -122.380722 Alt 13 Hdg 12 Len 8654 Wid 200 *** DelBth *** KSFO0101 Lat 37.628731 Long -122.393425 Alt 13 Hdg 102 Len 11861 Wid 200 *** DelBth *** KSFO0102 Lat 37.625286 Long -122.390739 Alt 13 Hdg 102 Len 10594 Wid 200 *** DelBth *** KSFO0191 Lat 37.627819 Long -122.366776 Alt 13 Hdg 192 Len 8654 Wid 200 ILS 108.90, Flags: GS DME BC *** DelBth *** KSFO0192 Lat 37.627205 Long -122.370110 Alt 13 Hdg 192 Len 7505 Wid 200 *** DelBth *** KSFO0281 Lat 37.611698 Long -122.358315 Alt 13 Hdg 282 Len 10594 Wid 200 ILS 109.55, Flags: GS DME BC *** DelBth *** KSFO0282 Lat 37.613525 Long -122.357109 Alt 13 Hdg 282 Len 11861 Wid 200 ILS 111.70, Flags: GS DME BC Delete all taxiways! COM: Delete all frequencies!=============================================================================aerosoft\U.S. Airports\SanFrancisco\scenery\af2_flytampa_ksfo.bgl=============================================================================Airport KSFO :N37:37:08.2908 W122:22:29.5987 13ft City Name="San Francisco" Airport Name="San Francisco Intl" in file: aerosoft\U.S. Airports\SanFrancisco\scenery\af2_flytampa_ksfo.bgl Runway 10L/28R centre: N37:37:16.0655 W122:22:31.0055 13ft Start 10L: N37:37:42.6612 W122:23:34.3727 13ft Hdg: 117.9 true Computed start 10L: Lat 37.628731 Long -122.393438 Start 28R: N37:36:49.4049 W122:21:27.5529 13ft Hdg: 297.9 true Computed start 28R: Lat 37.613525 Long -122.357127 Hdg: 117.870 true (MagVar 15.600), ASPHALT, 11861 x 200 ft Secondary ILS ID = IGWQ *** No matching ILS record - assume provided by another layer *** Runway *** KSFO0101 Lat 37.628731 Long -122.393440 Alt 13 Hdg 102 Len 11861 Wid 200 *** Runway *** KSFO0282 Lat 37.613525 Long -122.357124 Alt 13 Hdg 282 Len 11861 Wid 200 Runway 10R/28L centre: N37:37:06.5739 W122:22:28.3000 13ft Start 10R: N37:37:30.2542 W122:23:24.7390 13ft Hdg: 117.9 true Computed start 10R: Lat 37.625286 Long -122.390741 Start 28L: N37:36:42.8613 W122:21:31.8643 13ft Hdg: 297.9 true Computed start 28L: Lat 37.611698 Long -122.358313 Hdg: 117.880 true (MagVar 15.600), ASPHALT, 10594 x 200 ft Secondary ILS ID = ISFO *** No matching ILS record - assume provided by another layer *** Runway *** KSFO0102 Lat 37.625286 Long -122.390739 Alt 13 Hdg 102 Len 10594 Wid 200 *** Runway *** KSFO0281 Lat 37.611698 Long -122.358315 Alt 13 Hdg 282 Len 10594 Wid 200 Runway 1R/19L centre: N37:37:02.3627 W122:22:25.5305 13ft Start 1R: N37:36:26.0162 W122:22:49.6077 13ft Hdg: 27.7 true Computed start 1R: Lat 37.606819 Long -122.380731 Offset Threshold primary: 238 feet Start 19L: N37:37:38.7091 W122:22:01.4051 13ft Hdg: 207.7 true Computed start 19L: Lat 37.627831 Long -122.366782 Hdg: 27.740 true (MagVar 15.600), ASPHALT, 8654 x 200 ft Secondary ILS ID = ISIA *** No matching ILS record - assume provided by another layer *** Runway *** KSFO0012 Lat 37.606819 Long -122.380730 Alt 13 Hdg 12 Len 8654 Wid 200 *** Runway *** KSFO0191 Lat 37.627831 Long -122.366783 Alt 13 Hdg 192 Len 8654 Wid 200 Runway 1L/19R centre: N37:37:05.1486 W122:22:34.1919 13ft Runway 1L closed for landing Runway 19R closed for landing Start 1L: N37:36:33.8233 W122:22:54.9601 13ft Hdg: 27.7 true Computed start 1L: Lat 37.608986 Long -122.382216 Offset Threshold primary: 491 feet Start 19R: N37:37:36.4739 W122:22:13.4298 13ft Hdg: 207.7 true Computed start 19R: Lat 37.627205 Long -122.370119 Hdg: 27.740 true (MagVar 15.600), ASPHALT, 7505 x 200 ft *** Runway *** KSFO0011 Lat 37.608986 Long -122.382217 Alt 13 Hdg 12 Len 7505 Wid 200 *** Runway *** KSFO0192 Lat 37.627205 Long -122.370117 Alt 13 Hdg 192 Len 7505 Wid 200-------------------------------end extract--------------------------------------Copy and paste whatever you have into KSFO.txt. Move the cursor to the next airport section and again search for KSFO and repeat the copy/paste procedure. Do this until there are no more KSFO sections.Close runways.txt without saving and quit that second instance of that editor. Now save KSFO.txt.In a reply here you should be able to attach this KSFO.txt file which is a format that AVSIM allows.In all of these KSFO sections in runways.txt it is the last one that dominates. That last section should not contain deletes only. This last section is used to create r5.csv in your FSX folder. RC's process copies that as r4.csv into your RC\data folder and then creates a4.csv from that as well.All this is insuring that coordinates in your .pln file and a4.csv file match and that you are not getting a different afd type scenery file from your add-on KSFO into your RC scenery database.Note that the runways.txt sections also show the paths to these scenery files which can aid in making any "illegal" entries invalid by renaming the .bgl files.If you have a KSFO add-on in addition to your My Traffic add-on, it will show here. Generally the My Traffic or other traffic utility that introduces an afd type file must have that file made ineffective by renaming the extension so it does not dominate over your add-on airport scenery afd type file. Runways.txt will show if that is the case.I know this is a lot to do but we should be able to get to the bottom of things here.

RonWow that is some indepth reply. Thanks so much for the time and effort its much appreciated. I have the info you requested but when I tried to upload the txt as an attachment I get this "Upload failed. Please ask the administrator to check the settings and permissions" Why is it everywhere I turn with this windows 7 its another road block?Don

Make sure you saved the file as type .txt and it has a single .txt extension. What is the file size? I assume you logged in to the forum.