need some help with missing airport details

[Guest doggy769]

Hi guys

[jd 57]

if you have scenery for the new airport, then rebuilding the scenery database will provide the correct entries for the airport (a4.csv) and the runways (r4.csv)looks like you know how to add the frequencies into the f4.csv file.does that help?

[Guest doggy769]

thanks for the quick reply.....yes i have the scenery from siamavsim for the new VTBS ......have rebuilt scenery database several times but VTBS is not listed in the a4 or r4 data files except where i added it the the f4.csv.....i guess it has something do do with the scenery. is there any way i can add this info to the correct data files....thanks againcameron

[jd 57]

it would be better if we figure out what/why the scenery isn't being picked up by the makerwys.execan you verify that makerwys.exe in the fs root directory is 3.97?

[ronzie 21]

I thought ICAO codes were swapped but apparently not. Disregard.

[Guest doggy769]

>it would be better if we figure out what/why the scenery>isn't being picked up by the makerwys.exe>>can you verify that makerwys.exe in the fs root directory is>3.97?hi jd,it would appear that i have makerwys version 2.90...and am currently using RC4.2thanks againcameron

[ronzie 21]

You need to update the makerws. http://fsuipc.simflight.com/beta/MakeRunways_Beta_398.zip and install it in your FS9 or FSX root folder. Rename your current makerwys.exe to makerwys.xxx first so you have a backup.After the new version is in place open RC and run the Scenery Database Rebuild utility.

[Guest doggy769]

thanks for your advice.i hav downloaded/installed makerwys 3.98 to the fs9 folder and run the rebuild....i still don't have VTBS listed in the a4 r4 etc.....sorry...any other suggestionscheers and thanks again cameron

[jd 57]

john burgess will be waking up in a few hours, maybe he'll have a couple of ideasjd

[ronzie 21]

