Apple

Correct. Corrected to "true"

Not sure the file supports "td" (and what is the format?), Done

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"

Also doesn't work for the F16 - I spawned two groups, added the Link16 IDs in the DED - other than in SP they are neither becoming part of my group nor is further information available: Eventually the groups are just added with https://wiki.hoggitworld.com/view/DCS_func_addGroup like normal. The data is read from the template.

Active runway needs a runway name, like "07R" or "21" not just "R". Watch your dcs.log for errors. Stretch out starting the instances a bit by using __Start(3) instead of Start(). For questions - join our discord.

It has a basic balancing, ie no ground attacks when there’s no players, players are blessed with extra interceptors etc. indeed not many ppl have the map; it got a lot more green wood area in the latest patch.

[Original threat lost, apologies!] Situational Overview Following a REDFOR insurgency post the Falklands war, a new Caudillo has taken over larger parts of the southern tip of South America. BLUEFOR has been tasked to sweep the RED zones South to North and re-establish the previous order. USMC has landed close to Ushuaia and Port Willams and has established a bridgehead. The HMS Invincible provides protection in the channel, the USS Forrestal is crusing east of the mainland. CAP operations has been established from Ushuaia and CTLD/CSAR helicopter operations from Ushuaia Helo Port and FARP London. USMC SOF have been inserted deep into the Phase-One-Zone Rio Grande and provide target information and target markers. https://www.digitalcombatsimulator.com/en/files/3328279/ Background This late cold-war mission is set on the South-Atlantic/Falkland maps. Sound output leverages Text-To-Speech-Generation(TTS) via SRS, best via Google (own account needed) or Windows Desktop (far less voices). For SRS-TTS to work on your PC, consult this guide: https://github.com/FlightControl-Master/MOOSE_GUIDES/blob/master/documents/Moose TTS Setup Guide.pdf Before running, you need to setup the SRS and Load/Save paths correctly to match your system and/or server, and create a folder for persistence. Read and follow the instructions in the README.txt file on how to do that! Help is available via the MOOSE Discord https://discord.gg/aQtjcR94Qf Version history * Features SRS-TTS * Features Persistence * Build with Moose * V1.41p1 - Phase One Initial Community Release * V1.42p1 *** Removed dependency on WWII Assets and A-4-EC. *** Made the config an external file, see README.txt for details on how to adjust. *** Repaired ground saving and loading. * V1.43p1 *** All F1CE and M2K now belong to France, not the US *** SOF messages timing changed * V1.44p1 *** Improved Conquer Airbase Logic *** Exchanged AWACS Voice (now faster) to avoid overlaps * V1.45p1 *** Marker creation on conquered Airbases for CTLD loading zones now lighter. * V1.46p1 *** Added two Spanish F1EE in Puerto Williams SRS Output Demo from the Mission (YouTube)

"Operation Gaucho" Multiplayer Mission. This mission uses newer Moose Classes and Text-To-Speech conversion via SRS extensively. The video demonstrates some key speech outputs. Voices generated with Google TTS Join our Moose Discord: https://discord.gg/gqxpDHJ36E Mission Download: https://www.digitalcombatsimulator.com/en/files/3328279/ Ciribob's excellent SRS-Tool for DCS: https://github.com/ciribob/DCS-SimpleRadioStandalone

Thanks @Flappieappreciated. Still, it looks the code was touched in 2.8 bc the behaviour is now different (needs a name in MP or stops after the 1st loop); any reason why this was altered?

From my testing, ADF beacons aka trasnmission must have a name now, i.e. the last paramter which was kind of optional until now, must be there: trigger.action.radioTransmission(Sound, Vec3, 0, false, Frequency, 1000, nameofbeacon) Then you can "renew" the ADF beacon with another trigger of the same or another name. Without name - no dice on renewal. Why do we "renew" beacons? Because in Multiplayer it was running only 30 seconds straight, then stopped, no matter if loop was true or false or how long the actual sound file was. But preliminary testing shows the looping is working now in MP, too. Cool, Good Job - but why didn't anyone tell us?

Can confirm the issue is replayable for SA-342 Gazelle helicopters.

If you're using Moose, commands almost never start with small caps, it should be SetRadioRelay.. SetTACAN and SetTower ...

Okay so be it.

No idea mate if it ever worked. I know it's not working on current beta

Anyone looking at this?