grim_reaper68 Posted August 20 Posted August 20 (edited) Hi, I'm working on a full ILS usable beacons.lua file. As far as I could see, there was an issue with frankfurt main runway ILS issues, solved thanks @drPhibes, I could make Frankfurt, Hamburg, Hannover, and Berlin "secondary" runways usable, and corrected Hamburg Finkenwerder ILS issue, as the glideslope and the localizer where mixed. So If you noticed some bugs or inaccuracies on some ILS airfields, just let me know, so I can make an edited lua file , with all corrections that I could make. The file will be shared on the user files, with kneeboard files so you can choose the runway You want to land, and have the ILS informations for them. I edited also the Hahn frequencies to 111.30 for the runway 21, and 109.30 for the runway 03. Those are virtual frequencies, as at this time, I didin't found any information about the cold war period for the ILS frequencies. I will share my work with the help of @drPhibes ASAP and keep it up to date ASAP as every update will change the original file. I saw that the devs has taken in account a lot modifications I've made, so I have a great hope of an original file that will be 100% functional over the time. Edited 3 hours ago by grim_reaper68 Title modified 4
drPhibes Posted 4 hours ago Posted 4 hours ago If you don't mind me hijacking the thread a little, there are also some issues with NDBs on the map. Many of the NDBs located at the middle/outer markers for various airports have the same operating frequency in both runway directions, but the markers and NDBs are not interlocked based on the active runway (which they would be IRL, just like ILS). This is not an issue for the markers (which are all at 75 MHz) since they radiate a narrow beam straight up, but the NDBs can be difficult to identify by their ident codes (as the morse code for the two NDBs overlap) at long range, and are unstanble at short range, since your ADF will show erratic bearings. This may or may not be fixed when ED release their new ATC, but until then, I propose adding a 1kHz offset to every duplicate in the list below (where it doesn't cause any other frequency conflicts). E.g.: 313000 airfield2_2 LG Altes Lager 314000 airfield2_4 BM Altes Lager 645000 airfield2_0 L Altes Lager 646000 airfield2_1 B Altes Lager The duplicate list: Freq. BeaconID ID Airfield Notes 205000 airfield1_0 G Wittstock 205000 airfield1_4 O Wittstock 421000 airfield1_1 GJ Wittstock 421000 airfield1_6 OR Wittstock 219000 airfield15_0 P Templin 219000 airfield15_8 I Templin 451000 airfield15_4 PG Templin 451000 airfield15_6 IK Templin 221000 airfield101_0 - Sperenberg Invalid ident 221000 airfield101_3 NZ Sperenberg 254000 airfield101_1 Ch Sperenberg 254000 airfield101_2 - Sperenberg Invalid ident 295000 airfield118_7 X Holzdorf 295000 airfield118_8 H Holzdorf 609500 airfield118_2 XH Holzdorf 609500 airfield118_4 HX Holzdorf 300000 airfield22_7 Z Mahlwinkel 300000 airfield22_8 Z Mahlwinkel 620000 airfield22_3 NU Mahlwinkel 620000 airfield22_6 ZW Mahlwinkel 313000 airfield2_2 LG Altes Lager 313000 airfield2_4 BM Altes Lager 645000 airfield2_0 L Altes Lager 645000 airfield2_1 B Altes Lager 325000 airfield10_1 NZ Damgarten 325000 airfield10_5 M Damgarten 668000 airfield10_0 MA Damgarten 668000 airfield10_7 NW Damgarten 330000 airfield13_3 G Garz 330000 airfield13_5 G Garz 679500 airfield13_0 GZ Garz 679500 airfield13_4 ZG Garz 345000 airfield4_1 Z Zerbst 345000 airfield4_5 K Zerbst 708000 airfield4_3 KJ Zerbst 708000 airfield4_6 ZB Zerbst 350000 airfield82_1 GX Kothen 350000 airfield82_2 RX Kothen 718000 airfield82_0 G Kothen 718000 airfield82_4 R Kothen 365000 airfield157_2 LU Allstedt 365000 airfield157_3 BZ Allstedt 376000 airfield84_0 UU Parchim 376000 airfield84_3 AS Parchim 398000 airfield169_1 DK Merseburg 398000 airfield169_7 KD Merseburg 412000 airfield24_2 W Neuruppin 412000 airfield24_3 G Neuruppin 842000 airfield24_0 GK Neuruppin 842000 airfield24_1 WO Neuruppin 423000 airfield25_3 NE Peenemunde 423000 airfield25_4 EN Peenemunde 425000 airfield171_3 M Leipzig 425000 airfield171_4 S Leipzig 426000 airfield236_1 G Mockau 426000 airfield236_2 L Mockau 430000 airfield26_2 M Schönefeld 430000 airfield26_8 S Schönefeld 442000 airfield12_1 OM Finow 442000 airfield12_2 RG Finow 460000 airfield23_2 T Neubrandenburg 460000 airfield23_3 DK Neubrandenburg 476000 airfield21_0 U Lerz 476000 airfield21_4 B Lerz For the WSL or mingw64 users, all frequencies in the beacon file can be listed using grep "frequency" beacons.lua | sort (There is probably also some unnecessarily convoluted powershell command that can do the same thing) 1
grim_reaper68 Posted 2 hours ago Author Posted 2 hours ago Talking about other navaids, I noticed that in the late 60's, Frankfurt had a vortac (58 "FFM" 112.1) who seemed to be near the middle marker of the runway 25.
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now