grim_reaper68

In fact as told, lua file is correct, all objects positions and directions are correct, but they are displayed inverted in the mission editor, but shown correctly in the F10 map information window. You tell me that you haven't inverted localiser on runway 25R, that's strange, as I have them on both end, despite using the default lua file. Maybe you can put the airfield163 complete part of the file in the post, so I can run tests. Because I'm pretty sure that I backed it up before starting working on it, but just to be sure. Here is my part of the Beacons.lua of Frankfurt, I added some comment to make it easier to identify while working, as they're not following. You can try just to change the BeaconId like I've done, and the second runway ILS will appear. There are airfield163_3 to airfield163_99, airfield163_4 to airfield163_98, airfield163_9 to airfield163_97 and airfield163_10 to airfield163_96. i'm actually at Hamburg in the file, where I managed to make the runway 15-33 ILS actice with the same method. But as told in another post, DCS isn"t able to manage 2 runways at the same airport. --LOC 07L { display_name = _('Frankfurt'); beaconId = 'airfield163_0'; type = BEACON_TYPE_ILS_LOCALIZER; callsign = 'DLF'; --ILS correction frequency = 109500000.000000; --ILS correction position = { -443583.906250, 100.000100, -851177.812500 }; direction = -100.841391; positionGeo = { latitude = 50.047996, longitude = 8.598907 }; sceneObjects = {'t:75400878'}; chartOffsetX = 4593.000000; }; --GS 25R { display_name = _('Frankfurt'); beaconId = 'airfield163_1'; type = BEACON_TYPE_ILS_GLIDESLOPE; callsign = 'DLF'; frequency = 109500000.000000; position = { -443643.500000, 100.000100, -851917.625000 }; direction = 78.659744; positionGeo = { latitude = 50.046376, longitude = 8.588953 }; sceneObjects = {'t:215803068'}; }; { display_name = _('Frankfurt'); beaconId = 'airfield163_2'; type = BEACON_TYPE_AIRPORT_HOMER; callsign = 'FR'; frequency = 297000.000000; position = { -442648.875000, 128.143317, -844779.937500 }; direction = -101.576053; positionGeo = { latitude = 50.065653, longitude = 8.684068 }; sceneObjects = {'t:75410730'}; }; --GS 25L { display_name = _('Frankfurt'); beaconId = 'airfield163_99'; type = BEACON_TYPE_ILS_GLIDESLOPE; callsign = 'FFM'; frequency = 110700000.000000; position = { -444321.468750, 100.000100, -852673.437500 }; direction = 81.530965; positionGeo = { latitude = 50.039301, longitude = 8.580205 }; sceneObjects = {'t:215794929'}; }; --LOC 07R { display_name = _('Frankfurt'); beaconId = 'airfield163_98'; type = BEACON_TYPE_ILS_LOCALIZER; callsign = 'IRFR'; frequency = 111100000.000000; position = { -444262.406250, 100.000100, -851914.812500 }; direction = -100.825012; positionGeo = { latitude = 50.040944, longitude = 8.590415 }; sceneObjects = {'t:75400879'}; chartOffsetX = 4222.000000; }; { display_name = _('Frankfurt'); beaconId = 'airfield163_5'; type = BEACON_TYPE_AIRPORT_HOMER; callsign = 'FW'; frequency = 382000.000000; position = { -445875.125000, 90.751128, -863257.500000 }; direction = -118.128176; positionGeo = { latitude = 50.009882, longitude = 8.439541 }; sceneObjects = {'t:75377411'}; }; { display_name = _('Frankfurt '); beaconId = 'airfield163_6'; type = BEACON_TYPE_TACAN; callsign = 'FFM'; frequency = 114200000.000000; channel = 89; position = { -443403.843750, 118.535061, -848339.000000 }; direction = -12.414081; positionGeo = { latitude = 50.053775, longitude = 8.637223 }; sceneObjects = {'t:215810048'}; }; --GS 07L { display_name = _('Frankfurt'); beaconId = 'airfield163_7'; type = BEACON_TYPE_ILS_GLIDESLOPE; callsign = 'RHM'; frequency = 110100000.000000; position = { -444432.531250, 100.000100, -855199.875000 }; direction = -97.789724; positionGeo = { latitude = 50.034575, longitude = 8.546010 }; sceneObjects = {'t:214647238'}; }; --LOC 25R { display_name = _('Frankfurt'); beaconId = 'airfield163_8'; type = BEACON_TYPE_ILS_LOCALIZER; callsign = 'RHM'; frequency = 110100000.000000; position = { -444506.750000, 100.000100, -855987.625000 }; direction = 79.143587; positionGeo = { latitude = 50.032752, longitude = 8.535441 }; sceneObjects = {'t:75394723'}; chartOffsetX = 4591.000000; }; --LOC 25L { display_name = _('Frankfurt'); beaconId = 'airfield163_97'; type = BEACON_TYPE_ILS_LOCALIZER; callsign = 'FFM'; frequency = 110700000.000000; position = { -445112.812500, 100.000100, -856363.250000 }; direction = 79.197225; positionGeo = { latitude = 50.026870, longitude = 8.531721 }; sceneObjects = {'t:75383580'}; chartOffsetX = 4222.000000; }; --GS 07R { display_name = _('Frankfurt'); beaconId = 'airfield163_96'; type = BEACON_TYPE_ILS_GLIDESLOPE; callsign = 'IRFR'; frequency = 111100000.000000; position = { -445032.750000, 100.000100, -855591.500000 }; direction = -99.485803; positionGeo = { latitude = 50.028721, longitude = 8.542056 }; sceneObjects = {'t:214647239'}; }; { display_name = _('Frankfurt'); beaconId = 'airfield163_11'; type = BEACON_TYPE_AIRPORT_HOMER; callsign = 'FFM'; frequency = 320000.000000; position = { -443411.906250, 118.986508, -847382.500000 }; direction = -101.576053; positionGeo = { latitude = 50.055115, longitude = 8.650293 }; sceneObjects = {'t:75410731'}; };

