grim_reaper68

Hi already demanded here, I added a map with some airbase in or next to their zone 3 polygon.

As child, my first flight was in a C160 Transall in Fürstenfeldbruck. And in fact, extendind the map up to Munich would be great so that after a flight, we could go on the Oktoberfest or any Biergarten to drink a refreshing drink.

Hi take a look here, I've made some correction of the original file. Tested with F-16, A-10CII and Mirage F1. Any bug or information for more accuracy welcome. Hope it will help you. But as told in the related post, DON'T FORGET TO BACKUP THE ORIGINAL FILE!

I noticed that despite the fact that the wind is in the runway direction, if 25L/07R has the same ILS frequency, there is an interference, so I set up the "modern frequency for the 07R so it's fully usable. here is my beacons part of Frankfurt --LOC 07L { display_name = _('Frankfurt'); beaconId = 'airfield163_20'; type = BEACON_TYPE_ILS_LOCALIZER; callsign = 'RHM'; frequency = 110100000.000000; position = { -443583.906250, 100.000100, -851177.812500 }; direction = -100.841391; positionGeo = { latitude = 50.047996, longitude = 8.598907 }; sceneObjects = {'t:73852303'}; chartOffsetX = 4593.000000; }; --GS 25R { display_name = _('Frankfurt'); beaconId = 'airfield163_27'; 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:214099125'}; }; { 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:73862380'}; }; --GS 25L { display_name = _('Frankfurt'); beaconId = 'airfield163_30'; 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:214090990'}; }; --LOC 07R { display_name = _('Frankfurt'); beaconId = 'airfield163_24'; type = BEACON_TYPE_ILS_LOCALIZER; callsign = 'IFSE'; frequency = 110950000.000000; position = { -444262.406250, 100.000100, -851914.812500 }; direction = -100.825012; positionGeo = { latitude = 50.040944, longitude = 8.590415 }; sceneObjects = {'t:73852304'}; 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:73828942'}; }; { 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.414079; positionGeo = { latitude = 50.053775, longitude = 8.637223 }; sceneObjects = {'t:215810048'}; }; --GS 07L { display_name = _('Frankfurt'); beaconId = 'airfield163_21'; 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:212951504'}; }; --LOC 25R { display_name = _('Frankfurt'); beaconId = 'airfield163_28'; type = BEACON_TYPE_ILS_LOCALIZER; callsign = 'DLF'; frequency = 109500000.000000; position = { -444506.750000, 100.000100, -855987.625000 }; direction = 79.143587; positionGeo = { latitude = 50.032752, longitude = 8.535441 }; sceneObjects = {'t:73846094'}; chartOffsetX = 4591.000000; }; --LOC 25L { display_name = _('Frankfurt'); beaconId = 'airfield163_29'; 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:73835198'}; chartOffsetX = 4222.000000; }; --GS 07R { display_name = _('Frankfurt'); beaconId = 'airfield163_23'; type = BEACON_TYPE_ILS_GLIDESLOPE; callsign = 'IFSE'; frequency = 110950000.000000; position = { -445032.750000, 100.000100, -855591.500000 }; direction = -99.485803; positionGeo = { latitude = 50.028721, longitude = 8.542056 }; sceneObjects = {'t:212951505'}; }; { 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:73862381'}; };

TAlking about dynnamic weather, the last time I used it, some clouds disappeared in the field of view, has it been corrected?

I asked the same question, it seems not to be possible to have random weather in DCS.

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.

Yes of course, in game it's available on the CE, EE for player and IA CT and CR. The BE/B had never been able to use it, so I limited it to those who could carry them IRL and the 2 single seater playable version. And as the single and the two seater versions shares the same file for the chaff flares emiter position, you lose the original spanish position for them. As they don't pass the IC, I made the latest version with OVGME, so you can revert easily to the original from MP if needed.

That's impressive! You deserve that your work would be integrated as DCS core weather.

Hi I have a strange issue with the mod. I tried everything on the settings TAA MSAA SSAO on/off etc, reinstall it, but nothing works. The ED assets haven't the issue. I'm not sure it comes from the mod, but maybe someone can help me. My PC, R9 5900X, RX 7900XTX, 64G DDR4, single monitor 1920-1080. I just run some tests and it seems that only "scattered showers 5" is affected by the phenomenon.

CT will have a laser range finger, for a better AG accuracy. Corail pod panel, updated weapon selection panel, better integrated RWR and the abiliy to use GPS for navigation. CR would be a great add, if it could be possible to add the aerial photography to DCS, so it would be possible to make aerial reconnaissance, and make the game more interactive. But In my mind this function is more on the side of ED as AERGES. But as told it's maybe for those versions CR/CT. It's more a wish than a planned version from AERGES.

As I discussed with them, and shared my 3D model, they would, as there is a Corail pod in the shape folder, just be patient. They will make some improvements. Maybe we will have the F1CT/CR one day too.

