Getting new tower frequency into RC from an airport changed using Airport Design Editor

[nrcapes 0]

I want to add a Tower frequency to an airport that did not have a Tower when FSX was frozen. I recompiled the scenery file for airport KEAU using Airport Design Editor to add a frequency for Tower, to \addonscenery\scenery\keau_adex\nrc.bgl. FSX shows the new frequency in Map when i restart FSX. I rebuilt the scenery database in RC. However when I load a flight plan into RC with that airport as the destination,the Tower frequency is not shown under Controller Info. I can add this at the Controller Info screen, but I would rather have RC pick up this info from FSX. This is a Wideclient configuration with both FSX and the flight plans on the server. Should RC be picking up this information?

[Ray Proudfoot 9,115]

Frequencies are stored in f4.csv in the data folder and are not read from your BGLs.

 

You will need to edit that file - always use Notepad - and add the Tower frequency in the correct position.

 

I can't find the sequence but if you know a Tower frequency for a known airport search for that in f4.csv and then enter the one for KEAU in the same position replacing the 0 that will currently exist.

[Pete Dowson 558]

Frequencies are stored in f4.csv in the data folder and are not read from your BGLs.

 

You will need to edit that file - always use Notepad - and add the Tower frequency in the correct position.

 

MakeRunways does actually extract them from the BGL's and puts every frequency into a file called "f5.csv". This was for use by RC version 5. I did ask JD if he wanted auto-generation for RC version 4 too, but he declined saying the version 5 format was superior. It probably wouldn't be hard to add but I'd need more information on the format. If you look at f5.csv it is very different!

 

Regards

Pete

[nrcapes 0]

MakeRunways does actually extract them from the BGL's and puts every frequency into a file called "f5.csv". This was for use by RC version 5. I did ask JD if he wanted auto-generation for RC version 4 too, but he declined saying the version 5 format was superior. It probably wouldn't be hard to add but I'd need more information on the format. If you look at f5.csv it is very different!

 

 

 

Regards

Pete

 

Regarding this and the previous post, there is no f4.csv file in the FSX folder (and no "data" folder). Should there be? There IS an f5.csv file, but how do I get RC to read it?

 

Thanks!

[Ray Proudfoot 9,115]

The f4.csv file is in your Radar Contact data subfolder. If you don't have that one then edit the f5.csv instead. It should be identical to the one in the FSX folder.

 

RC can only read the files in RC4\data folder.

[nrcapes 0]

The f4.csv file is in your Radar Contact data subfolder. If you don't have that one then edit the f5.csv instead. It should be identical to the one in the FSX folder.

 

RC can only read the files in RC4\data folder.

 

Thanks! Actually it is in the RCV4\data folder in Win7, but in RCV4x\data in WinXP. Changing the frequency worked!

[Ray Proudfoot 9,115]

Excellent! The RC parent folder name will vary according to whether you have FS9, FSX or both installed.

[ronzie 21]

And a caution:

When editing f4.csv always make a backup copy somewhere. The format is strict and no extra spaces, etc, must be added. If not strictly followed it will be corrupt and RC will fail at some point. If you don't make a safe copy an RC reinstall will be required.

 

Never use Excel or other spreadsheet or database application to edit .csv files and always keep copies of working backups. Always save in msdos text format insuring that the file name retains just the .csv extension.

 

RC4 only uses runway data produced by makerwys to after processing create r4,csv and a4.csv in its data folder. These are the only csv files automatically updated.

 

Congratulations on a successful modification retaining the exact csv format.

[nrcapes 0]

And a caution:

When editing f4.csv always make a backup copy somewhere. The format is strict and no extra spaces, etc, must be added. If not strictly followed it will be corrupt and RC will fail at some point. If you don't make a safe copy an RC reinstall will be required.

 

Never use Excel or other spreadsheet or database application to edit .csv files and always keep copies of working backups. Always save in msdos text format insuring that the file name retains just the .csv extension.

 

RC4 only uses runway data produced by makerwys to after processing create r4,csv and a4.csv in its data folder. These are the only csv files automatically updated.

 

Congratulations on a successful modification retaining the exact csv format.

 

Thanks! This is one reason I always change critical components on my client pc where RC runs, not on the server where FSX runs. If I have to do a re-install, I'd rather do it on the client. BTW, congrats to Pete for his makerwys software.

 

Do I understand the following correctly: ADE creates a .BGL file for an airport; makerwys extracts data from the BGL file to create the f4.csv file, which RC then uses for frequencies. If I make a change to an airport frequency using ADE, that change will propagate to RC via makerwys and overwrite the change I made to f4.csv. Correct?

[ronzie 21]

Do I understand the following correctly: ADE creates a .BGL file for an airport; makerwys extracts data from the BGL file to create the f4.csv file, which RC then uses for frequencies. If I make a change to an airport frequency using ADE, that change will propagate to RC via makerwys and overwrite the change I made to f4.csv. Correct?

 

No, this is not correct for version 4. The comm frequencies are a fixed database and not extracted for use in version 4. You can make changes on a per session use in the RC Controller tab but those are not saved between sessions.

 