Hi First of all, thanks for the update! I saw that Tempelhof's runway has switched, Could you do the same for Schonefeld?

Hi While working on the Beacons.lua file, I was surprised that the ILS frequencies displayed in the mission editor were inverted compared to the information window while flying, as you can see on the screens. I tested it with the original Beacons.lua file, and had the same issue after I used the modified file. So don't be surprised that the frequencies doens't match to the original one. The runway 07R-25L ILS doens't have this issue. I checked the position of all localisers and glideslopes which are correct. Second thing: the localiser on the same runway is inverted too. While being on right of the runway, the localiser needle is on the right too, and as more you're offset of the runway, as more the needle goes away on the right. Here an example while approaching runway 07L. As you can see, I'm on the right of the runway and the needle should be on the left. I've made a video to show the bugs. I had a third one, as I was on final on runway 25R, at one moment the localiser needle disappeard, shown on the second part of the video, where I added the landing on runway 07R-25L so you can see clearly the difference. As told this video is made with my modified Beacons.lua file, so the runway 07R-25L can be used to land with ILS. And the issue is on both ends of the runway.

In fact, the website is a goldmine for those informations. Maybe all ICAO ID's and ILS, RSBN and PRGM frequencies should been used from this period.

Could you eventually list them? I saw that Buckeburg has this problem, for landing as despite the wind direction, ATC always tells you to land on runway 26. I will make a global feedback ASAP to a dev member. Spangdahlem altitude problem has always reported. Here:

Buckeburg (I know it should be wrotten Bueckeburg ) correction added to the Beacons.lua now. It can be downloaded from the deicated post. I deleted the runway 08 localiser (in fact there was no glideslope on runway 08 in the lua file, and IRL no localiser at all) and corrected the runway 26 Glideslope. Works fine now.

New update 05/17/2025 see first post for information.

Thanks. Know issue: Buckegurg ILS broken. Update will come ASAP.

