drPhibes

That sounds like an excuse I'd use if someone asked me to help out with beach balls, ballons and whatnot.

@MAESTR0: let me know if you're interested in some acurate info about the ILS at Damascus RWY 05R. I can see from the screenshot that it has the standard DCS fibreglass glide path tower with a Sideband or Null-ref antenna system, while the actual system at 05R is a M-array Normarc system on a lattice mast. Other than this minor nitpicking, the screenshots look great. Keep up the good work!

The US Navy did. I don't know if it's still in service. https://www.navy.mil/navydata/fact_display.asp?cid=2200&tid=600&ct=2

Please check your sources. 1. The USMC source you refer to says nothing about the AV-8B carrying any of these weapons. AGM-88 is mentioned once in the document, and that's in the table describing firing range requirements. 2. Regarding link #2: I don't know what kind of fantasy land the author of that article lives in, but it is pure imagination. The RAN has never operated any type of Harrier.

Yes and no. If there is an ILS for each runway direction, an interlock (which switches off the ILS for a runway if the reciprocal runway direction is active) is an ICAO requirement for CAT II and III approaches (Annex 10, 3.1.2.7), and it is recommended for CAT I. For a runway equipped with a single ILS, the rules of operation can either be decided by the local ANSP or airport. The issue in DCS is that the logic for selecting the active runway direction is flawed/suboptimal.

A good example of the opposite was the wiki page for the AV-8B, which until recently claimed that it could carry the AGM-88 and AGM-84, neither of which is true.

https://www.deutsches-museum.de/flugwerft/sammlungen/ IIRC the technical museum in Berlin also has a few aircraft on display (in addition to all the other interesting exhibits). UK: RAF Hendon IWM Duxford I haven't been to Cosford, but it should be worth a visit.

Hmeymim = Bassel Al-Assad, so it's there, just listed under the wrong country. There were a few screenshots from Hmeymim on Ugra Media's website before it disappeared.

King Hussein Air College is in Jordan (Mafraq Air Base), and as far as I can see, the only Hatay in the area covered b the map is in Turkey. King Hussain Air College gives a good indication of how far south the detailed part of the map extends. The project description previously available at Ugra Media's now dead website mentioned Irbid and Jerash in the south, and Gaziantep in the North, so with a map size of 600x500km I'd expect it to go as far east as approximately Deir ez-Zor.

Qabr Al-Sitt air base: https://www.google.com/maps/place/33%C2%B027'30.0%22N+36%C2%B021'23.0%22E/@33.4580978,36.3574373,660m/data=!3m1!1e3!4m5!3m4!1s0x0:0x0!8m2!3d33.4583333!4d36.3563833

The Win buttons are available as modifiers, so this is a feature, not a bug.

Any kind of benchmark based on a piece of software that is in constant development (with frequent reports of performance changes from update to update) is completely worthless.

So Deka and/or ED should spend their valuable time changing parts of their software because a server admin doesn't listen to your "highly requested" (sic.) suggestions? Sorry to say so, but the world doesn't revolve around you.

Several of my friends who previously shot the original Shadow in IPSC Production have upgraded to the Shadow 2, and they all seem to be pretty pleased with it. The only real weak spot is the slide stop pin, which breaks on all CZ75s and derivatives (Tanfoglio etc) after a few thousand rounds.

Three.

Noope... https://www.army.mil/article/225257/aces_fielding_upgrades_to_army_command_units

The technical term for a TACAN without DME is "switched off" or "out of service". A TACAN works by amplitude modulating bearing info on the DME reply pulses.

Exchanging opinions is fine, but you have to realize that not all opinions have equal value. If I have to choose between what BIGNEWY or someone else from ED or a 3rd party dev. writes about the status of a project, or the uninformed opinions of people with no insight into the development of a module, I'll stick with the official news. I'm not pointing at anyone in particular here, but the ammount of Dunning-Kruger symptoms some users show in in these forums is borderline painful. Good thing I'm already a misanthrope...

There may be multiple development builds used for different stages of testing (e.g. a release candidate build and a devlopment build, and perhaps one for Vulkan testing and one for integration into a new smart toast iron), so the fact that you don't see a certain terrain in the mission creation dialog in a video demonstrating a new module means nothing.

Just out of curiosity, what did you think this message meant when you ordered?

There have been enough cases of attention seeking "modders" passing off ther peoples work as their own. Expecting people to be honest, especially on the internet, is unfortunately not a good idea.

Check your wind direction. The ILS is interlocked off if the wind direction dictates that a different runway direction is the active runway, or if the wind speed is too low. I tested it with a 10kt headwind (mission editor wind direction approximately 320°), and the ILS at TTR RWY 14 works fine in the F-16 with the latest OB release (2.5.6.47224).

108-111.975 MHz is the whole band allocated for the localizer. When the ILS standard was first defined in Annex 10, there were just 20 channels, starting at 108.1 and continuing up to 111.9 in odd decimal intervals. Later on, the channel width was made narrower, allowing 20 new channels at f+50kHz. The only invalid LOC frequencies in the PG map last time I checked was two runways at Al Dhafra and Bandar Abbas, so there are plenty of other runways where you can pratice ILS landings in the F-16. The frequency separation between carriers that you quote isn't really relevant. It relates to the spacing between the course (COU) and clearence (CLR) signals for dual frequncy localizers. In a dual frequency LOC, in addition to the main fan-shaped beam (COU, approx ±10° width) radiating from the loc array, you also have a CLR signal (±35° width, with a null at the center), whose only purpose is to give a full right or left deflection in the CDI when you are outside, but near, the coverage area of the COU signal. The frequencies are offset far enough apart to avoid any intermodulation problems between the two carriers, while still still remaining inside the channel width of the receiver.

Do you have any plans of fixing the relevant beacons.lua entries as well? It has been reported multiple times in the PG bugs & problems section.

Those aren't valid localizer frequencies. The bug has been reported, but ED hasn't done anything about it yet.