Jump to content

Recommended Posts

Posted

Hi

Just made a flight in the Southwest of the map, and none of the ILS had a glide slope. Tested with Mirage F1, M2000 and F-16 to be sure.

Tested on Spangdahlem, Ramstein, Zweibrücken, Frankfurt.

Posted

In fact, I just took a look at Spangdahlem and found 3 Localiser , one called 'SPA' 109.9 direction -75.032 , 'ISPA' 108.1 direction 55.64  and 'ISPE' 109.15 direction -124.38. 2 Glideslope: 'ISPA' 108.1 direction 143.55 'ISPE' 109.15 direction -35.75. If I compare with Batumi, Localiser and Glideslope have the same direction. That explains why they're not working. 

Posted

Interesting grim_reaper68 might explain why you get a momentary GS alive as you pass abeam the GS antenna on landing.

Posted

In fact, I noticed that too. While flying next to the runway, the GS reacted for a couple of seconds. I managed to make Spangdahlem work by pasting the same direction as those from the LOC on the GS.

  

  • 2 weeks later...
Posted (edited)

Tested Ramstein, it works.

ro3xOVA.jpg

Edited by YoYo

Webmaster of http://www.yoyosims.pl

Yoyosimsbanner.gif

Win 10 64, i9-13900 KF, RTX  4090 24Gb OC, RAM 64Gb Corsair Vengeance LED OC@3600MHz,, 3xSSD+3xSSD M.2 NVMe, Predator XB271HU res.2560x1440 27'' G-sync, Sound Blaster Z + 5.1, TiR5, [MSFS, P3Dv5, DCS, RoF, Condor2, IL-2 CoD/BoX] VR fly only: Meta Quest Pro

Posted

What I noticed is that the descriptions are mixed up. An example from Rammstein:

Yd5Azyc.jpg

111.5 for 277 runway, but it isnt true:

Rv3sNfA.jpg

111.5 is for 95, for 277 runway is 111.75. 

Perhaps there are similar errors in the description at other airports.

  • Like 2

Webmaster of http://www.yoyosims.pl

Yoyosimsbanner.gif

Win 10 64, i9-13900 KF, RTX  4090 24Gb OC, RAM 64Gb Corsair Vengeance LED OC@3600MHz,, 3xSSD+3xSSD M.2 NVMe, Predator XB271HU res.2560x1440 27'' G-sync, Sound Blaster Z + 5.1, TiR5, [MSFS, P3Dv5, DCS, RoF, Condor2, IL-2 CoD/BoX] VR fly only: Meta Quest Pro

Posted (edited)

In fact IREL (111.50) is on the runway 9, and i found another error in the rwy 27 as the ILS should be called IRWR (110.75) and not OGNID who seems to be a marker. Do you know where to find the descrition file? Or maybe it's encrypted. 

@YoYo did you test it on runway 9 (111.50) on my side i had the localiser who didn't work. runway 27 is ok.

 

Edited by grim_reaper68
Posted

Finally I managed to make Ramstein ILS work correctly. And to have the correct information.

DCS World MT_2025.05.04-11.11_1.png

I just changed the order in the lua file to have this, I grouped both LOC and Glideslope together 

{
        display_name = _('Ramstein');
        beaconId = 'airfield165_0';
        type = BEACON_TYPE_ILS_LOCALIZER;
        callsign = 'IRWR';
        frequency = 110750000.000000;
        position = { -498508.187500, 245.303041, -936275.500000 };
        direction = 96.579995;
        positionGeo = { latitude = 49.435961, longitude = 7.577700 };
        sceneObjects = {'t:67627740'};
        chartOffsetX = 3104.000000;
    };
    {
        display_name = _('Ramstein');
        beaconId = 'airfield165_1';
        type = BEACON_TYPE_ILS_GLIDESLOPE;
        callsign = 'IRWR';
        frequency = 110750000.000000;
        position = { -498729.625000, 245.303041, -933698.187500 };
        direction = 97.482673;
        positionGeo = { latitude = 49.438106, longitude = 7.612817 };
        sceneObjects = {'t:187581164'};
    };
    {
        display_name = _('Ramstein');
        beaconId = 'airfield165_2';
        type = BEACON_TYPE_ILS_LOCALIZER;
        callsign = 'IREL';
        frequency = 111500000.000000;
        position = { -498893.093750, 244.777131, -932940.937500 };
        direction = -83.419990;
        positionGeo = { latitude = 49.437874, longitude = 7.623375 };
        sceneObjects = {'t:67634644'};
        chartOffsetX = 3104.000000;
    };
    {
        display_name = _('Ramstein');
        beaconId = 'airfield165_3';
        type = BEACON_TYPE_ILS_GLIDESLOPE;
        callsign = 'IREL';
        frequency = 111500000.000000;
        position = { -498511.750000, 245.303041, -935470.250000 };
        direction = -82.517339;
        positionGeo = { latitude = 49.437206, longitude = 7.588512 };
        sceneObjects = {'t:187573484'};
    };
    {
        display_name = _('Ramstein');
        beaconId = 'airfield165_4';
        type = BEACON_TYPE_TACAN;
        callsign = 'RMS';
        frequency = 0.000000;
        channel = 81;
        position = { -498853.218750, 245.303041, -935310.937500 };
        direction = -173.171209;
        positionGeo = { latitude = 49.434471, longitude = 7.591479 };
        sceneObjects = {'t:67626958'};

 

  • 2 weeks later...
Posted

Hi

If you haven't done it yet, you can find my work here, any feedback of lack or mistakes welcome. For complete ILS frequencies, a look on the Beacon information in the Mission Editor, will give you all frequencies, as on airfields with 2 runways, only the marked one (blue circle with white bar) ILS frequencies will appear on the F10 map.

Don't forget to backup your original file, if you want to try it. 

 

  • Thanks 1

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...