Hi,For some reason RC would only provide runways 20 and 24 as an option for URSS. 2 and 6 seem to be missing.I did try to regenerate the runway file with the other utility mentioned in another thread - but had similar results.Any suggestions?

if ai are landing and taking off 20 and/or 24, those are the only ones you're going to getif you go into the controller's page, and hit the runway pull down menu, and 2 and 6 there?what happens if you ask ground you'd rather have a different runway, do 2 and 6 show up there?do you have any add-on scenery, which is causing makerwys not to pick up 2 and 6?hard to say what's going on therejd

JD,You're right about AI, they do land and takeoff from Rwy 24 (and go through the mountain as they do so).The controllers page also lists 20 and 24 as the only available options, nor will you get them if you asked for an alternate runway.I do have an addon scenery with a standard AFCAD (no stars for crossing runways) in which 6 and 2 are ticked as "closed for takeoff" (there's a mountain range in front of them, that's why you can't use 20/24 for landing). Beyond that I do not know under what conditions makerwys will fail to pick those up.

A closer look reveales that its most likely an AFCAD issue. FS can't see those ends of the runway either, probably missing "start points".

http://www.vatrus.net.ru/downloads/charts.xhtmlhas a list of charts for Russian airports. URSS is listed.Rwys 2 and six appear to have an ILS or localizer but the default AFCAD does not.In addition FS itself does not recognize runway closures unless both ends are closed. One way stuff doesn't work for AI.As I recall the beta version of makerwys v398 available from the FSUIPC forum and linked here in other posts no longer depends on start locations but it does recognize closures.If you modify your AFCAD RC will follow but not necessarily AI.6 and 2 I believe are for landing and 18 and 24 for takeoff.I can't read the Russian on the plates :)I'm judging by the 25 mile MSA as shown on the plate.See if you can get anything out of these charts. If you change anything run the database builder especially after installing makerwys v398.

Hi Ron,Your observations are absolutely correct, I'm just not sure as to what you mean in "one way stuff".I have solved the problem, at least as far as recognizing those runways by adding start points for Rwy 2 and 6. There's a similar problem with LLBG actually. in that particular airport runways 26 and 30 are used for takeoff and 12 for landing. All parking spots are stacked along rwy 12-30, so there's no way to ask AI to take the longer taxi route over to 26.For URSS landing on 20/24 and T/O from 2/6 are virtually impossible due to the topography, unless you insist on going right through the "wall" of mountains - as AI the airplanes do :)

According to the folks at Project AI, FS must have equal properties for take-off, landing, or closed privilege properties for the each end of the runway. Closing a runway at one end will not affect AI.As for RC recognizing runways without start locations, make a safe copy of makerwys.exe (you can just rename it) in your FS9 root folder and install from this beta copy link:http://fsuipc.simflight.com/beta/MakeRunways_Beta_398.zipOur beta group has not experienced any problem with this version to my knowledge.See if that cures this problem if you wish to ignore the presence of start locations.History:Makerwys originally required start locations so as not to include the phantom star runway placement used with AFCAD to make non-parallel runways active. This created a problem with certain scenery layers (search on KPDX and KPVD here) that ran at higher priority that did not include start locations. In this beta version the requirement was eliminated and other properties such as minimum length were used. It was a complex mix with contributions to the algorithm by quite a few of the beta-tester testers here and by the developer, Pete Dowson, who maintains FSUIPC. I don't recall the final mix in the algorithm but it seems to work pretty well.The beta puts out other data to be used in version 5 but this has not caused any problems with version 4 compatibility.With this beta you can choose not to use the start locations at one end to restrict AI as some developers do. The beta will not include runway ends marked as closed for landing, however, as it should, if I recall correctly so check each end accordingly.

Hi ron,This is actually the "other utility" I was refering to in my first post, so I did regenerate the files with it prior to posting here.It did not pick those runways! not until I have inserted starting points anyway.From your post I understand this particular version should have - right? I can post you my original AFCAD file if you are interested (I just don't know how to add attachments on this forum).My problem has already been solved partially. I do get all runways appearing both in FS and RC. Making AI (or FS ATC) choose one side (be it of two different runways) for takeoffs and the other for landings - This if I understand you correctly , is impossible.

I assume you generated the new files using the Rebuild Scenery DB command in RC after installing the beta makerwys.exe in the FS9 folder. This is the only way some of the data files will be copied to and others created in the RC4data folder.To attach a file here first convert it to .zip format for best transmission.At the bottom of the reply window click on Click Here To Choose Your Attachments. Select the type as .zip. Click the browse button to select your folder and file where the .zip is stored. Click on upload file.A zipped AFCAD .bgl should fit within the 150K limit.In the meantime I'll get the current summary of what we use as the runway inclusion/exclusion properties. It will take me a couple of days for this because of my work schedule temporarily changing daily and the time delay for communication among those involved. I'll post the request on our beta conference.Regarding AI respecting one-way runway use is best looked at in the AFCAD forum at Project AI. If I'm incorrect I apologize but I've seen this issue posted on other forums. The poster usually is rfields with the answer.

Thanks for your kind assistance Ron!Here's the original AFCAD:http://forums.avsim.net/user_files/171384.zipI'll try snooping around the AFCAD forums, although I've seen nothing to contrast what you've said so far.//Michael

I do not know what happened but the attached file was corrupt (I tried twice) and Winzip would not open it. It was 4K in size, rather small for a zipped .bgl file. Be sure you test the zip before attaching and that when browsing to your .zip file make sure the file name is in the window of the attachment form and then you classify it in the checkboxes below the name as type .zip.

Oh,I use winrar for zipping files, so maybe try to rename it, if winzip can open rar files.I guess marking the attachment as a zip file automatically assigns it the suffix - zip.//Michael

OK. I installed it and took a quick look, will get it more detailed tonight and then I'll do a scenery rebuild db in RC.Can you tell me why there are a number of start locations coinciding with the gates? Is this for dynamic ground scenery for AI vehicles or ground traffic?I took a quick look at the runway properties as well.

I don't know Ron.Truth be told, I only noticed them yesterday when I checked the integrity of that zip file. There's nothing about the scenery that would warrant them but they don't seem to make any difference.I did my rebuild not through RC but by directly running the executable from FSs root, don't think that should matter either.

You _MUST_ run the Scenery Rebuild through RC4. It executes a batch file that will call makerwys. When makerwys finished he batch file will then copy some of the files it produces to the rcv4 data folder such as r4.csv. It also creates a4.csv (airport location and characteristics) files from the r4.csv and other items RC 4 uses.http://forums.avsim.net/user_files/171425.zipcontains an extract (in .pdf format) of the r4.csv file in rcv4data of the information lines for URSS. I used the AF2 file you supplied with the v398 of makerwys.exe. Note that all four runways are listed (ignore the trailing 0 in the first column after the ICAO airport code), that is runways 2, 6, 20, 24.When RC runs, it reads only the data in its data folder under the folder you installed RC in. Running the makerwys.exe in the FS9 folder will NOT update data nor create needed data in the data folder under the RC folder where it is installed. That is why your data did not update when you placed the new makerwys in the FS9 folder.When you run the Scenery Database Rebuild from RC you will get several dialog windows appearing waiting for you to OK them and each one will denote the starting and completing of each step including building and copying the files to RC4's data folder.Run the Scenery Rebuild from RC4 and all should be well.*****Never use a spreadsheet program to look at the .csv files yourself unless you copy them leaving the originals intact to a temporary folder and inspect them there. ********