When you run the scenery rebuild utility a file is created called runways.txt in your FS9 folder, the same folder where make runways is located.Open that up in notepad and search for VTBS sections. Copy and paste those sections into a new file and save it. That file is a detailed log of what makerwys.exe is doing.If you can zip it up and attach it to a reply here in this (bottom section of reply form here) we can look at it. It is important that you zip it up to preserver its format.You may have one or more sections that look like this:=============================================================================Area.160 "FRF-KDFWv3" (Layer=76)Local=......CommonAddonSceneryFRF-KDFWv3=============================================================================......CommonAddonSceneryFRF-KDFWv3sceneryAF2_KDFWSTAR.bgl=============================================================================Airport KDFW N32:54:03.2304 W097:02:25.5068 603ft Delete all taxiways! Delete all runways and starts!*** DEL *** KDFW0131 Lat 32.912563 Long -97.021469 Alt 603 Hdg 130 Len 9004 Wid 200*** DEL *** KDFW0132 Lat 32.909645 Long -97.083092 Alt 603 Hdg 133 Len 9307 Wid 150 ILS 109.50*** DEL *** KDFW0171 Lat 32.898342 Long -97.009766 Alt 603 Hdg 175 Len 8517 Wid 150 ILS 111.75*** DEL *** KDFW0172 Lat 32.915703 Long -97.029808 Alt 603 Hdg 175 Len 13427 Wid 200 ILS 111.35*** DEL *** KDFW0173 Lat 32.910160 Long -97.025948 Alt 603 Hdg 175 Len 11411 Wid 150 ILS 110.30*** DEL *** KDFW0181 Lat 32.915802 Long -97.050674 Alt 603 Hdg 175 Len 13427 Wid 200 ILS 110.55*** DEL *** KDFW0182 Lat 32.910305 Long -97.054619 Alt 603 Hdg 175 Len 11411 Wid 150 ILS 111.90*** DEL *** KDFW0311 Lat 32.890335 Long -97.063194 Alt 603 Hdg 313 Len 9307 Wid 150*** DEL *** KDFW0312 Lat 32.894993 Long -97.000793 Alt 603 Hdg 310 Len 9004 Wid 200 ILS 110.90*** DEL *** KDFW0351 Lat 32.878876 Long -97.030006 Alt 603 Hdg 355 Len 13427 Wid 200 ILS 111.35*** DEL *** KDFW0352 Lat 32.874981 Long -97.009903 Alt 603 Hdg 355 Len 8517 Wid 150 ILS 111.75*** DEL *** KDFW0353 Lat 32.878857 Long -97.026115 Alt 603 Hdg 355 Len 11411 Wid 150 ILS 110.30*** DEL *** KDFW0361 Lat 32.879002 Long -97.054771 Alt 603 Hdg 355 Len 11411 Wid 150 ILS 111.90*** DEL *** KDFW0362 Lat 32.878975 Long -97.050873 Alt 603 Hdg 355 Len 13427 Wid 200 ILS 110.55 Runway 13L/31R centre: N32:54:13.5966 W097:00:40.0638 603ft Runway 13L closed for landing Runway 31R closed for take-off Start 13L: N32:54:44.0149 W097:01:15.8472 603ft Hdg: 135.4 true Computed start 13L: Lat 32.912563 Long -97.021466 Offset Threshold primary: 625 feet Start 31R: N32:53:43.1783 W097:00:04.2806 603ft Hdg: 315.4 true Computed start 31R: Lat 32.894993 Long -97.000796 Hdg: 135.360 true (MagVar 5.700), CONCRETE, 9004 x 200 ft*** RWS *** KDFW0131 Lat 32.912563 Long -97.021469 Alt 603 Hdg 130 Len 9004 Wid 200*** RWS *** KDFW0312 Lat 32.894993 Long -97.000793 Alt 603 Hdg 310 Len 9004 Wid 200 Runway 13R/31L centre: N32:53:59.9586 W097:04:23.3224 603ft Runway 13R closed for landing Runway 31L closed for landing Start 13R: N32:54:33.4219 W097:04:57.7990 603ft Hdg: 139.1 true Computed start 13R: Lat 32.909645 Long -97.083089 Start 31L: N32:53:26.4628 W097:03:48.8458 603ft Hdg: 319.1 true Computed start 31L: Lat 32.890335 Long -97.063197 Hdg: 139.140 true (MagVar 5.700), CONCRETE, 9307 x 150 ft*** RWS *** KDFW0132 Lat 32.909645 Long -97.083092 Alt 603 Hdg 133 Len 9307 Wid 150*** RWS *** KDFW0311 Lat 32.890335 Long -97.063194 Alt 603 Hdg 313 Len 9307 Wid 150 Runway 14 /32 centre: N32:41:04.6651 W096:26:09.6073 603ft Runway 14 closed for landing and take-off Runway 32 closed for landing and take-off Hdg: 143.260 true (MagVar 5.700), CONCRETE, 1111 x 1 ft Runway 15 /33 centre: N32:35:58.1499 W096:25:46.5552 603ft Runway 15 closed for landing and take-off Runway 33 closed for landing and take-off Hdg: 151.160 true (MagVar 5.700), CONCRETE, 1111 x 1 ft Runway 16 /34 centre: N32:35:44.4147 W096:22:41.9880 603ft Runway 16 closed for landing and take-off Runway 34 closed for landing and take-off Hdg: 159.060 true (MagVar 5.700), CONCRETE, 1111 x 1 ft Runway 1 /19 centre: N32:36:32.2287 W096:25:40.7825 603ft Runway 1 closed for landing and take-off Runway 19 closed for landing and take-off Hdg: 166.960 true (MagVar 5.700), CONCRETE, 1111 x 1 ft Runway 2 /20 centre: N32:35:04.6993 W096:25:23.4968 603ft Runway 2 closed for landing and take-off Runway 20 closed for landing and take-off Hdg: 174.860 true (MagVar 5.700), CONCRETE, 1111 x 1 ft Runway 17L/35R centre: N32:53:11.9826 W097:00:35.4129 603ft Runway 17L closed for take-off Runway 35R closed for take-off Start 17L: N32:53:52.3135 W097:00:35.1875 603ft Hdg: 180.3 true Computed start 17L: Lat 32.898342 Long -97.009769 Start 35R: N32:52:31.6192 W097:00:35.6335 603ft Hdg: 0.3 true Computed start 35R: Lat 32.874981 Long -97.009900 Hdg: 180.270 true (MagVar 5.700), CONCRETE, 8517 x 150 ft*** RWS *** KDFW0171 Lat 32.898342 Long -97.009766 Alt 603 Hdg 175 Len 8517 Wid 150*** RWS *** KDFW0352 Lat 32.874981 Long -97.009903 Alt 603 Hdg 355 Len 8517 Wid 150 Runway 17C/35C centre: N32:53:40.1656 W097:01:33.7509 603ft Start 17C: N32:54:34.8473 W097:01:33.4307 603ft Hdg: 180.3 true Computed start 17C: Lat 32.910160 Long -97.025951 Start 35C: N32:52:45.6136 W097:01:34.0164 603ft Hdg: 0.3 true Computed start 35C: Lat 32.878819 Long -97.026127 Hdg: 180.270 true (MagVar 5.700), CONCRETE, 11427 x 150 ft*** RWS *** KDFW0173 Lat 32.910160 Long -97.025948 Alt 603 Hdg 175 Len 11427 Wid 150*** RWS *** KDFW0353 Lat 32.878819 Long -97.026131 Alt 603 Hdg 355 Len 11427 Wid 150 Runway 17R/35L centre: N32:53:50.2403 W097:01:47.6699 603ft Runway 17R closed for landing Runway 35L closed for landing Start 17R: N32:54:54.8022 W097:01:47.3241 603ft Hdg: 180.3 true Computed start 17R: Lat 32.915703 Long -97.029808 Start 35L: N32:52:45.6784 W097:01:48.0160 603ft Hdg: 0.3 true Computed start 35L: Lat 32.878876 Long -97.030007 Hdg: 180.260 true (MagVar 5.700), CONCRETE, 13427 x 200 ft*** RWS *** KDFW0172 Lat 32.915703 Long -97.029808 Alt 603 Hdg 175 Len 13427 Wid 200*** RWS *** KDFW0351 Lat 32.878876 Long -97.030006 Alt 603 Hdg 355 Len 13427 Wid 200 Runway 18R/36L centre: N32:53:50.5318 W097:03:16.9024 603ft Start 18R: N32:54:35.3656 W097:03:16.6320 603ft Hdg: 180.2 true Computed start 18R: Lat 32.915783 Long -97.054603 Start 36L: N32:52:46.1319 W097:03:17.1710 603ft Hdg: 0.2 true Computed start 36L: Lat 32.878956 Long -97.054787 Hdg: 180.240 true (MagVar 5.700), CONCRETE, 13427 x 150 ft Primary ILS: IVYN 111.90 Secondary ILS: IBXN 111.90*** RWS *** KDFW0182 Lat 32.915783 Long -97.054604 Alt 603 Hdg 175 Len 13427 Wid 150 ILS 111.90*** RWS *** KDFW0361 Lat 32.878956 Long -97.054787 Alt 603 Hdg 355 Len 13427 Wid 150 ILS 111.90 Runway 18L/36R centre: N32:53:50.5966 W097:03:02.7724 603ft Runway 18L closed for landing Runway 36R closed for landing Start 18L: N32:54:55.1585 W097:03:02.4378 603ft Hdg: 180.3 true Computed start 18L: Lat 32.915802 Long -97.050682 Start 36R: N32:52:46.0347 W097:03:03.1071 603ft Hdg: 0.3 true Computed start 36R: Lat 32.878975 Long -97.050865 Hdg: 180.240 true (MagVar 5.700), CONCRETE, 13427 x 200 ft*** RWS *** KDFW0181 Lat 32.915802 Long -97.050682 Alt 603 Hdg 175 Len 13427 Wid 200*** RWS *** KDFW0362 Lat 32.878975 Long -97.050865 Alt 603 Hdg 355 Len 13427 Wid 200and that's what we need to look at. Please place these VTBS sections only in the order they appear in a new file perhaps called mrVTBS.txt, zip, and attach to your reply. The entire runways.txt file even zipped is too large to attach.If you do not find any VTBS sections at all let us know.At the same time, include a note telling us the location of each .bgl file including any AF2 file noting the complete path on your install.I know it is a lot of work to do this but it will help us get to the route of the problem.Thanks for your assistance.

