Good day

 

For the last 10 flights I've never gotten any vector again by RC4 and every time I captured the ILS, I got told "radar services terminated" and my copilot (from MultiCrewExperience) was no longer able to communicate with the ATC. This is getting quite annoying...

No matter the size of the airport, I always ended up having to fly the full transition even though the airports feature full ILS

A few examples: EDDH, EDDG, EPBY, EDNY, EDDK, LBSF, LHBP

Is there any option I can enable to always get vectors to the ILS, since I bought RC4toXP mainly to get vectors while flying offline, please? Now I have to follow the full transition every time

The problem usually started with "do you have the latest weather and what approach do you request" I always replied with affirmative (since i use ASXP weather) and selected IAP ILS and then the runway.

 

Thanks in advance 

Alex, you’re using RC4 with X-Plane I believe. I’ve never flown XP. The “do you have the latest weather and what approach do you request" when flying P3D happens when the airport has no Approach frequency.

Can you provide a screenshot of the main RC interface after a plan is loaded and before you press OK.

The other question is what has changed since things worked correctly? Scenery Rebuild done?

 

1 hour ago, Ray Proudfoot said:

Alex, you’re using RC4 with X-Plane I believe. I’ve never flown XP. The “do you have the latest weather and what approach do you request" when flying P3D happens when the airport has no Approach frequency.

Can you provide a screenshot of the main RC interface after a plan is loaded and before you press OK.

The other question is what has changed since things worked correctly? Scenery Rebuild done?

 

Now as you mention, I remember that I never was sent to approach again.

The only thing that has been changed is the new airac cycle by Navigraph but as far as I know, RC4 does not use any airac, does it?

Here are the screenshots, I have just noticed that there aren't any frequencies ticked for departure and approach, usually those were ticket automatically. I never use control info, I usually open it for Notams only. This could be the cause of the issue but why has this setting even changed itself?

 

 

Cheers Alex

 

Hi Alex,

As I suspected the lack of Approach frequency is why you can’t be handed over for vectors to an ILS intercept.

I don’t have my RC PC on at present but from memory the frequencies are held in f5.csv. See if the contents of that file have changed. It doesn’t get updated by Navigraph for P3D and I imagine the same is true for XP. Always open it with Notepad+, never Excel.

Look in f5.csv for EGCC which does have an Approach frequency. Then check your other troublesome airports for one.

I’ll check my files tomorrow and get back to you. I’ll also check if I have IFR TRAINING set to ON.

Thanks, I'll check it out

The f4.csv file is the one RC4 uses for facility frequencies--f5.csv is the freq data in a different format intended for a version of RC that was never released.  The file is created by MakeRwys for the ESP platforms, but MakeRwys for XPlane does not generate the f4.csv file.  I use the f4.csv file transplanted from my P3D configuration, which is more complete than the old version included with RC4.

The default EDDG airfield in RC4 does not have an approach or departure control frequency listed in the f4.csv file. 

If you want vectors at any airport where the freqs are missing from the freq database, you'll need to manually edit the f4.csv file in your RC4 data folder. 

For example, the default line for EDDG in my f4.csv file is:

  EDDG,Munster-Osnabruck,127.17,0,121.87,129,80,0,0,0,0

to add the published approach and departure control freqs, I replace the last two params (zeros in this case) with the approach and dept freqs (129.18,129.30):

  EDDG,Munster-Osnabruck,127.17,0,121.87,129,80,0,0,129.18,129.30

 

 

Thanks for clarifying things Bob. This may be useful for those who want to manually edit their f4.csv. The entries are comma-separated.

• ICAO code
• airport name
• atis frequency
• clearance frequency
• ground frequency
• tower frequency
• unicom frequency
• multicom frequency
• approach frequency
• departure frequency

13 hours ago, Bob Scott said:

The f4.csv file is the one RC4 uses for facility frequencies--f5.csv is the freq data in a different format intended for a version of RC that was never released.  The file is created by MakeRwys for the ESP platforms, but MakeRwys for XPlane does not generate the f4.csv file.  I use the f4.csv file transplanted from my P3D configuration, which is more complete than the old version included with RC4.

The default EDDG airfield in RC4 does not have an approach or departure control frequency listed in the f4.csv file. 

If you want vectors at any airport where the freqs are missing from the freq database, you'll need to manually edit the f4.csv file in your RC4 data folder. 

For example, the default line for EDDG in my f4.csv file is:

  EDDG,Munster-Osnabruck,127.17,0,121.87,129,80,0,0,0,0

to add the published approach and departure control freqs, I replace the last two params (zeros in this case) with the approach and dept freqs (129.18,129.30):

  EDDG,Munster-Osnabruck,127.17,0,121.87,129,80,0,0,129.18,129.30

 

 

Is it possible to download a completed file with every airport added, please? Since you said make runways only generates this file in P3D it would be really helpful, if you could send it to me. 

I only use X Plane

Thanks in advance

Alex, not every airport has departure and approach services. Many smaller ones don’t need such services.

It’s not difficult to edit your f4.csv now that the layout of the file has been described and Bob has supplied those for EDDG.

3 hours ago, Ray Proudfoot said:

Alex, not every airport has departure and approach services. Many smaller ones don’t need such services.

It’s not difficult to edit your f4.csv now that the layout of the file has been described and Bob has supplied those for EDDG.

Yes that might be true, but big airports like EDDK and EDDH should have those which lead back to missing lines in the config file which I would have to add manually and I would be busy for hours adding those manually. That is the reason why I ask him kindly to send me his auto generated config file which I can't create automatically

Edited August 26, 20223 yr by Alex Walker

Apologies for reopening this thread, but could it be an option to simply load a flight, go on "Controller Info" and then check the boxes next to the departure and approach blanks in the column for the arrival airport? If I do so, the blanks automatically fill with frequencies.

Best regards,

shorthauler

 

@EPICfan, I’m not sure what you’re asking. Not all airports have an Approach frequency. Have you run MakeRunways?

Yes, I have. Unfortunately I have not found out yet how to post screenshot. If I open a flightplant from OLBA (Beirut) to OSDI (Damascus), in the OSDI column the frequencies for Departure and Approach are "0". The small square checkboxes left to the fields are unchecked. If I check them I get 122.70 for Departure and 126.95 for Approach. It seems to me that these are virtual frequencies made up by Radar Contact in order to enable vectoring. Is this the case?

 

Best regards

shorthauler

1 hour ago, EPICfan said:

Yes, I have. Unfortunately I have not found out yet how to post screenshot. If I open a flightplant from OLBA (Beirut) to OSDI (Damascus), in the OSDI column the frequencies for Departure and Approach are "0". The small square checkboxes left to the fields are unchecked. If I check them I get 122.70 for Departure and 126.95 for Approach. It seems to me that these are virtual frequencies made up by Radar Contact in order to enable vectoring. Is this the case?

 

Best regards

shorthauler

I've just created a quick flight plan and can confirm OSDI has no approach frequencies. Clicking the checkbox fills them with some but mine are different to yours. Probpably random as you suggest.

I've never used that feature. Instead if I fly to an airport without APP support I leave RC4 to give me suitable options. It probably is to gain approach vectors. The alternative is to fly your own approach by choosing the option at 40nm out when that decision needs making.