The only data updated by RC4 is pulled from the r5.csv runway data file (copied as r4.csv to the RCv4 data folder) during a scenery rebuild and then a4.csv is derived from that. f4.csv must be manually changed for permanent comm assignments by very careful manual editing.

 

f5.csv created by makerwys is for possible future use in RCv5. See the pinned topic on RCv5 development status.

 

In RCv4 it is best to let RC auto-tune the comm radios or let the co-pilot run comms (which has some disadvantages) which will use the f4.csv values or your temporary controller panel assignments.

[Pete Dowson 558]

No, this is not correct for version 4. The comm frequencies are a fixed database and not extracted for use in version 4.

 

Sorry, I added confusion by introducing the f5.csv file, which MakeRunways does produce. but that was in preparation for the maybe-coming V5. Having done all the work to make the f5.csv file for version 5, it would be easy enough to do the f4.csv file as well, but JD said it wasn't worth it back then because of the change to V5 ... Duh!

 

If someone knows the exact format of f4.csv (i.e. which goes where), and can relate the different frequency types to the number codes used in f5.csv, maybe I can generate the f4.csv file as well. After all we have at least another year to wait till we even know if there will be a use for f5.csv! Seems a bit of a waste.

 

Regards

Pete

[nrcapes 0]

No, this is not correct for version 4. The comm frequencies are a fixed database and not extracted for use in version 4. You can make changes on a per session use in the RC Controller tab but those are not saved between sessions.

Where does the fixed database come from? If I add a frequency using ADE and compile a BGL to \scenery\addonscenery and run FSX, does this build f4.csv?

In RCv4 it is best to let RC auto-tune the comm radios or let the co-pilot run comms (which has some disadvantages) which will use the f4.csv values or your temporary controller panel assignments.

Well, yes, but I have the Saitek radio panel and I try to make things as realistic as possible by tuning the radios myself.

[ronzie 21]

Here's the quandary:

 

There is no guarantee that FS scenery comm data matches current charts. What you can do is print-screen the RC controller page for a guide of the airport bound frequencies. For center that is a different complex issue as there is much variation in the real world in dealing with FIR jurisdictions at times frequencies are used.

 

Now the RC controllers announce the frequencies you are to use. You can manually tune the radio before acking the command and then separately do the contact. The print screen of the controller page will let you set up the standby frequencies in the airport areas ready to switch.

 

New airports can be manually added to the f4.csv file as noted in previous posts. Back up this file carefully as previously noted.

 

There are a couple of discrepancies I've noted regarding swapped ground and departure frequencies in stock airports but this is what appears to work somewhat in my experience - not guaranteeing accuracy:

 

 

 

for comparison.

 

I know that Unicom does not show in the RC controller tab.

If you insert a new airport place it in ICAO alphabetical order following the example for commas and spacing exactly.

 

This information is from my own deduction for those who wish to attempt to adjust f4.csv. This does not come from jd.

 

I do not know who furnished the database back in the days of RC3 and 4's development around 2002. Back then some of these databases were offered some at no charge and some payware offered by various sources. One specialist was Richard Stefan, now with Navigraph.com. Others, like Pete, may have extracted data from stock scenery from FS7 or so. I don't really know.

 

Now to be clear - I only am offering the suggestion and can not take any responsibility for file corruptions. I've helped some users here with restoring kai-tak frequency data among others - search for that.

[ronzie 21]

Just a note to add that the unknown field in f4.csv appears to be MULTICOM\CTAF. This is not used in the current RC version.

 

In periods when there is no operation of a tower or no tower it used to be UNICOM that pilots reported their local intentions and positions at for local traffic when approach and flying the various legs of the pattern. UNICOM is also used as a frequency for an FBO (Fixed Base Operator) for convenience communications such as asking to have a cab called to meet the aircraft at the estimated arrival time while still far enough out. For people meeting the aircraft and waiting at the FBO office or reception area it is used to notify those people of impending arrival. It also is used for other items such as advance requesting of fuel or other services when in UNICOM range. In some places, particularly outlying airports, it can be used for contacting an airport manager or even small airline operations agent.

 

Now MULTICOM or CTAF (Common Traffic Advisory Frequency) is used for pilot initiated position reporting and intentions (Anoka Traffic Cherokee 180 right downwind runway 36 full stop landing, Anoka Traffic Cherokee 180 take-off runway 36 north departure - or left traffic west departure, etc.). Usually MULTICOM is designated for non towered airports typically 122.9. CTAF is used for part-time towered airports and may use the tower frequency during closed tower operating periods.

 

RC4 is not supporting Unicom, Multicom, and CTAF airport comm simulation for position and status reporting so those fields can be left blank. In the f4 format pdf I attached the ? for the unknown field is where some f4 entries have the Multicom\CTAF entry. Where the field has a part-time tower the tower frequency and MULTICOM\CTAF field may be the same.

[ronzie 21]

http://forum.avsim.net/topic/380869-new-optional-comm-frequency-f4csv-scenery-extraction-for-airports/

 

This additional external procedure in updating RC's scenery database should help. It creates an f4.csv file to be copied to the RC data folder.