Ramsay

AFAIK most of the RSBN and PRMG in the eastern zone are missing / wrongly coded. Only ED's L-39 uses the map's beacon.lua (MiG-21 has it's own definition files). Changes/additions required are discussed in this thread with an example beacon.lua that adds several missing RSBN beacons (Russian TACAN equivalent).

"Out of the box" there are only GermanyCW missions for ED's own aircraft i.e. there are none for 3rd party aircraft - I assume these might be made/added by the 3rd party developers themselves. There are 3x missions for the Hornet and 10x missions for the Viper (note that not all of ED's aircraft have GermanyCW missions i.e. some WWII aircraft, etc.) Example of the currently included F-16C IA Missions

Searching in DCS's Mods/Aircraft folder shows there are currently 88 GermanyCW .miz missions that ED have added to their own modules in support of the new map. Most of these are simple Free Flight and similar missions with 2-4 mission per aircraft. Here's a couple of examples Mi-24P TF-51D Yak-52

TL;DR: In DCS, ATC will only enable ILS for the "active" runway, in this case RWY 30. Detail: Although you have correctly tuned your ILS to 111.70 and set CP/PD to 115°T - Mineralnye Vody is NOT transmitting an ILS signal for RWY 12 in this mission. As the M-2000C is not receiving an ILS signal - selecting APP mode will not display a synthetic extended runway centreline or runway silhouette. You can confirm if an ILS signal is being received by turning up the ILS volume on the audio panel and/or checking if the ADI's yellow ILS guide "bars" are visible.

When entering data into the CDU, the CLR key toggles East/West at the start i.e. before entering degrees and minutes.

The DCS AV-8B's AWLS compatibility with "regular ILS" is purely fictional - the "real" AWLS is a microwave landing system and uses the same 20 channels as the Hornet i.e. ICLS. As there is no way in RL or DCS to enter an ILS frequency via the cockpit or a MFD page, the only way to do so is by editing a DCS AV-8B config file - "DCS World\Mods\aircraft\AV8BNA\Cockpit\Scripts\RadioNav\AN_ARN128_config.lua" Comment In IFR conditions - consider flying TACAN approaches as a more realistic/plausible real life SOP. AFAIK due to the current dispute between Razbam and ED (where Razbam and their coders/artists are not receiving their portion from sales of their aircraft modules) - it is unlikely the AV-8B code will be updated to support the new map. Note: there is a slim chance a Razbam dev will do the work for free and ED will agree to push the change as part of an official patch but I wouldn't hold your breath.

TL;DR: • SimAppPro creates a custom Viewport file "DCS World\Config\MonitorSetup\wwtMonitor.lua" • Many modules use the same default Viewport naming scheme (i.e. "LEFT_MFCD", "RIGHT_MFDC" and "CENTER_MFDC"). • The Mirage F1 uses "LEFT_MFCD" and "RIGHT_MFDC", so once you have setup SimAppPro for another aircraft that uses the same MFD viewport names i.e. A-10C, F-16C, FA-18C, etc. - the Mirage F1 radar screen will be exported. Detail When setting up your MFDs using SimAppPro it creates a customised Viewport file "DCS World\Config\MonitorSetup\wwtMonitor.lua" You can then copy it to "Saved Games\DCS\Config\MonitorSetup" and customise SimAppPro's default settings (in your saved copy) to your own preferences i.e. I set the Kiowa's exported MFD's to a 4:3 aspect, etc. There are lots of videos and posts explaining how to Export DCS Viewports - this one gives a list of modules and the viewport names they use (but I'm sure there are many others). AFAIK it's not easy to export the F-4 Phantom Radar to an external Viewport/MFD ATM however Heatblur do plan to add viewport support later. https://forum.dcs.world/topic/349414-export-to-second-monitor/#findComment-5569012

