Search the Community

Since it's easiest to create DTCs or Datacartridges for the Mirage from F10 Map Markers, I've developed a small Moose-based script to create DTC files from those markers. Enjoy! You can find the script here: https://github.com/FlightControl-Master/Moose_Community_Scripts/blob/main/Scripts/M2K_Datacartridge_Creator.lua Use a newer Moose build from here: https://github.com/FlightControl-Master/MOOSE_INCLUDE/blob/develop/Moose_Include_Static/Moose_.lua Description: Mirage 2000C Datacartridge Generator v1.0 Author: Applevangelist Prerequisites * Familiarize yourself with M2K data cartridges or DTCSs in the flight manual, section 19-6 * Desanitize the mission scripting environment in here C:\Program Files\Eagle Dynamics\DCS World.Openbeta\Scripts\MissionScripting.lua or here C:\Program Files\Eagle Dynamics\DCS World\Scripts\MissionScripting.lua depending on which version of DCS you are running Add two minus signs in front of the sanitizeModule lines, they should look like this: --sanitizeModule('os') --sanitizeModule('io') --sanitizeModule('lfs') This is necessary, so the file can be written to disk * Ensure that the directory Datacartridges exists here C:\Users\<yourname>\Saved Games\DCS\Datacartridges or C:\Users\<yourname>\Saved Games\DCS.openbeta\Datacartridges depending on which version of DCS you are running * Note - Currently the Mirage does not detect freshly created DTCs in-game. It will find the cartrige after the next restart, however. Creating a data cartridge While in-game, press F10 to bring up the map. Place a marker on the map and enter this text: "M2K New CAP_Kutaisi". This will create a new data set called "CAP_Kutaisi" - this will show up on the cartridge in-game later on when selecting a cartride. Mission names must not contain spaces or pattern matching magic characters (http://www.easyuo.com/openeuo/wiki/index.php/Lua_Patterns_and_Captures_(Regular_Expressions)), i.e. none of these: %,-,.,?,+,* "M2K" is the keyword which always needs to come first to detect an entry. Creating a new data set deletes existing entries, so if you made a mistake you can start anew. Assuming we are starting from Kutaisi, let's create our first waypoint. Put a marker on the start of the runway 07 in Kutaisi and enter this text: "M2K BUT1 name=Kutaisi cp=67". This will create our first waypoint (BUT) with the number one. The runway heading is cp, in this case 67 degrees true. The altitude is automatically taken as land height at this point. With cp as a parameter, rd (route desiree) is automatically set to equal cp, and pd (glidepath) is set to 3.5. Create another waypoint on the map, by placing a new marker on the map, e.g. "M2K BUT2 alt=5000". This creates waypoint two, with an altitude of 5000 meters. You may create up to 20 waypoints for a single plan. 1-10 waypoints will be stored the the Mirage's INS system under BUT 11-20. If you use more than 10 waypoints, the Mirage will start adding waypoints at BUT1, overwriting whatever is there. Known keywords (all optional) for BUT creation are: "alt", "cp", "pd", "rd" and "name". The format is always (except for name) "key=xxxx.xx" where x are numbers and . the decimal separator, e.g. alt=5000.23. The format for "name" is "name=abc" where abc is alphanumeric, no spaces, no special characters. Entries are separated by spaces. Special keywords are "FT" to switch to foot for altitude entries and "KM" to switch back to meters. Example with multiple parameters given "M2K BUT4 alt=25000 FT rd=267" - BUT four, altitude 25000ft, route desiree 267 degrees. Creating a new BUT with an existing number will overwrite the existing BUT, i.e. you can correct entries this way. Creating BAD entries If you want e.g. to use this system to plan for a preplanned strike, you can amend a BUT with BAD (delta deviation) information. This is done like so: Let's assume you have created BUT3 to be your ingress point for the strike: "M2K BUT3 alt=150 FT rd=90". Now put a marker on the target area in the map and add this text: "M2K BAD3". This will amend the info for BUT3 with the delta distance information and delta altitude (ground height automatically assumed). Optionally you can use the keyword "dalt" to give the delta altitude yourself: "M2K BAD3 dalt=-56" (foot in this case, because we switched to imperial prior. Creating a new BAD with an existing number will overwrite the existing BAD information, i.e. you can correct entries this way. Saving Place a marker and add this text: "M2K Save". This will save the DTC data to your directory. The filname will be "mapname_missionname.dtc", e.g. "Caucasus_CAP_Kutaisi.dtc"

Hi, For a training mission, I would like to spot easily a convoy of 5 units by using a radio call to put a smoke marker on one of the unit. If a unit is dead, the smoke should appear on another one. How can I do that? I start with : ONCE (Radio call, NO EVENT) > > RADIO ITEM ADD FOR GROUP (2, Request smoke, 1, 1) SWITCHED CONDITION (AAV-7) > FLAG EQUALS (1,1) / UNIT ALIVE (AAV-7) > SMOKE MARKER ON UNIT (AAV-7, RED) / FLAG OFF (1) From that, I have to cover all possibilities for each units to be dead or alive, which is a huge work. There should be a better option. Thanks for your help, Vincent

I noticed the Red dot with a '1' in it, over the Modules button at the top left of the main screen. There is nothing new for me to install.. I didn't expect there to be as I had not purchased anything recently. The Red dot does not show if I run the normal OB DCS.