Hi,

 

I am using FS9.1, Aerosoft Scenery EDLV,

 

after installing the scenery I run the "Rebuild Database" and added EDLV (EDLV,Niederrhein,124.45,0,129.4,129.4,0,0,130.8,0) to f4.csv, when I realised that RC is unable to identify the airport.

EDLV is present in a4.csv and r4.csv.

ETUL still is present in f4.csv, but not in a4.csv and ra.csv.

 

When I load a flightplan with destination EDLV, the arrival under "Controller Info" is empty, frequencies are set to zero. Above it says f.i. EGSS to ETUL EGSS, ETUL

 

EDLV is the former ETUL, Laarbach AB (stock FS9 Airport) and the ILS RWY27 is still named "Laarbach" in AFCAD which comes with the scenery.

 

How can I get RC to cooperate with this scenery?

 

Thanks in advance for any help.

 

Christian

do you have the latest version of makerwys.exe installed in the root directory of fs9? if not, go get it, link is pinned at the top of the forum. install it. click rebuild scenery database.

Thank You for Your response!

I am rebuilding the database with the latest version of makerwys.exe installed.

 

Supplementary investigations have shown that I think my problem has to do with the AFCAD of that scenery.

 

Using good old FSNav, I detected that the ILS RWY27 is linked to "Laarbruch" ETUL, the FS9 stock airfield, which changed in 2003 to EDLV, while ILS/BC RWY 09 is named "Niederrhein", which is EDLV. When I plan a flight with Runway 09, everything is fine and RC is able to identify the airport. It´s only RW 27, which causes the problem. It´s the same with FSNav, it identifies Rwy27 with ETUL, Rwy09 with EDLV. So I guess it´s not RCs fault.

 

So the question is, how to link ILS RW27 to EDLV too.

 

Have a nice weekend

Hans-Christian

Before anything please make safe copies of the following files in a safety folder outside of RC:

In your rcv4 folder copy rcv3.dat and keyboard.dat. In RCv4\data copy f4.csv and m5.csv to this backup folder. Having safe copies especiaslly of rcv3.dat and keyboard.dat can avoid a reinstallation as well as f4.csv and m4.csv.

 

First is the comms problem to take care of:

 

In versions of makerwys from 4.612 or later it creates an f4.csv in your FS9 folder which is data extracted from your scenery. You should find a line in that f4.csv for EDLV. RC4 as current does not make use of this file so you can add that EDLV line to the f4.csv file in RCv4\data in alphabetical order. The f4.csv file supplied by RC is a fixed database not updated in the scenery update within RC's data folder so that should be done.

 

Here's the existing ETUL line in f4.csv:

 

ETUL,Laarbruch AB,0,0,122.10,122.10,0,0,119.70,130.50

 

Since I don't have that Aerosoft scenery I'll just duplicate that line inserted into the correct place in f4.csv:

 

EDLS,Vreden,0,0,0,0,0,0,0,0

EDLT,Munster-Telgte,0,0,0,0,0,0,0,0

EDLV,Laarbruch AB,0,0,122.10,122.10,0,0,119.70,130.50

EDLW,Dortmund,125.12,0,121.82,134.17,0,0,0,0

EDLX,Romerwardt,0,0,0,0,0,0,0,0

 

or use the line copied from f4.csv in your FS9 folder as extracted by makerwys from Aerosoft's scenery

 

It is important that all .csv files be edited with a text editor such as notepad or wordpad in msdos .txt mode. Exact format must be followed regarding commas and space characters or f4.csv will not be valid and in some cases corrupt some .dat files requiring reinstallation of RC.

 

EDLV needs to be added to the m4.csv file. Just copy the ETUL line to an inserted line in alphabetical order with the new ICAO. This file deals the MSA calculation that RC uses for your approach altitudes in the airport pattern and also defines the transition altitude.

 

Here's the ETUL line to copy:

ETUL,246,5000

 

Here's the m4.csv section modified:

 

EDLS,419,5000

EDLT,423,5000

EDLV,246,5000

EDLW,1377,5000

EDLX,410,5000

 

As far as RC the ILS frequencies used by Aerosoft will be in the r5.csv file copied as r4.csv to RC's data folder. That just tells RC a localizer is present and if it has a glideslope for an ILS approach. I don't recall if RC4 displays that frequency. It does in later versions.

 

I never used FS Nav. I don't know if it pulled data from your installed scenery. There is a scenery design limitation in FS9 in that you can not delete an ILS from stock scenery. You can do some things with it, though.

 

Specific to ETUL default airport has no localizers nor ILS approaches. Therefore the limitations for basing a new airport with changed ILS data does not apply. Current charts show LOC and ILS as INIW on 110.70 for Rwy 27. Runway 9 has no precision (LOC\ILS) approach but uses NDB. The Rwy 27 chart does not show a circling minimum altitude. Eurocontrol is my source for these charts and they have published any changes up to 2011. Niederhein is the name of the NDB for the IAF and also the DME source.

 