Do you have the same issue as me with the EC1/30 not appearing on the F1B list? I tested in DCS with France as country, but also in the EDM, where all liveries should appears. Of course it's not a great issue as it works with the F1BE.

This is a transport tank as you can see

Hi I just noticed that the EC 1/30 Alsace BA132 Colmar Meyenheim is missing in the F1B selection, but is present in the F1BE. I also noticed that the F1B/BE livery from the BA118 Mont de Marsan has the wrong number. In fact, the BA118 Mirage F1B should be 118-SR or SL as here, the green part of the nose should be more olive green as here in the photo.

In fact, a lot of things has been upgraded, but there arre still some issues with ILS on several airfields and airports. I'm trying to make correction on the lua file. Unfortunately, I have no acces to RSBN using aircrafts at this time. If you want to share your corrections, so I can merge them to my file and share it on the user files. So We could make the best optimised beacons.lua file for both sides of Germany. Despite the fact that the devs didn't give any news about the navaids, a lot of reported bugs had been taken in account. You can take o look here about Frankfurt ILS issues And here my request about ILS issues. Of course RSBN issues and corrections are welcome.

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.

Hi thanks for the debug. If you take a look here https://www.mil-airfields.de/approach-charts/de-germany/frankfurt-rhein-main-air-base.html you could see that the frequencies in the late 60's are : 07L 110.10 "RHM" , 25L 110.70 "FFM", 25R 109.50 "DLF", and at least 07R 110.70 "FFM" too but with no Glideslope. But we can eventually use the modern frequencies 110.95 "IFSE" to have a complete working ILS. I will test your modification on both side to be sure that everything works, but with the Cold War frequencies i've found. I will soon make a proper working beacons.lua file and share it in the user files so there will be more runways usable. And make some kneeboard pages and printable one, so the pilots could use the runway they want depending on the wind direction. Hamburg is a little bit special as there are no parallel runways, and the ATC only use the "official" runway. Edit: first test runs nice, You get it to work!. I only tested runway 25R and 25L, but as the 25R is now OK, I suppose thet the 07L should be OK. I will test it this evening as in france it's 0:51 AM...

I uninstalled them completely with Revo Uninstaller and installed the latest version and no more bug.

Hi clean install of the latest version 25.8.1 solved the issue.

Hi I found some issue in the beacon lua file. I checked all glideslope and localiser positions who are correct, but the frequencies are totally mixed as shown in the screen below. In fact, compared to Hannover, there is a mix in the loc and G/S frequencies. I modified the lua file, so I could activate the second runway where I noticed no issue at all. LOC and GS works fine. But the main runway ILS system is still broken. As showed on the screen below, the localiser of the runway 25R-07L doesn't work correctly, and is inverted. Normally, if you are on the right of the runway, the needle should be on the left, in this situation the needle is on the right... it's made with the stock beacons.lua file As you can see, I'm on the right of the runway (light blue line), and the needle shows that I'm on the left. It should be on the left side (as drawed with the darker blue line). Both screen where made at the same position as you can see that I was in active pause while switching the ILS frequencies. Only the zoom in the cockpit is different. in comparision the ILS on runway 25L works fine with corrected frequencies and modification in the beacons.lua file, as shown below. Frequency 111.70 for runway 25L ILS approach,set up in the lua file, green strip for runway 25L, and the localiser needle is on the correct side . Same modification works for Hannover and Hamburg where both runways ILS works fine. So I think the issue comes from the core file that give the Beacons.lua file, because with corrected frequencies, the issue remains. It tried to harmonise the frequencies, but it doesn't work at all. The issue remains. Here a video from the bug on runway 25R, and as told, it's the original beacons lua file. The Loc needle is on the wrong side. And the runway 25L ILS approach with a correct ILS needles indication, as I "activated" the runway 25L-07R in the lua file. I hope you can figure out where the issue come from, as it's the only runway affected. By the way, thanks for your great work. If you want, I can make some screens from other airfields, so You can be sure of the relevance of my words. And maybe other pilots can confirm it too.

Are you flying solo on the map? Or with a lot of assets on it? In which resolution? 1920*1080 2K, 4K? Or maybe VR? My setup (R9 5900X, RX 7900 XTX 64Gb RAM DDR4) achieves between 60-300FPS depending on the location, weather and assets on the map. For example on Berlin with bad weather heavy rain) and 20 aircrafts in the zone, I have the lowest FPS (60)

Yes, I can understand it. In fact, none of the french pack or the Charles de Gaulle (CDG), have evolved since a while. So if Currenthill have the time to make a great french pack with vehicles, and why not some special forces (with animation) like the commandos de marine (navy seals) and the foreign legion, and why not the CDG and maybe the Clemenceau /Foch, that would be a great pack that I would download directly.

IDK, but maybe tgere is a way to make a feedback to AMD for this kind of issue.

In fact, back to 25.4.1 and it's OK.