-
Posts
688 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by grim_reaper68
-
SA-342 Gazelle 2023 "FM" Update
grim_reaper68 replied to Polychop Simulations's topic in SA-342M Gazelle
Hi lasing commands are only visible from the copilot profile, so you have to look at the copilot command page. In my case, but maybe related to my TM warthog profile, the keys for the lasing cover is E, and lasing LAlt+W. The weapon mode selection (Hot missile), are RAlt+H and RAlt+Q, next station is LShift+7 and previous station LShift+8. -
Military Assets for DCS by Currenthill
grim_reaper68 replied to currenthill's topic in Static/AI Mods for DCS World
Could you maybe share it? -
Military Assets for DCS by Currenthill
grim_reaper68 replied to currenthill's topic in Static/AI Mods for DCS World
Hi where did you get this livery for the Eagle? -
I just run a test flight and added smokes on the Loc, glideslope and RSBN, and I can confirm that in the L39, when RSBN and PRGM use the same channel, in Damgarten for sure (had to be confirmed on other airfields or maps), the loc needle deviates through the RSBN as you get closer. Bearing was set to 259° and the perfectly aligned with the runway. I had the same issue on the other side.
-
I will run tests on ohter airfields. I know you made all what you can, maybe it's the Mig 21 who has some issues. For the L-39, indeed it works, but as told while landing on runway 07 (79° bearing), the localiser was offset with the runway while using the channel 32. Seemed that it was using the RSBN as loc. For the question to @MAESTR0, I've posted a Beacons file, where the informations are completed, and several ILS updates where made. Only issue I had was on Frankfurt where the ILS on runway 07L-25R, I even tested it with the original file, with the same issue. Maybe you can test it, if you have the original file to confirm the bug. I made a video from the behavior. And if you want, you can load the Beacons file there, I just updated it with channel 32 for Damgarten.
-
Indeed, I've understood that. I was just wondering why the Mig 21 didn't catch the PRGM despite the fact it was tune on the same channel as the RSBN.
-
As far as I could see, Damgarten seemed never to had an ICAO code or something like that. About the channel, in fact in the Beacons file, the frequency is 820 MHz, which corresponds to the channel 20. I modified it in the file to 832000000.000000, and it works fine at channel 32 (RSBN and PRGM), but strangely the localiser seems to be wrong. As I needed to set the bearing at 72 instead of 79 while being aligned with the runway. I ran a test with channel 33 (833MHz) for the PRGM, and the bearing was correct. Here a screen with PRGM at channel 32. This solution works for the L39, but not for the Mig 21. He never shows any reaction to the channel 33. Same with channel 32 PRGM won't work at all.
-
I think they didn't know that ß is a special german S, as it looks like the greek Beta. As both persons above told, ß could be replaced by 2 "s".
-
Location of bases with firing ranges and tank courses
grim_reaper68 replied to ours's topic in DCS: Cold War Germany
-
Military Assets for DCS by Currenthill
grim_reaper68 replied to currenthill's topic in Static/AI Mods for DCS World
Same here, just tested, Germany 1.1.0 and 1.1.1 installed HX vehicles appears on the battlefield. -
Cold War Germany Photos and Videos
grim_reaper68 replied to Devil 505's topic in DCS: Cold War Germany
I just wonder how you, guys make so beautiful screens! -
Cold War Germany Photos and Videos
grim_reaper68 replied to Devil 505's topic in DCS: Cold War Germany
@Stanlesuper I first thought it was a real screen! Then I saw the information at the bottom. -
Cold War Germany Photos and Videos
grim_reaper68 replied to Devil 505's topic in DCS: Cold War Germany
Nice Mirage 2000D mod, is it from Split'air? -
ILS Frequencies for Hahn don’t work
grim_reaper68 replied to carbolicus's topic in Bugs and Problems
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. -
ILS Frequencies for Hahn don’t work
grim_reaper68 replied to carbolicus's topic in Bugs and Problems
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. -
ILS Frequencies for Hahn don’t work
grim_reaper68 replied to carbolicus's topic in Bugs and Problems
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'}; }; -
Frankfurt ILS runway 07L-25R issues
grim_reaper68 replied to grim_reaper68's topic in Bugs and Problems
Could you share your modified file so I can compare to mine. Thanks in advance. -
Nope it was there before, as I printed the whole beacons lua file before the latest update, I can prove it was there .
-
Frankfurt ILS runway 07L-25R issues
grim_reaper68 replied to grim_reaper68's topic in Bugs and Problems
I just maid an test flight landing on runway 25R, and i had the same loc issue while approaching the runway threshold. the loc disappear suddenly. same for 07 landing by the way ILS guided me to runway 07R... as you can see on the screen. So I can affirm that Frankfurt airport ILS system is completely broken since the latest update. IMHO, it's a bug in the dev core file, because before the update there was no problem. So to correct that, ILS loc and GS frequencies should be corrected as in the file joined, same for the directions. Something went wrong with the latest update on this airfield. I'm sure the devs will fix it. Don't use this file as there is only the Frankfurt airfield part. EDDF ILS corrected.lua -
Frankfurt ILS runway 07L-25R issues
grim_reaper68 replied to grim_reaper68's topic in Bugs and Problems
@Ramsay As told, there is no runway inversion, but the Localiser needle is on the wrong side. I repaired DCS to be sure to have the original file, and the issue is here. As you can see on the screen, I'm on the left side of the runway, so the loc needle should be on the right side in the HUD. No issue at other airfields and maps, only this runway seems to be affected. And between the Mission Editor (ME) and the ingame information, the frequencies are inverted too, as you can see below, runway 25R, ILS 110.10 in the ME, and 110.70 ingame... I just noticed another issue, If you take a closer look on the ME screen, you can see that the frequencies given ingame aren't on the same runway... In the ME the freq of runway 07L-25R are 110.70-110.10, and in game you have 111.10-110.70. But 111.10 is the freq of for runway 07, which is the frequency of runway 25L en the ME... , and should have be 110.10. And as I checked all ILS frequencies on this page https://www.mil-airfields.de/approach-charts/de-germany/frankfurt-rhein-main-air-base.html , and if you take a look, correct frequencies for the runways should be 07L: 110.10 "RHM" 25R: 109.50 "DLF" 07R: 110.70 "FFM" with no glideslope, actual charts gives you 110.95 "IFSE" for that runway (Loc and Glideslope) 25L: 110.70 "FFM" So there is a complete mix up here. I made a check using CCS coordinates on the map in the mission editor. And made 2 lua file to compare, I added comments, and grouped each runways ILS, so it's easier to read. And here the results, the original one --LOC 07L { display_name = _('Frankfurt'); beaconId = 'airfield163_0'; type = BEACON_TYPE_ILS_LOCALIZER; callsign = 'IFM'; frequency = 110700000.000000; position = { -443583.906250, 100.000100, -851177.812500 }; direction = -100.841391; positionGeo = { latitude = 50.047996, longitude = 8.598907 }; sceneObjects = {'t:75400878'}; chartOffsetX = 4593.000000; }; --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 07R { display_name = _('Frankfurt'); beaconId = 'airfield163_4'; type = BEACON_TYPE_ILS_LOCALIZER; callsign = 'DLF'; frequency = 109500000.000000; position = { -444262.406250, 100.000100, -851914.812500 }; direction = -100.825012; positionGeo = { latitude = 50.040944, longitude = 8.590415 }; sceneObjects = {'t:75400879'}; chartOffsetX = 4222.000000; }; --GS 07R { display_name = _('Frankfurt'); beaconId = 'airfield163_10'; type = BEACON_TYPE_ILS_GLIDESLOPE; callsign = 'IRF'; frequency = 111100000.000000; position = { -445032.750000, 100.000100, -855591.500000 }; direction = -99.485803; positionGeo = { latitude = 50.028721, longitude = 8.542056 }; sceneObjects = {'t:214647239'}; }; --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; }; --GS 25R { display_name = _('Frankfurt'); beaconId = 'airfield163_1'; type = BEACON_TYPE_ILS_GLIDESLOPE; callsign = 'IFM'; frequency = 110700000.000000; position = { -443643.500000, 100.000100, -851917.625000 }; direction = 78.659744; positionGeo = { latitude = 50.046376, longitude = 8.588953 }; sceneObjects = {'t:215803068'}; }; --LOC 25L { display_name = _('Frankfurt'); beaconId = 'airfield163_9'; type = BEACON_TYPE_ILS_LOCALIZER; callsign = 'IRF'; frequency = 111100000.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 25L { display_name = _('Frankfurt'); beaconId = 'airfield163_3'; type = BEACON_TYPE_ILS_GLIDESLOPE; callsign = 'DLF'; frequency = 109500000.000000; position = { -444321.468750, 100.000100, -852673.437500 }; direction = 81.530965; positionGeo = { latitude = 50.039301, longitude = 8.580205 }; sceneObjects = {'t:215794929'}; }; As you can see some of the glideslopes freq doesn't match to their localiser... I just wonder how you can manage to land an ILS approach with no matching frequencies. And the one I've modified, harmonised frequencies and callsigns. --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 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 07R { display_name = _('Frankfurt'); beaconId = 'airfield163_4'; 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; }; --GS 07R { display_name = _('Frankfurt'); beaconId = 'airfield163_10'; 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'}; }; --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; }; --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'}; }; --LOC 25L { display_name = _('Frankfurt'); beaconId = 'airfield163_9'; 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 25L { display_name = _('Frankfurt'); beaconId = 'airfield163_3'; 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'}; }; -
In fact it's mentionned here https://www.mil-airfields.de/de/fassberg.htm in the year 1984 NBD: 284 "FSB", but it's ingame, or should it be another one?
-
ILS Frequencies for Hahn don’t work
grim_reaper68 replied to carbolicus's topic in Bugs and Problems
It's corrected in my file, that will be available ASAP.