So Aerosoft should not have had any problem adding the ILS.

 

In FS9 I don't think you can delete a default airport but you can create a new one overlaying it with a new ICAO. You can delete runways and other data though with an exclude. This exclude will not delete the old ILS.

 

So FS NAV might trip up on this but the ILS which is new should be identified with EDLV.

 

Certainly RC should have the frequencies after your modification.

 

Is FS NAV the same as FS Navigator? If so updates are available for version 4 from navigraph.com and perhaps the new Aerosoft AIRAC update product. Navigraph for that does not support terminal procedures however.

 

The EDLV STAR shows all approaches from the NE or SE with NDB LAA as the IAF.

 

If you examine or want to modify Aerosoft's afd type file for EDLV, I recommend you use the safer free Airport Design Editor, not AFCAD221 which was designed before MS released the FS9 software development kit so a few

errors are in it.

 

http://www.airportdesigneditor.co.uk/

 

In the meantime here's an FS9 plan usuing STAR LMA1W from the SE:

[flightplan]

title=EGSS to EDLV

description=EGSS, EDLV

type=IFR

routetype=3

cruising_altitude=31000

departure_id=EGSS, N51* 53.05', E000* 14.05',+000348.00

departure_position=09

destination_id=EDLV, N51* 36.08', E006* 08.31',+000106.00

departure_name=LONDON_STANSTED

destination_name=NIEDERRHEIN

waypoint.0=EGSS, A, N51* 53.05', E000* 14.05', +000000.00,

waypoint.1=BRAIN, I, N51* 48.39', E000* 39.06', +000000.00, UM185

waypoint.2=DAGGA, I, N51* 49.19', E000* 47.39', +000000.00, UM185

waypoint.3=CLN, V, N51* 50.54', E001* 08.50', +000000.00, UL608

waypoint.4=LOGAN, I, N51* 44.51', E001* 36.43', +000000.00, UL980

waypoint.5=XAMAN, I, N51* 47.04', E002* 13.27', +000000.00, UL980

waypoint.6=REFSO, I, N51* 48.34', E002* 40.00', +000000.00, UL980

waypoint.7=GORLO, I, N51* 55.26', E003* 10.18', +000000.00, UZ301

waypoint.8=XULET, I, N51* 37.19', E006* 05.53', +000000.00,

waypoint.9=LMA, N, N51* 22.15', E006* 23.41', +000000.00,

waypoint.10=LAA, N, N51* 36.06', E006* 10.21', +000000.00,

waypoint.11=EDLV, A, N51* 36.08', E006* 08.31', +000000.00,

 

or

 

SOBTU 1W from the NE:

 

[flightplan]

title=EGSS to EDLV

description=EGSS, EDLV

type=IFR

routetype=3

cruising_altitude=31000

departure_id=EGSS, N51* 53.05', E000* 14.05',+000348.00

departure_position=09

destination_id=EDLV, N51* 36.08', E006* 08.31',+000106.00

departure_name=LONDON_STANSTED

destination_name=NIEDERRHEIN

waypoint.0=EGSS, A, N51* 53.05', E000* 14.05', +000000.00,

waypoint.1=BRAIN, I, N51* 48.39', E000* 39.06', +000000.00, UM185

waypoint.2=DAGGA, I, N51* 49.19', E000* 47.39', +000000.00, UM185

waypoint.3=CLN, V, N51* 50.54', E001* 08.50', +000000.00, UL608

waypoint.4=LOGAN, I, N51* 44.51', E001* 36.43', +000000.00, UL980

waypoint.5=XAMAN, I, N51* 47.04', E002* 13.27', +000000.00, UL980

waypoint.6=REFSO, I, N51* 48.34', E002* 40.00', +000000.00, UL980

waypoint.7=GORLO, I, N51* 55.26', E003* 10.18', +000000.00, UZ301

waypoint.8=XULET, I, N51* 37.19', E006* 05.53', +000000.00,

waypoint.9=SOBTU, I, N51* 41.52', E006* 32.52', +000000.00,

waypoint.10=LAA, N, N51* 36.06', E006* 10.21', +000000.00,

waypoint.11=EDLV, A, N51* 36.08', E006* 08.31', +000000.00,

 

These were generated in Auto mode by FSBuild but I did not specify a departure SID for Stansted. FS Build 2.4 uses AIRACs.

 

Your destination naming confusion has to do with the military ETxx to civilian EDxx German ICAO types.

 

Hi Ronzie,

 

thank You very, very much for Your detailed and easy to follow explanation! Thank You for taking that time to help me!

 

I followed Your instructions step by step (and learned a lot about RC4) and a first flight ended successful.

 

RC4 is able to find EDLV, to read elevation and transition altitude data, comm- and navfrequencies. - As long as I don´t use FsNavigator (FSNav) combined with Runway 27 (Runway 09 works) for exporting a FS9 flightplan. Therefore I will use FSBuild.

 

My best wishes,

thank You once again,

Hans-Christian