Ramsay

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).

IIRC ~80 KIAS for comfort and range (it's also approx. best autorotation speed for glide distance). 125 KIAS is the MAX VNE with crew doors fitted. • With weapons or a GTW above 4,500 lbs - VNE is 120 KIAS. • Without the doors - VNE is 110 KIAS = ~126 mph. No. AFAIK the fastest configuration would be to set the DCS Kiowa up as a Fort Rucker trainer (without weapons or the MMS) and was used in RL to train autorotations, etc.

Seemed ok when testing at Kobuleti (touch down point was about 1500 ft from start of runway), which airfield are you seeing this at ? Tested DCS 2.9.14.8394

The included training missions were created before changes were made to the avionics i.e. MFD display logic with RL limitations and a newer version of the TPOD/software. Unfortunately "M13: SENSORS AND TARGET DESIGNATION" is one of these - AFAIK most of the training missions were planned to be updated once a TDC designation "logic rework" was completed. However AFAIK the current ED/Razbam dispute has put all this on hold. Comment If looking to learn the current module, while not perfect (as they are a couple of years old), the best I can recommend (as a foundation) is • Chuck's AV-8B Guide along side an updated youtube guide such as • deephack's DCS AV8B Tutorial series or similar. Then if you have a particular issue i.e. dropping JDAMs, you can come back (to the forums) with a more specific request i.e. I've followed video xxx and can't designate, don't get HUD launch parameters, etc. with a screen shot(s) and/or a track file (to see if it's a know bug, limitation or procedural error).

Usually happens when the IR MAV isn't SOI (so slaves to the HUD flight path marker or target point/waypoint, etc.) - check the MFD reads IRMV, if not cycle the SSS or cage/uncage button as required until it does. If you continue to have issues please share a short track or video. Perhaps the tips in this old thread will help ?

The IRCM (disco ball, etc.) and L2MUM incompatibility is NOT a bug, I forget the exact details but IIRC the satellite antenna, etc. used by the L2MUM data link is fitted in the same location as the disco ball, so IRL an older Kiowa with IRCM cannot support L2MUM.

My guess is that it depends on your definition of "broken" i.e. the module has had "minor" issues since release (such as the HSI, GPS and TACAN using a mix of TRUE and MAG bearings) and it's taken IFE a long time to rectify them. DCS's 2023 multi-thread core update also broke some cockpit animations (i.e. canopy handle) that IFE retroactively "fixed". There's always been a minor bug(s) since I've owned the module, whether it be the gun sight mils or the current cold start ADI bug. However, to date, IFE have always found the resources/time to push fixes and the module continues to improve over time. Comment Although necessary to be patient for IFE's updates (i.e. the flight director, etc.), IMHO the MB-339 is definitely worth picking up in a sale (if looking for a modern/western trainer/COIN op platform). YMMV.