grim_reaper68

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")

Hi As I'm working on the ILS correction on the GDR side, I noticed during a test flight at Berlin's airports, that on Tempelhof, none of the ILS frequencies appears. But they are in the Beacon list. At Schonefeld, only the 25R (110.30). It seems to come from the fact that the main runway is on the 09L/27R for Tempelhof, and 07L/25R for Schonefeld, which, by the way have only an ILS on the 25R (that is correct). I think DCS is unable to "use" ILS at 2 runways at the same airport, which can be tricked in the beacons.lua, but only the "main" runway is displayed in the information window. So, I suggest to switch the "main" runway to 09R/27L for Tempelhof and 07R/25L for Schonefeld, so players could have both ILS direction displayed in the information window on the map while flying. Here you can see Tempelhof without any ILS information. And above I put the screen from the Mission Editor Beacon page. It my WIP Beacons.lua so don't be surprised to see informations you don't have on the stock one. Beacons And here Schonefeld information on the ingame map For comparison here the Hannover info, as you can see, the "main" runway is the southern one, and the ILS IHSE and IHSW are those from that one

The runways in the 80's and 90's had a lenght of 1882m (6174ft) for the 08/26 and 1704m (5590ft) for the 03/21. So larger aircraft like the AWACS or the KC-135 couldn't take of there. If you take a look here https://earth.google.com/web/search/wunstorf/@52.45817399,9.42855077,53.21398276a,5865.38077443d,35y,0h,0t,0r/data=Cj4iJgokCUDDiHet7UpAEehPjYlu40pAGdgMJiV61iVAIR4kloYHRCVAKhAIARIKMjAxMC0xMi0zMRgBQgIIAToDCgEwQgIIAEoNCP___________wEQAA , you can see that the runway 08/26 has been outspread in 2010. So the DCS runways are accurate to the period.

Hi Could it be possible to have the sound from the KC-135 on the KC-135 MPRS? On my side I have the turbofan engine sound on the KC-135, but the MPRS sounds more like an cessna citation... I searched for the KC-135 sound files, but found nothing.

@IvanK, my bad I concentrated of the major airfields. I made an update of some minor airfields, but hadn't time to test them. I also saw after research that Hildesheim didn't have an ILS as it was more an heli airfield on the actual informations I could find. But it's on the map... (meanwhile 111.20 doesn't work). As told I'm glad of any feedback about mistakes or omissions of my part. I also wil check all the East Germany part, and made the needed corrections. I try to find informations from the cold war period about the ILS and use actual charts to try to crosscheck the accuracy of the frequencies. I hope Ugra will include our work when totally finished, so it can pass the IC for accurate IFR MP flight. I also found an lonesome Localiser on Buckeburg at runway 7 whiwh is accurate but a little bit surprising. I first thought it was a mistake. Just an example: I looked at Leipzig Halle, where actually you have 2 runways 08-26, but on google earth in 2006 you have the "original" runway as in DCS (10-28). But I can find informations about the ILS from the 70's to the 90's... But I will at this time adjust the directions if needed and try to find the most accurate frequencies I could find (as even first decimals aren't usable). I just discovered the PRMG ILS, but don't know if I have any plane who's able to use them. I think only russian planes used it. So I ask all pilots who could check them, if the could make me a feedback, so I can modify what's needed.

Just checked in Google Earth, and in fact, you're right, the whole terrain around the airbase is too low. It should be at an average altitude of 1150ft. Meanwhile, the elevation of the terrain at the East is correct. It's just that the airbase is too low. When you look at Google Earth, and follow the terrain at the end of rwy 05, up to the road, the highest altitude will be 1280ft, which is accurate to DCS.