The synthetic runway is drawn and scaled on the HUD using the height above the airfield (QFE), Glide Slope (PCN waypoint info), runway/ILS bearing (PCN waypoint info) AND that you are "on" the LOCALISER and/or GLIDE SLOPE signal. It does not reference or use the waypoint's coordinates i.e. when landing at Vaziani (1500 ft MSL) if your altimeter isn't adjusted to QFE, the synthetic runway will be drawn smaller and further away as higher in glide slope --> greater distance from landing point. No, TACAN does not have the Glide Slope and Runway Direction required or generate an ILS beam. No, the radio navigation used in the M-2000C is backward compatible with earlier models - so can provide steering guidance to TACAN Offsets (VADs), etc. but these are limited to being functions of the HSI.

Do you have a waypoint (but) selected with the runway's (true) direction and glide slope programmed ? Details Assuming the ILS is transmitting. 1. If the landing waypoint was setup in the ME Select the landing waypoint (CP/PD will already have the Runway Heading and Glide Slope filled in) Contact ATC or check the mission briefing for the QFE and set the altimeter accordingly Set the ILS frequency (adjust ILS volume / check audio ID / HSI flags)* Set APP mode on the PCA Land using the ILS and HUD HUD localiser guidance will appear with localiser signal and aircraft heading is within +/- 6° of Runway Heading The HUD's Synthetic Runway will appear when BOTH localiser and glide slope signals are being received. * if the runway's ILS is not working you will not have the HUD localiser/synthetic runway symbology 2. If the landing airport has not been set up in the ME Contact ATC and check which runway is active and it's QFE Set the ILS frequency (adjust ILS volume / check audio ID / HSI flags)* set the altimeter to QFE (ATC usually gives it in inHg, so you'll need a table to convert to mbar/hPa) Select the active waypoint you are going to use to land (1-20), it's co-ordinates are unimportant (say waypoint 19). PREP the waypoint runway info on the PCN (PREP 19 INS) turn the PCN selector to CP/PD (RH/DS in the English cockpit) enter the runway's true heading in the left field i.e. 179.0°T enter the desired glide slope in the right field i.e. 3.0° Set APP mode on the PCA Land using ILS and the HUD This is covered in Chuck's M-2000C Guide (Part 13 - Navigation & ILS Landing, Page 318) https://drive.google.com/file/d/1jmp9ueZo9xOPyGzo3YO0AnFYEH-5Iotr/view

Ivank created a list of depression settings for various Mk82 profiles in this post - I haven't tested them but they should provide a good place to start from i.e. ~140 mils

The default route i.e. route 1 (named "ME" for Mission Editor), is the regular DCS route created in the ME i.e. waypoints 0 to 4 in the example mission. The Kiowa can have 2 other pre-programed routes, these are created using the ME drawing tool with the drawn lines given special names that the DCS Kiowa recognises "KW-ROUTE2" and "KW-ROUTE3". These drawn lines add additional waypoints after the last ME waypoint i.e. Route 2 might get waypoints 5 to 9 and Route 3 - waypoints 10 to 13.

Not as far as I know. It's covered in the last few pages of the DCS OH-58D User Guide i.e. 24.5 and 24.6 (pages 242-244) and an example mission "DCS World\Mods\aircraft\OH-58D\Doc\kw_demo_mission.miz" to study, that uses the ME's drawing layers to create battlefield graphics, etc. The OH-58D Silent Thunder Campaign also makes use of the ME's drawing layers if you want more examples. Comment If you need a "simple" video walk though using the ME to create these - I guess I can make one tailored to your needs but I'll need to revise the exact process, layers, etc. myself before making it (as it's not a feature I've used that often - other than testing).

Old youtube videos are out dated as the DCS MB-339A's sight size and depression adjustments didn't match the real aircraft and documentation until recently. These were fixed as part of the 30th October 2024 DCS Patch (however the manual and included training missions need updating to match this improved (realistic) behaviour). https://forum.dcs.world/topic/341576-dcs-changelog-and-updates-2024/#findComment-5544747 Comment It's possible the 0-1 hundreds thumb wheel's limitation is unintended (as there were some issues with how the depression settings effected the sight - since fixed), so only an IFE dev can say for certain if the current behaviour is intended.

This may be intended as +200 mils likely falls outside the gun sight's field of view ?

This is NOT a bug - what you see modelled is a launch tube (the missile is carried inside).