Minsky

Here are two important outtakes from the real-world A-10 manual: First, setting the ILS approach course is mandatory, period. Second, if the computed steering guidance (incorrectly referred to as "ILS needles") becomes unreliable, the pilot should disregard it and fly the raw ILS signals (outlined in red). P.S. On your last screenshot you are about 150 feet below the glideslope. Of course it wants you to climb.

Why would it be accurate if you haven't set the course?

"Another desert map"© added. > Download <

Despite all the ridiculous excuses from the PR team, it was quite obvious that this is technically doable. Thanks to all artists and programmers at ED who pulled this off

With the map itself? None so far. Various modules (Hornet, Viper, Apache, A-10C II, Su-25T, TF-51D and probably others) got the usual assortment of Instant Action activities, but no proper missions.

In real world both runways share the same frequency (108.90). Even if this wouldn't work in DCS, RWY09L ILS must be changed to something else, since 108.80 is not a valid ILS frequency.

RWY18 ILS at Erbil has incorrect frequency: 109.20 instead of 109.10

This might help: https://www.digitalcombatsimulator.com/en/files/3325364/

If you're so reluctant to change these helipads to non-clickable icons, then maybe ask ED to add a new aerodrome type for the Mission Editor & F10 map? With smaller icon and text, so they won't be so obtrusive and mix up with "real" aerodromes. With more and more heliports added to new maps, this feature is long overdue:

See the title.

See the title.

According to charts, Hatzor should either have VORTAC, or TACAN with a co-located VORDME beacon. Currently in DCS only the DME (no VOR) beacon is implemented.

Was it really necessary to add them as a full-fledged "aerodromes"? They clutter the already cluttered map view to the point of being unreadable. Also, the newly added airfields, that occupy the 220-223 ID range, cannot be used with the nav system of the Flaming Cliffs aircraft (Su-25T etc.). When swiping the IDs in the POS/ПОС mode, it stops at around #211 and jumps back to #1. I would really like them to downgrade those helipads to simple map icons.

3+ years later but it's finally fixed.

It was added in a recent patch for some reason.

Thanks for the newly added helipads guys, much appreciated! Can you please also mark them with map icons, like it's done on other maps? They'll be much easier to find, considering many are placed at incorrect locations. Would also be nice to make them less generic by replacing certain pads with a more civilian variant (no sandbags etc.) And while you're at it, maybe also add icons to the unmarked airstrips? It's impossible to spot most of them on the map unless you know exactly where to look.

There are two identical VOR beacons at Mount Pleasant, copied & pasted on top of each other.

Can't say I'm 100% happy with it, but it certainly added character and made the map look less barren & generic. Although there's plenty of room for improvement, especially in colour matching and lighting.

This tool can remove all modded objects from the .miz file: https://www.digitalcombatsimulator.com/en/files/3322208/

This one perhaps?

Thank you! The gist of it is that when a frequency is not explicitly declared by the developer, it gets automatically assigned by the program. When developer changes frequency or adds a new airfield, that program then must reassign remaining frequencies to remaining airfields, which often lead to these reshuffles. The obvious solution would be to manually declare all frequencies, but that's either too bothersome, or technically impossible, or a mix of both. So the devs usually populate the VHF band with whatever they found in charts/google, and leave the other bands to chance. The above is true for every map in DCS, not just Syria. Ugra gets the most blame because their maps are more popular and more often receive major updates.

For some reason they've made the frequencies .05 MHz apart in DCS:

@ac5 Something has been lost in translation perhaps? He could've meant that they fixed it internally and will include the fix in the next patch:

Just tried this in a clean mission with every possible Hornet state: airborne, runway start, hot start, and cold start. Each state with and without radio presets, with and without easy comms. Never got any response from Manston. The "abort takeoff" trick obviously doesn't work either, since the ATC doesn't answer. Randomly called other airfields (happened to be Detling and Lympne) and got normal response.

Thanks for combing through this. Most of them are now aligned okay, but please check RWY26 ILS at Ben-Gurion.