Hi With the help from @Thadeyus and @drPhibes, I propose you an updated beacons.lua for West Germany. Radionav freq corrected by @Thadeyus. Airports with 2 runways where only one ILS was working, have now both working, thanks @drPhibes. Hamburg is a little bit tricky as the runways aren't parallel. And the ATC only announce landing on runway 5-23, but depending on wind direction runway 15-33 ILS works fine. ILS frequencies and directions (most the time the Glideslope) have been corrected. I will make a frequency ref ASAP. If someone would indicate me if East Germany ILS are broken, or incorrect, let me know so I can update it. I suppose it wouldn't pass the IC. If you notice some inaccuracies in the modified ILS (wrong frequencies or else) just tell me. I used different sources, but maybe some are too recent. Paste the file into your DCS World\Mods\terrains\GermanyColdWar folder. Don't forget to backup your original file! Use at your own risks Enjoy! Update 05/13/2025: East Germany treated, and corrections on Western airfields New update 05/17/2025: Buckeburg, correction of ILS 26 glideslope and deleted runway 08 Localiser. 05/29/2025 New update. Known issues, Frankfurt ILS runway 07L-25R doesn't work correctly. Runway 07R-25L works fine. 07R 111.10 25L 110.70, waiting for feedback of @Ramsay, as it seem to have a solution. Buckeburg ATC only tells you to land on runway 26, same for Bindersleben (runway 10), Dev report will be made ASAP, as it hasn't anything to do with the lua file. Hamburg Finkenwerder: Glideslopes paired to the localisers and on the correct runway. Hamburg, Hannover, Tegel, Schonefeld. All runways ILS usable. Just write down the ILS frequencies of the alternate runways in the Mission Editor. I will make a kneeboard and printable doc of all frequencies ASAP. Hamburg runways aren't parallel, (05-23, 15-33), so depending on the wind direction, you have the choice to land on the best runway. DCS ATC will only tells you to land on runway 05-23, as it's unable to manage 2 runways at one airport. Inverted Ils position and direction on Leipzig Halle, as it should be, runway 29 ILS instead of 11. Modified Pferdsfeld 109.20 (unusable) to 109.30 ILS runway 09. I didn't found informations about ILS on this runway, but let it so, to have one more airfield for ILS landing. If you noticed any bug, feel free to tell me, so I can correct it. RSBN/PRGM aren't treated, as I didn't fly "red" aircrafts since now. I just loaded the L-39C to make test flights, but I have to learn about the rusisan ILS systems. So any feedback about East Germany RSBN/PRGM system inaccuracy is welcome too. New Update 06/07/2025 Damgarten RSBN/PRGM set to 832MHz (channel 32) as it should be. Noticed a localizer deviation while landing runway 07, with the L39. To confirmed by professionnal L39 pilots as I'm newbie and have only 14 days trial. beacons.lua

