carbolicus Posted May 26 Posted May 26 The ILS frequencies for both runway directions at Hahn are 112.00 and higher. They hence don’t work - the A10C ILS frequency range cannot be set above 111.95, and although you can set 112.00 in the F4E it won’t pick it up. Having said that, must just say that the CWG map is excellent; looks fantastic and performs very well indeed in VR!
drPhibes Posted May 27 Posted May 27 If things haven't changed since the eighties, the correct frequencies should be: RWY 03: 109,3 MHz, ID: IHAE RWY 21: 111,3 MHz, ID: IHAW 1
grim_reaper68 Posted May 27 Posted May 27 (edited) It's corrected in my file, that will be available ASAP. Edited May 27 by grim_reaper68 1
carbolicus Posted May 28 Author Posted May 28 12 hours ago, grim_reaper68 said: It's corrected in my file, that will be available ASAP. Thanks both!
grim_reaper68 Posted May 28 Posted May 28 Hi just replace the Hahn part in the Beacons.lua file with that and you will have the ILS working fine. { display_name = _('Hahn'); beaconId = 'airfield155_0'; type = BEACON_TYPE_TACAN; callsign = 'HAH'; frequency = 482000000.000000; channel = 24; position = { -438376.968750, 494.136999, -948705.187500 }; direction = -62.061947; positionGeo = { latitude = 49.941656, longitude = 7.260916 }; sceneObjects = {'t:75882522'}; }; { display_name = _('Hahn'); beaconId = 'airfield155_1'; type = BEACON_TYPE_ILS_FAR_HOMER; callsign = 'HAH'; frequency = 482000.000000; position = { -433464.093750, 404.907357, -944366.500000 }; direction = -139.539097; positionGeo = { latitude = 49.991666, longitude = 7.307249 }; sceneObjects = {'t:77332480'}; }; { display_name = _('Hahn'); beaconId = 'airfield155_2'; type = BEACON_TYPE_ILS_LOCALIZER; callsign = 'HAN'; frequency = 111300000.000000; position = { -438922.406250, 494.137030, -949526.875000 }; direction = 43.087785; positionGeo = { latitude = 49.935547, longitude = 7.251175 }; sceneObjects = {'t:217662256'}; chartOffsetX = 2985.000000; }; { display_name = _(''); beaconId = 'airfield155_3'; type = BEACON_TYPE_ILS_GLIDESLOPE; callsign = 'HAN'; frequency = 111300000.000000; position = { -436871.718750, 494.137030, -947771.125000 }; direction = 41.114624; positionGeo = { latitude = 49.956334, longitude = 7.269749 }; sceneObjects = {'t:218825637'}; }; { display_name = _('Hahn'); beaconId = 'airfield155_4'; type = BEACON_TYPE_ILS_LOCALIZER; callsign = 'HAH'; frequency = 109300000.000000; position = { -436439.250000, 494.137030, -947203.500000 }; direction = -136.912208; positionGeo = { latitude = 49.961040, longitude = 7.276341 }; sceneObjects = {'t:218825638'}; chartOffsetX = 2890.000000; }; { display_name = _('Hahn'); beaconId = 'airfield155_5'; type = BEACON_TYPE_ILS_GLIDESLOPE; callsign = 'HAH'; frequency = 109300000.000000; position = { -438376.406250, 494.137030, -948841.250000 }; direction = -138.432185; positionGeo = { latitude = 49.941439, longitude = 7.259072 }; sceneObjects = {'t:217662255'}; }; { display_name = _('Hahn'); beaconId = 'airfield155_6'; type = BEACON_TYPE_VOR; callsign = 'HAH'; frequency = 113000000.000000; position = { -436683.343750, 494.137030, -947216.125000 }; direction = 44.382051; positionGeo = { latitude = 49.958887, longitude = 7.276788 }; sceneObjects = {'t:26820608'}; }; { display_name = _('Hamburg'); beaconId = 'airfield17_0'; type = BEACON_TYPE_ILS_FAR_HOMER; callsign = 'FU'; frequency = 350500.000000; position = { -67656.671875, 42.313069, -699764.750000 }; direction = -119.998992; positionGeo = { latitude = 53.575024, longitude = 9.875992 }; sceneObjects = {'t:159384196'}; }; 1
Raisuli Posted May 28 Posted May 28 Now if we could just get that changed on the default file! Thanks for the fix!
grim_reaper68 Posted May 28 Posted May 28 I'm working on a patch, it could be out before the week-end. I will share it with the devs, and make them a feedback of all issues I've found, so they can include it on the next update. 1
Raisuli Posted May 28 Posted May 28 1 hour ago, grim_reaper68 said: I'm working on a patch, it could be out before the week-end. I will share it with the devs, and make them a feedback of all issues I've found, so they can include it on the next update. Well...until then I have a power shell script to fix all the fixes that get unfixed with updates. This was added to the list. I know there's a mod for that, but last time I looked my way was easier, at least for me
grim_reaper68 Posted May 29 Posted May 29 When I say a patch, it's only the correction of the beacons.lua file. I don't have the dev tools, so I can't touch the "core" file, which generate the lua file. But I'm trying to report every inaccuracy, or issue i can find.
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