drPhibes

I wouldn't touch wubuntu with a barge pole. It's just Kubuntu with Wine, a Windows-like KDE theme, some stolen Microsoft assets and added spyware. Trademark and copyright violations aside, the people behind it seem quite sketchy. TL;DR: you're better off with a regular linux distro + Wine if you want to play DCS (it works reasonably well according to the hoggit nerds: https://wiki.hoggitworld.com/view/DCS_on_linux).

You are right about the TACAN being missing, but you are mixing up the channel with the DME located right next to it. Andøya TACAN (ID: OYA) = 28X. Source: https://ais.avinor.no/no/AIP/View/135/2024-11-28-AIRAC/html/eAIP/EN-ENR-4.1-no-NO.html#ENR-4.1

30MB/s here, so it's more likely an ISP issue than an ED issue.

Who said anything about the command line? Those changes are made in config files that you can edit with any text editor.

The net upgrade size is much smaller than the total ammount of GB downloaded. If the devs add 1 byte of data to a 2GB file, 2GB is downloaded, but the actual change in disk use is 1 byte. Temporary space for the download and installation is the big issue here.

Updates usually drop around 16-17-ish CEST.

2 years.

Yes.

Use of precision landing aids at regular airports was apparently not a priority when the US Navy ordered the F/A-18. ICLS and ILS are completely incompatible, so there's no way for "our" Hornet to use the ILS at Anderson. The best you can get is using a mod with ground based ICLS beacons.

Your presumption is wrong. When you have two parallel runways (of an equivalent length and standard), it is quite common to use different runways for takeoff and landing.

It was abandoned when the Turkish invaded the northern part of the island in 74.

He might be referring to the F16 being available to Finland and Sweden in DCS, but with no fictional liveries to match.

Is the "VOR-ILS/OFF/TACAN and OMNIBEARING" selector (switch 21 on p.19 in the manual) set correctly?

A relative from Troms refers to everyone living south of Narvik as "søringa", so I guess the southernmost cities with airports in the Kola map would be in southern Norway by that standard

And from that list, only the Vigen and F1 are "European strike platforms form the 60/70ies". Mirage 2000C: multirole, and entered service in 84. F4E: Not European, and technically it's more of a multirole aircraft than a strike aircraft. Hawk/C101/MB339: trainers with a secondary offensive role. Harrier II: While the AV8B is based on an European design, and a strike aircraft, it is not a 60ies/70ies aircraft (it entered service in 85).

I found a DVOR (without DME) at Kutaisi, which has a much more accurate model. It's basically good enough to pass for both a DVOR with and without a co-located DME.

Being a professional in the field (15 years in the r&d dept of a major navaid manufacturer), I have a few suggestions for improvements for the 3d models used in the various DCS maps. All maps use the same models, so I assume that they are part of a standard asset pack for the terrain developers. These are minor details that only the biggest nerds will notice, but I thought I'd let you know anyway. Localizer antenna: The localizer antenna used in DCS is clearly meant to be a log-periodic dipole antenna (LPDA), but the 180° phase shift between each radiating element in the antenna means that it can’t be constructed like the model in DCS, where the staggered up/down position of the radiating elements is symmetrical about the center line of the antenna. This website has a nice figure showing how a LPDA is constructed: https://3g-aerial.biz/en/online-calculations/antenna-calculations/logperiodic-lpda-antenna-online-calculator This is also how all the different localizer LPDAs used by the major ILS manufacturers are constructed. Other than the misplaced radiating elements on one side of the antenna, the general shape of the antenna is fine(-ish). DVOR: The diameter of the counterpoise (the elevated platform that the antennas are mounted on) is a little small (~25m in DCS, while they are ~30m in real life). The 48 sideband antennas should be mounted equally spaced in a ring with a diameter of 13,5m, but in DCS it is ~9m. The sideband antennas are the wrong type. In DCS they are regular horizontal dipoles, but all DVORs use alford loop antennas. The shape of the radomes can vary, but they are usually cylindrical or square with a conical or pyramid top. Here are a few examples (with dimensions in the PDF): https://www.antennas.com/?s=dvor&post_type=product https://net-com.bytom.pl/anteny_lotnicze/AT-DVOR%20011%20en.pdf The DVOR carrier antenna is missing in DCS. It should be mounted in the center of the counterpoise, and it should also be an alford loop antenna. The DME, antenna which sits in the center of the counterpoise in DCS, can be mounted coaxially with the carrier antenna in some cases, but it is also common to place it at the edge of the counterpoise. The lattice mast should not be poking up through the counterpoise.

It looks a lot like the panoramic camera described here: https://www.airvectors.net/avmirf1.html

If you buy all the regions separately you get exactly the same product as if you buy the complete map, just at a higher price.

The following methos works fine: 1. Just copy the whole DCS directory to the new computer. 2. Run a repair. 3. Copy over the \saved games\dcs world\ folder to the new computer, overwriting all files (so you don't have to set up control assignments). Or you could skip step 1 and 2 and do a regular install if you don't mind spending hours downloading potentially hundreds of gigabytes of content all over again.

The turorials do not take months to complete. In fact, they are much quicker than your current trial and failure-method.

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.

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'}; };

Maybe your time would be better spent by reading the manual (or Chuck's guide)? It's a much more efficient way of learning than trying, failing, and asking on the forums for every single feature in the aircraft.

What makes you think that the 3D artist responsible for making the pilot model would have been working on the code related to the DTC or Lantirn if the pilot body wasn't a priority? It's like expecting a plumber to fix the electrical wiring in your house.