I'm unaware about using scripts, maybe you can explain me or send me a mission where it's used, so I could try to use it on CWG.

Those informations doesn't appear in any lua file, so I presume that they are part of core files only the devs have access.

I suppose you have to fly to all of them know which ID number correspond to the airfield.

If you could share a screen, maybe I would had a better idea.

Could you develop what you're looking for?

I will make a report direct to a dev as I'm now in contact with him. I will just try to group all inaccuracies together, so they have the most complete list possible.

Hi I just made a correction, but I noticed that despite a wind at 263° 20kts, on a test flight to validate the correction, the ATC told me to land on runway 26... I took of at Bremen airport from runway 09, which is correct. Seems Bueckeburg only use runway 26. I also started direct on Buckeburg, and it was on runway 08. After take off, I contacted the ATC, to request a landing, and it gives me runway 26...

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.

Hi Update today East Germany added and corrections on the western side. File in the first post. All feedback of lack or mistake welcome. Complete ILS frequencies on the Beacon information window in the mission editor

As far as I could understand DCS functioning, it's unable to manage 2 runways at the same airport. You can check other airports with 2 runways, I'm pretty sure Jester will yell at you every time you try to take off on the non official runway (that one without the blue circle). As in Germany or in France military airfields haven't or rarely have 2 runways. Maybe it's more common in the USA, I don't know.

I will test your mission ASAP.

I just made a test with 2 Gazelle, starting at parking 26 and 25, first nav point placed on the north. They flew to the East ovr buildings where the leader started to turn on itself without flying to the waypoints. I then moved the first waypoint over the runway and it works, but the heli went first to the same point before flying the flightplan. By the way they never crashed into the airport buildings, neither on take off, nore no landing.

Hi I noticed that a lot of navaids didn't appear in the Beacon window of the ME. In fact, as the Callsign is used more than twice, the first placed in the Beacons.lua will appear on the list. For example the callsign 'CL' is used for Allstedt, Celle and Pferdsfeld ILS. So in the ILS list in the ME You will only see Allstedt. I modified those from Allstedt and let them for both other airfields. If I select Celle ILS and click on 'Go to beacon', it goes to Pferdsfeld. I made a video so you can see. I not sure that it's only a bug of CWG, maybe more a general bug.

You can add this to your the list. -Werneuchen Zerbst, Laage had an RSBN/PRGM, Garz an KRM/GRM.

My bad. I also noticed that Bindersleben should only have the 28 ILS (109.90) or KGSP (50) depending on the period as seen on https://www.mil-airfields.de/de/erfurt-bindersleben.htm Radio beacons Data for the year 1984: KGSP 28 (SP-50): 110,3 LOM 28: 410 "RF", 7388m to THR LMM 28: 330 "R", 1017m to THR LOM 10: 306 "FR", 5461m to THR LMM 10: 330 "F", 1050m to THR KGSP was an instrument landing system of the soviet type SP-50. Even though it used the same radio frequencies, is was not compatible with the ICAO ILS. The system at Erfurt was in use until ca. 1984. A new ILS was installed in 1988. Data for the year 1990: ILS 28: 109.9 "IRF" LOM 28: 410 "RF", 7388m to THR LMM 28: 330 "R", 1017m to THR LOM 10: 306 "FR", 5461m to THR LMM 10: 330 "F", 1050m to THR

Hi After West Germany, I took a look at the former DDR ILS, and noticed some inaccuracies. I could correct most of them and will share it ASAP. But some of them could only be corrected by the UGRA team. Leipzig Halle: in the Cold War period, it was named Leipzig-Schkeuditz, as I found here https://www.mil-airfields.de/de/halle-leipzig-airport.htm , but other sources tells that it was named Halle since 1928. The ILS should be on runway 29 if I believe the same source. Airfields without informations found (neither cold war nor actual ), who had ILS in DCS: Finow, Barth, Werneuchen, Haina, Allstedt, Garz (KRM/GRM29 Kanal38), Laage (PRGM 10/28, RSBN Kanal 40 "LR")