[Subs 0]

Cameron,I was also having this problem with VTBS and have been working with the team to find the solution. I think you'll find the suggestions below will help your situation in the same way. The problem for me was, the entry for VTBS in scenery.cfg was pointing in a slightly different location than what is required.So if your AF2_VTBS.bgl is placed along with all the VTBS scenery bgls: (plse ingnore the dots, I included them to retain formatting)Addon Scenery..........|..........-------VTBS...................|...................-------scenery (AF2_VTBS placed in here)...................|...................-------textureYour path entry in your scenery.cfg should point to:Addon SceneryVTBSIf you point the path incorrectly to Addon SceneryVTBSsceneryit won't work.This change should now allow Makerunways to pick up the airport.Also, just check the line added to f4.csv is;VTBS,Suvarnabhumi,125.70,0,121.65,118.20,0,0,0,0,0,0In jd's earlier post about a similar topic, his suggested line entry may have missed a couple of zeros at the end. With this corrected line above, RC should be able to pick up and use the new VTBS airport :()Let us know how you go,Subs

[Guest doggy769]

hi ron....thanks again so much for helping me try to get to the bottom of this.i have attached the zip you requested.this is the entry i currently have in my scenery.cfg for this VTBSscenery.[Area.136]Title=Bangkok VTBSLocal=Addon SceneryBangkok VTBSRemote=Active=TRUERequired=FALSELayer=136the AFCAD and all other .bgls for this scenery are located incProgram FilesMicrosoft GamesFlight Simulator 9Addon SceneryBangkok VTBSscenery

[Subs 0]

Your runways data in the attached file proves makerunways is picking up the airport for sure. I know you mudt be sick of clicking that Rebuild Database button, but this time delete your r4.csv and a4.csv files in the RCv4data folder. Then Rebuild Database again.Let us know if VTBS is in r4.csv and/or a4.csv now.Thanks,Subs

[Guest doggy769]

hi subs...hav done as u rqstd ....still no luck i'm afraid...VTBS is not in either .csv file......this is very frustrating, but am very appreciative of your continued helpcheers cameron

[John Burgess 0]

Hi there,The file you posted actually contains entries for a file AF2_VTBS.bgl in your Addon SceneryScenery folder.If this file also exists in the Addon SceneryBangkok VTBSscenery folder there should be another entry in the runways.txt file for this.To figure out what is happening we need everything in the runways.txt file which refers to the Addon SceneryBangkok VTBSscenery folder.As a work around for now put the af2 file for this airport in a seperate folder (for example Addon SceneryBangkok VTBS AF2scenery),add this to your scenery library and give it the highest priority. Then rebuild the scenery database. Hopefully that will get you up and running.All the best,John