@drPhibes I just noticed an inversion, between the directions. In fact, IHSW should be on runway 27 and IHSE on 9. Same for the frequencies. I changed them as you can see here. and a flight check. RWY 9L and RWY 9R here are the lines (only the ILS part, as I hadn't to modify the VOR/NBD) --Hannover -- 09L { display_name = _('Hannover'); beaconId = 'airfield19_99'; type = BEACON_TYPE_ILS_LOCALIZER; callsign = 'IHNE'; --ILS correction frequency = 108300000.000000; --ILS correction position = { -188436.453125, 51.180933, -730706.875000 }; direction = -78.514527; --ILS correction positionGeo = { latitude = 52.466823, longitude = 9.703153 }; sceneObjects = {'t:130102024'}; chartOffsetX = 2963.000000; }; { display_name = _('Hannover'); beaconId = 'airfield19_98'; type = BEACON_TYPE_ILS_GLIDESLOPE; callsign = 'IHNE'; --ILS correction frequency = 108300000.000000; --ILS correction position = { -187671.062500, 51.180936, -733377.500000 }; direction = -78.514527; positionGeo = { latitude = 52.469834, longitude = 9.662851 }; sceneObjects = {'t:48754130'}; }; -- 27R { display_name = _('Hannover'); beaconId = 'airfield19_97'; --ILS correction type = BEACON_TYPE_ILS_LOCALIZER; callsign = 'IHNW'; --ILS correction frequency = 108900000.000000; --ILS correction position = { -187795.875000, 51.180936, -733856.125000 }; direction = 101.497718; positionGeo = { latitude = 52.468062, longitude = 9.656230 }; sceneObjects = {'t:131006862'}; chartOffsetX = 2962.000000; }; { display_name = _('Hannover'); beaconId = 'airfield19_96'; --ILS correction type = BEACON_TYPE_ILS_GLIDESLOPE; callsign = 'IHNW'; --ILS correction frequency = 108900000.000000; --ILS correction position = { -188147.750000, 51.180936, -731212.125000 }; direction = 101.497718; positionGeo = { latitude = 52.468662, longitude = 9.695199 }; sceneObjects = {'t:48754131'}; }; -- 09R { display_name = _('Hannover'); beaconId = 'airfield19_7'; type = BEACON_TYPE_ILS_LOCALIZER; callsign = 'IHSE'; --ILS correction frequency = 108700000.000000; --ILS correction position = { -189994.000000, 51.180936, -730121.062500 }; direction = -78.514527; positionGeo = { latitude = 52.453909, longitude = 9.715167 }; sceneObjects = {'t:130102023'}; chartOffsetX = 2640.000000; }; { display_name = _('Hannover'); beaconId = 'airfield19_6'; type = BEACON_TYPE_ILS_GLIDESLOPE; callsign = 'IHSE'; --ILS correction frequency = 108700000.000000; --ILS correction position = { -189648.265625, 51.180936, -732407.375000 }; direction = -78.514527; --ILS correction positionGeo = { latitude = 52.453763, longitude = 9.681384 }; sceneObjects = {'t:47898667'}; }; --27L { display_name = _('Hannover'); beaconId = 'airfield19_2'; type = BEACON_TYPE_ILS_LOCALIZER; callsign = 'IHSW'; frequency = 109500000.000000; position = { -189416.812500, 51.180936, -732959.937500 }; direction = 101.497301; positionGeo = { latitude = 52.455030, longitude = 9.672881 }; sceneObjects = {'t:130102022'}; chartOffsetX = 2604.000000; }; { display_name = _('Hannover'); beaconId = 'airfield19_10'; type = BEACON_TYPE_ILS_GLIDESLOPE; callsign = 'IHSW'; --ILS correction frequency = 109500000.000000; --ILS correction position = { -189997.359375, 51.180936, -730727.625000 }; direction = 101.497301; positionGeo = { latitude = 52.453033, longitude = 9.706422 }; sceneObjects = {'t:47900634'}; };

Finally I managed to make Ramstein ILS work correctly. And to have the correct information. 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'};

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.

Where should I remove it? Here?

So maybe, to be accurate, the TACAN position and frequency should depend from the time. But the point is, when was it changed?

@drPhibes you make my day with your data. I couldn't imagine that the beaconID could be the cause of this trouble. Hamburg airport had the same problem with runway 15-33 where the ILS wasn't working at all. By the way as both runway have different directions, the ATC only uses the 05-23, and never tells to land on 15-33, but with a wind on the ground at 170° 10kts, the 33 ILS is active. Strangely Frankfurt doens't have this problem, despite the fact that it's wrotten same as Hannover. here is my part of Fankfurt airport with correct ILS direction and frequencies { display_name = _(''); beaconId = 'airfield163_0'; type = BEACON_TYPE_ILS_LOCALIZER; callsign = 'RHM'; --ILS correction frequency = 110100000.000000; --ILS correction position = { -443583.906250, 100.000100, -851177.812500 }; direction = -100.841391; positionGeo = { latitude = 50.047996, longitude = 8.598907 }; sceneObjects = {'t:75253086'}; chartOffsetX = 4593.000000; }; { display_name = _(''); beaconId = 'airfield163_1'; type = BEACON_TYPE_ILS_GLIDESLOPE; callsign = 'IFCE'; --ILS correction frequency = 110100000.000000; --ILS correction position = { -444432.531250, 100.000100, -855199.875000 }; direction = -97.789724; positionGeo = { latitude = 50.034575, longitude = 8.546010 }; sceneObjects = {'t:213574106'}; }; { display_name = _(''); beaconId = 'airfield163_2'; type = BEACON_TYPE_ILS_GLIDESLOPE; callsign = 'IFCW'; --ILS correction frequency = 109500000.000000; --ILS correction position = { -443643.500000, 100.000100, -851917.625000 }; direction = 78.659744; positionGeo = { latitude = 50.046376, longitude = 8.588953 }; sceneObjects = {'t:214721712'}; }; { display_name = _(''); beaconId = 'airfield163_3'; type = BEACON_TYPE_ILS_LOCALIZER; callsign = 'IFSW'; --ILS correction frequency = 110700000.000000; position = { -445112.812500, 100.000100, -856363.250000 }; direction = 79.197225; positionGeo = { latitude = 50.026870, longitude = 8.531721 }; sceneObjects = {'t:75235958'}; chartOffsetX = 4222.000000; }; { display_name = _(''); beaconId = 'airfield163_4'; 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:75263155'}; }; { display_name = _(''); beaconId = 'airfield163_5'; type = BEACON_TYPE_ILS_LOCALIZER; callsign = 'IFCW'; --ILS correction frequency = 109500000.000000; position = { -444506.750000, 100.000100, -855987.625000 }; direction = 79.143601; positionGeo = { latitude = 50.032752, longitude = 8.535441 }; sceneObjects = {'t:75246876'}; chartOffsetX = 4591.000000; }; { display_name = _(''); beaconId = 'airfield163_6'; type = BEACON_TYPE_ILS_GLIDESLOPE; callsign = 'IFSE'; --ILS correction frequency = 111100000.000000; --ILS correction position = { -445032.750000, 100.000100, -855591.500000 }; direction = -99.485803; positionGeo = { latitude = 50.028721, longitude = 8.542056 }; sceneObjects = {'t:213574107'}; }; { display_name = _('Frankfurt'); beaconId = 'airfield163_7'; type = BEACON_TYPE_VORTAC; callsign = 'FFM'; frequency = 114200000.000000; channel = 89; position = { -443403.843750, 118.535061, -848339.000000 }; direction = -12.414080; positionGeo = { latitude = 50.053775, longitude = 8.637223 }; sceneObjects = {'t:214728704'}; }; { display_name = _(''); beaconId = 'airfield163_8'; 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:75263156'}; }; { display_name = _(''); beaconId = 'airfield163_9'; type = BEACON_TYPE_ILS_GLIDESLOPE; callsign = 'IFSW'; --ILS correction frequency = 110700000.000000; --ILS correction position = { -444321.468750, 100.000100, -852673.437500 }; direction = 81.530965; positionGeo = { latitude = 50.039301, longitude = 8.580205 }; sceneObjects = {'t:214713585'}; }; { display_name = _(''); beaconId = 'airfield163_10'; 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:75229589'}; }; { display_name = _(''); beaconId = 'airfield163_11'; type = BEACON_TYPE_ILS_LOCALIZER; callsign = 'IFSE'; --ILS correction frequency = 111100000.000000; --ILS correction position = { -444262.406250, 100.000100, -851914.812500 }; direction = -100.825012; positionGeo = { latitude = 50.040944, longitude = 8.590415 }; sceneObjects = {'t:75253087'}; chartOffsetX = 4222.000000; };

Exactly that's the point.

same here the container are flickering a lot

Do you give me the permission to add your modifications to mine? I corrected all ILS of the West Germany airfields that were incorrect (frequencies and direction). Maybe I missed some but hope for players to inform me. I added an extra comment at the end of the beacons.lua: -- Note: Adujusted most NDB frequencys. Changed frequencys are Marked with "--Frequency adyusted" by Thadeyus -- Note: Corrected ILS glideslopes and localizer frequencies and directions marked with "--ILS correction" by grim_reaper68

Wiesbaden have one ILS on runway 25 (freq 108.50, ident ITOU), by the way on actual charts, WIB 88X is the correct TACAN. After a research, I found WBD but it has 28X and not 88X Tacan approach May 1966 I found interesting informations here https://www.mil-airfields.de/radio-beacons/de-germany/radio-beacons-west-germany-1958.html

Yes, after several modifications in the beacons.lua to correct some lines.

Hi Continuing testing all western airport ILS to fix them, I just noticed that Hannover airport, despite the fact that there are both ruways equiped with ILS, the 9L-27R ILS doens't work at all. Never had a tone in the F16, the frequencies are correct and correctly set . As Frankfurt airport is similar and both ILS are working, I can't explain, what's wrong there. Maybe you can fix it. By the way, I had a tanker who took off from this runway, so it seems to be recognised.

Hi Did you test it on both runways? maybe it could be that only one is recognised.

In fact after a search, the first decimal is odd, so the only available frequecies decimals are .10, .15, .30, .35, 50, .55 etc... up to .95. I also found ILS freq for Zweibrücken that are 108.35 for runway 3 (29.96°) and 109.35 for runway 21 (209.96°). Not sure they where accurate in the cold war period, but would be nice to have them to be able to make ILS landing on ZWB. As now there is only the runway 3 ILS, They should have to add the runway 21 ILS on the map.

Hi Both airports have the same ILS frequencies in the same direction. While landing in Pferdsfeld runway 05, the ILS had a strange behavior. In fact sometimes it was on the runway, and sometimes completely on the left. Same in the other direction. Changing the ILS frequencies of Wiesbaden solved the problem. By the way, actually Wiesbaden Airbase have just one ILS on runway 25 (108.10).I don't if that was the case in the cold war period.

I noticed something today. Sometimes, when the map is loaded, the RAM used is up to 24-25Gb, and sometimes I got it down to 1.5-4Gb. while running at low RAM usage, I got FPS drops, that I never have while the RAM is at the upper load.