drPhibes Posted May 14, 2024 Posted May 14, 2024 I'm too impatient to wait for all the missing airports (with their associated navaids) to be added to the Norwegian part of the map, so I have started adding a few TACANS and DVOR/DMEs to help with navigation when flying along the coast. I have also fixed (or at least improved) the crooked LOC07 at Bodø, and added the missing LOC16 approach to Banak/Lakselv. Nothing is ready for release yet, but if anyone is interested, I can see if I can get something done during the weekend. 1 5
Rudel_chw Posted May 14, 2024 Posted May 14, 2024 12 minutes ago, drPhibes said: Nothing is ready for release yet, but if anyone is interested, I can see if I can get something done during the weekend. I'm really interested, but please do not hurry because of me, as I'm still busy on the swedish part of the map, porting my Viggen missions onto the Kola map. 1 For work: iMac mid-2010 of 27" - Core i7 870 - 6 GB DDR3 1333 MHz - ATI HD5670 - SSD 256 GB - HDD 2 TB - macOS High Sierra For Gaming: 34" Monitor - Ryzen 3600 - 32 GB DDR4 2400 - nVidia RTX2080 - SSD 1.25 TB - HDD 10 TB - Win10 Pro - TM HOTAS Cougar Mobile: iPad Pro 12.9" of 256 GB
fagulha Posted May 14, 2024 Posted May 14, 2024 I´m interested too. Take your time. Thank you for working on this and sharing. Keep up. F. 1 About carrier ops: "The younger pilots are still quite capable of holding their heads forward against the forces. The older ones have been doing this too long and know better; sore necks make for poor sleep.' PC: 14th I7 14700KF 5.6ghz | 64GB RAM DDR5 5200 CL40 XMP | Gigabyte RTX 4080 Super Aero OC 16 GB RAM GDDR6X | Thermalright Notte 360 RGB | PSU Thermaltake Though Power GF A3 Snow 1050W ATX 3.0 PCIE 5.0 / 1 WD SN770 1TB M.2 NVME + 1 SSD M.2 2TB + 2x SSD SATA 500GB + 1 Samsung 990 PRO 4TB M.2 NVME (DCS only) | Valve Index| Andre´s JeatSeat.
drPhibes Posted May 16, 2024 Author Posted May 16, 2024 All the VOR+DME (13) and TACAN (4) sites in the area have been added. Now I just need to check if they all work. 2 2
skywalker22 Posted May 17, 2024 Posted May 17, 2024 Will it pass IC? I doubt it. Pass this to Orbx, so they include it in the map.
drPhibes Posted May 17, 2024 Author Posted May 17, 2024 Unless ED have changed the way the IC works since my last beacon mod several years ago, it will not pass IC.
Tholozor Posted May 24, 2024 Posted May 24, 2024 Glad to see I wasn't the only one who thought to do this! REAPER 51 | Tholozor VFA-136 (c.2007): https://www.digitalcombatsimulator.com/en/files/3305981/ Arleigh Burke Destroyer Pack (2020): https://www.digitalcombatsimulator.com/en/files/3313752/
drPhibes Posted May 26, 2024 Author Posted May 26, 2024 (edited) Here's what I've made so far. I have chosen to not publish a complete beacons.lua, since that would revert any improvements made by Orbx if I don't keep it updated, so you'll need to paste the code below into yur beacons.lua file yourself. 1. Navigate to \DCS World\Mods\terrains\Kola\ and make a copy of the existing beacons.lua 2. Open beacons.lua in a text editor, e.g. Notepad++, VS Code or similar. 3. Scroll down to line 185, and delete (or comment out) line 185 to 196. 4. Paste the code below at the end of the file, before the final } -- Bodø: fixed alignment for LOC 07 { display_name = _('BODO'); beaconId = 'airfield7_2'; type = BEACON_TYPE_ILS_LOCALIZER; callsign = 'BO'; frequency = 110300000.000000; position = { -66777.370239, 14.925576, -346636.089121 }; direction = -96.100000; positionGeo = { latitude = 67.205775, longitude = 14.404108 }; sceneObjects = {'t:22119438'}; chartOffsetX = 3703.000000; }; -- Banak LOC 16 { display_name = _('banak'); beaconId = 'airfield1_5'; type = BEACON_TYPE_ILS_LOCALIZER; callsign = 'bk'; frequency = 109350000.000000; position = { 233270.852105, 1.404329, 88608.212175 }; direction = -8.267315; positionGeo = { latitude = 70.054556, longitude = 24.976822 }; sceneObjects = {'t:24846604'}; chartOffsetX = 2898.000000; }; --Evenes TACAN { display_name = _('ENEV'); beaconId = 'airfield13_1'; type = BEACON_TYPE_TACAN; callsign = 'EVS'; frequency = 111000000.000000; channel = 67; position = { 60228.512886, 21, -239542.069812}; direction = 0; positionGeo = { latitude = 68.491286, longitude = 16.675058 }; sceneObjects = {'t:00000000'}; }; --Evenes DVOR+DME { display_name = _('ENEV'); beaconId = 'airfield13_2'; type = BEACON_TYPE_VOR_DME; callsign = 'EVD'; frequency = 117350000.000000; channel = 120; position = { 56431.193858, 37, -239526.363192 }; positionGeo = { latitude = 68.457336, longitude = 16.681939 }; sceneObjects = {'t:000000000'}; }; -- Bardufoss TACAN { display_name = _('ENDU'); beaconId = 'airfield14_1'; type = BEACON_TYPE_TACAN; callsign = 'BAR'; frequency = 113400000.000000; channel = 81; position = { 117734.736203, 106, -159002.606530 }; direction = 0; positionGeo = { latitude = 69.045764, longitude = 18.586586 }; sceneObjects = {'t:00000000'}; }; -- Bardufoss DVOR+DME { display_name = _('ENDU'); beaconId = 'airfield14_2'; type = BEACON_TYPE_VOR_DME; callsign = 'BDF'; frequency = 114200000.000000; channel = 89; position = { 120058.40325, 167, -163708.159663 }; positionGeo = { latitude = 69.064883, longitude = 18.466397 }; sceneObjects = {'t:000000000'}; }; -- Andøy TACAN { display_name = _('ENAN'); beaconId = 'airfield15_1'; type = BEACON_TYPE_TACAN; callsign = 'OYA'; frequency = 109100000.000000; channel = 28; position = { 150255.640500, 4, -254222.831391 }; direction = 0; positionGeo = { latitude = 69.286269, longitude = 16.143767 }; sceneObjects = {'t:00000000'}; }; -- Andøy VOR+DME { display_name = _('ENAN'); beaconId = 'airfield15_2'; type = BEACON_TYPE_VOR_DME; callsign = 'AND'; frequency = 112200000.000000; channel = 59; position = { 150435.995162, 6, -254305.101072 }; positionGeo = { latitude = 69.287822, longitude = 16.141328 }; sceneObjects = {'t:000000000'}; }; -- Tromsø DVOR+DME { display_name = _('ENTC'); beaconId = 'airfield16_1'; type = BEACON_TYPE_VOR_DME; callsign = 'TRO'; frequency = 113800000.000000; channel = 85; position = { 190386.747391, 145, -140242.220054 }; direction = 0.000000; positionGeo = { latitude = 69.702814, longitude = 18.996797 }; sceneObjects = {'t:00000000'}; }; --Alta DVOR+DME { display_name = _('ENAT'); beaconId = 'airfield17_1'; type = BEACON_TYPE_VOR_DME; callsign = 'ATA'; frequency = 117400000.000000; channel = 121; position = { 221498.954094, 1, 27908.980714 }; direction = 0.000000; positionGeo = { latitude = 69.977478, longitude = 23.371758 }; sceneObjects = {'t:00000000'}; }; -- Vardefjell (Mosjøen) DVOR+DME { display_name = _('ENMS'); beaconId = 'airfield18_1'; type = BEACON_TYPE_VOR_DME; callsign = 'VFL'; frequency = 113300000.000000; channel = 80; position = { -215654.999771, 618, -412765.810931 }; positionGeo = { latitude = 65.879508, longitude = 13.307842 }; sceneObjects = {'t:000000000'}; }; -- Mosjøen DVOR+DME { display_name = _('ENMS'); beaconId = 'airfield18_2'; type = BEACON_TYPE_TACAN; callsign = 'MOS'; frequency = 113900000.000000; channel = 86; position = { -215852.697984, 616, -412763.685831 }; positionGeo = { latitude = 65.877756, longitude = 13.308417 }; sceneObjects = {'t:000000000'}; }; -- Kirkenes VOR+DME { display_name = _('ENKR'); beaconId = 'airfield19_1'; type = BEACON_TYPE_VOR_DME; callsign = 'KIK'; frequency = 112000000.000000; channel = 57; position = { 216335.661881, 84, 279276.143526 }; positionGeo = { latitude = 69.723786, longitude = 29.869081 }; sceneObjects = {'t:000000000'}; }; -- Vardø VOR+DME { display_name = _('ENSS'); beaconId = 'airfield20_1'; type = BEACON_TYPE_VOR_DME; callsign = 'VRD'; frequency = 114100000.000000; channel = 88; position = { 293231.183127, 8, 312737.43914 }; positionGeo = { latitude = 70.357628, longitude = 31.047253 }; sceneObjects = {'t:000000000'}; }; -- Sandnessjøen DVOR+DME { display_name = _('ENST'); beaconId = 'airfield21_1'; type = BEACON_TYPE_VOR_DME; callsign = 'STO'; frequency = 112000000.000000; channel = 57; position = { -201777.511861, 28, -449522.901048 }; positionGeo = { latitude = 65.960286, longitude = 12.469314 }; sceneObjects = {'t:000000000'}; }; -- Brønnøy DVOR+DME { display_name = _('ENBN'); beaconId = 'airfield22_1'; type = BEACON_TYPE_VOR_DME; callsign = 'BNN'; frequency = 115300000.000000; channel = 100; position = { -255826.390352, 2, -468859.820763 }; positionGeo = { latitude = 65.457086, longitude = 12.214417 }; sceneObjects = {'t:000000000'}; }; -- Hammerfest DVOR+DME { display_name = _('ENHF'); beaconId = 'airfield23_1'; type = BEACON_TYPE_VOR_DME; callsign = 'HMF'; frequency = 112400000.000000; channel = 71; position = { 302980.063217, 367, 36499.561332 }; positionGeo = { latitude = 70.704192, longitude = 23.690586 }; sceneObjects = {'t:000000000'}; }; -- Stokmarknes VOR+DME { display_name = _('ENSK'); beaconId = 'airfield24_1'; type = BEACON_TYPE_VOR_DME; callsign = 'SKG'; frequency = 112800000.000000; channel = 75; position = { 75496.377074, 1, -305477.120326 }; positionGeo = { latitude = 68.578325, longitude = 15.034969 }; sceneObjects = {'t:000000000'}; }; -- Seida VOR+DME { display_name = _('Seida'); beaconId = 'airfield25_1'; type = BEACON_TYPE_VOR_DME; callsign = 'SDA'; frequency = 113600000.000000; channel = 83; position = { 263860.883040, 272, 203621.362394 }; positionGeo = { latitude = 70.234261, longitude = 28.070178 }; sceneObjects = {'t:000000000'}; }; Edited May 26, 2024 by drPhibes 1
Rudel_chw Posted May 26, 2024 Posted May 26, 2024 15 minutes ago, drPhibes said: I have chosen to not publish a complete beacons.lua, since that would revert any improvements made by Orbx if I don't keep it updated, so you'll need to paste the code below into yur beacons.lua file yourself. Thanks a lot, I agree that this approach is better, tough I will still implement it as a User Mod to have the ability to enable/disable it easily. A question cames to mind .. is it possible to add RSBN and PRMG beacons in the same way? ... I believe that the Mig-21 does not use the Map's Beacons.lua, but has its own implementation, do you know if that is correct? best regards, Eduardo For work: iMac mid-2010 of 27" - Core i7 870 - 6 GB DDR3 1333 MHz - ATI HD5670 - SSD 256 GB - HDD 2 TB - macOS High Sierra For Gaming: 34" Monitor - Ryzen 3600 - 32 GB DDR4 2400 - nVidia RTX2080 - SSD 1.25 TB - HDD 10 TB - Win10 Pro - TM HOTAS Cougar Mobile: iPad Pro 12.9" of 256 GB
drPhibes Posted May 26, 2024 Author Posted May 26, 2024 I haven't experimented with RSBN/PRMG personally, but I have been approached by a few people who have started adding them to the Russian airbases, so I assume that it's just as easy as adding ILS and VOR/TACAN. You can find the frequencies for the PRMG/RSBN channels using type = BEACON_TYPE_PRMG_LOCALIZER frequency = 905100000 + 6825000 * (channelNum - 1) type = BEACON_TYPE_PRMG_GLIDESLOPE frequency = 939600000 + 6825000 * (channelNum - 1) type = BEACON_TYPE_RSBN frequency = 801000000 + 1000000 * (channelNum - 1) I think the Mig-21 was released before RSBN/PRMG was implemented in DCS, so LNS chose to use a local beacon database, located in \DCS World\Mods\aircraft\MIG-21bis\Cockpit\Systems\R_NAV_data*.lua. It's similar to what Razbam did with the AWLS system in the Harrier before ICLS was added to DCS. 1
Tarres Posted May 26, 2024 Posted May 26, 2024 (edited) The MiG-21 uses a system derived from when it was a Lomac mod, so every beacon, even NDBs and markers are coded for the mod. RSBN system from ED has been present from Blackshark v1.0 onwards, but change the 21 code to the real one rsbn/prmg system implemented by ED from Blackshark 1.0 onwards required to rewrite basically all the code of the 21. Edited May 26, 2024 by Tarres
Recommended Posts