Data cartridges terrain choice

[RockMyRoot]

I took my time to experience the data cartridge function on M2000C and I absolutely love it. I use it mainly to get my favorite waypoints in online servers and never get lost. 

I use the fuction with .DTC files I program myself, that way I can personnalize the labels, choose a runway for landing points and add the "route désirée" I want.

With my code for Caucasus :

Quote

--atterissages ILS sur Caucasus

terrain = "Caucasus"
aircraft = "M-2000C"
date = "23/01/2003"
name = "ILS CAUCASE"

-- magnetic declination 6.6deg

waypoints = {}
waypoints[1] = { name="Batumi RWY13 110.3 16X", lat="N41:36:34", lon="E41:36:01", rd=126.6, cp=126.6, pd =3 }
waypoints[2] = { name="Belsan RWY10 110.5", lat="N43:12:20", lon="E44:36:21", rd=92.6, cp=92.6, pd =3 }
waypoints[3] = { name="Kobuleti RWY07 111.5 67X", lat="N41:55:47", lon="E41:51:48", rd=70.6, cp=70.6, pd =3 }
waypoints[4] = { name="Kutaisi RWY07 109.75 44X", lat="N42:10:39", lon="E42:28:53", rd=74.6, cp=74.6, pd =3 }
waypoints[5] = { name="Mineralyne RWY12 111.7", lat="N44:13:40", lon="E43:04:53", rd=115.6, cp=115.6, pd =3 }
waypoints[6] = { name="Nalchik RWY24 110.5", lat="N43:30:51", lon="E43:38:13", rd=235.6, cp=235.6, pd =3 }
waypoints[7] = { name="Senaki RWY09 108.9 31X", lat="N42:14:27", lon="E44:02:53", rd=95.6, cp=95.6, pd =3 }
waypoints[8] = { name="Sochi RWY06 111.1 31X", lat="N43:26:39", lon="E39:56:28", rd=62.6, cp=62.6, pd =3 }
waypoints[9] = { name="Tbilisi RWY13 110.3 25X", lat="N41:40:01", lon="E44:57:23", rd=128.6, cp=128.6, pd =3 }
waypoints[10] = { name="Vaziani RWY13 108.75 22X", lat="N41:37:44", lon="E45:01:38", rd=136.6, cp=136.6, pd =3 }

I got everything that I want to practice ILS landing with synthetic runway, another function I love, thanks again Razbam for this amazing mod.

My problem here is I don't manage to program cartridges for other terrains than Caucasus this way. I tried "Syria" or "PersianGulf" in the "terrain" argument, none of them worked. It works with .MIZ files but I cannot set all my parameters this way.

So I have a simple question. Is there a list of the values I am supposed to use in "terrain" for all terrain mods ?

 

[kablamoman]

I've made many carts for the Persian Gulf map and the terrain variable is indeed as you wrote it. ie. 

terrain = "PersianGulf"

I can confirm that works in the .dtc format, so may be worth double checking other things.

[RockMyRoot]

15 hours ago, kablamoman said:

so may be worth double checking other things.

Thanks for the advice, after research, my code was incorrect. It was missing a single comma in a waypoint parameter...

 

[RockMyRoot]

Dear all,

After getting difficulties to implement a Sinai map datacartridge and for the guys looking for it : terrain = "SinaiMap"

[grim_reaper68]

Hi just stupid question, where do you put your file to have those waypoints? Never saw a DTC file.

Edited December 2, 2023 by grim_reaper68

[Northstar98]

12 minutes ago, grim_reaper68 said:

Hi just stupid question, where do you put your file to have those waypoints? Never saw a DTC file.

It goes in Saved Games\Datacartridges and you should have an EXAMPLE.dtc file in there if you own the Mirage 2000.

[grim_reaper68]

No trace of an datacartridges folder in my saved games... Maybe i schould create it. I have the mirage 2000 in fact and found the example.dtc. So i suppose that i have to create my own dtc files or could they be made with the mission editor?

[Ramsay]

2 hours ago, grim_reaper68 said:

i suppose that i have to create my own dtc files or could they be made with the mission editor?

TL;DR:

AFAIK dtc files are more flexible as they can store Offset Waypoints (BAD), etc.

Using using the mission editor is simpler (just create a mission with a single M-2000C and set of way points).

Detail

The data cartridge is described on pages 276 - 277 of the current DCS M-2000C manual found in
• "DCS World\Mods\Aircraft\M-2000C\Doc\DCS M-2000C Flight Manual EN.pdf"

A data cartridge can be of 2 formats:
• A .miz mission file with a single Mirage 2000C inside it, programmed with the desired flight plan/waypoints.
• A .dtc data cartridge file in lua (lua is a programming language used by DCS) consisting of a few configuration variables and an array containing the flight plan.

This is an example of the datacartridge folder structure for the Mirage

Edited December 2, 2023 by Ramsay

[grim_reaper68]

I created the folder and put the Caucasus ILS into it. I can load it in the M2000. So if I undersand it correctly, to create a datacartridge with the mission editor, I need to create the flightplan with only the M2000 and after saving the mission, just have to move the miz file into the datacartridge folder, and then i can use it on other mission. is that correct? 

Edit: just made a test with a miz file, the waypoints started at 11 instead of 01... 

Edited December 2, 2023 by grim_reaper68

[Ramsay]

2 hours ago, grim_reaper68 said:

just made a test with a miz file, the waypoints started at 11 instead of 01... 

That is intended i.e. waypoints 11 - 19 from the data cartridge might define a combat area, alt flight plan, divert airfields, etc.
with waypoints 1-10 left free for the primary flight plan / airfields (This reflects how the data cartridge is used in RL).

RL Examples - Training Zone R55, 11 = Bullseye, 12-18 = Training Zone Boundary

Desert Storm

If the data cartridge has more than 10 waypoints - the imported data starts at waypoint 1 and overwrites/replaces any other coordinates already stored in the PCN.

https://forum.dcs.world/topic/309740-dtc-not-transferring-the-waypoint/?do=findComment&comment=5059012

 

Edited December 2, 2023 by Ramsay
Add RL Waypoint Examples

[grim_reaper68]

Ok, thanks for the information. I just made a test by creating my own DTC file, with waypoints from 1 to 10 and airfield coordinates from 11 to 20, it works fine! 

After a perfect flight, I just noticed some deviation from the synthetic runway with RockMyBoot DTC file. It appears that the correct heading for Kutaisi is at 74° and not 74.6°

[machinist_]

Because I am currently working on my own data cartridges ( .dtc format).
The goal is to create a data cartridge for each map and the ILS capable airfields.

Here all terrains I could test:
terrain = "Caucasus"
terrain = "Nevada"
terrain = "Normandy"
terrain = "PersianGulf"
terrain = "SinaiMap"
terrain = "Syria"

[Kercheiz]

Just go to Mods/terrains/XXX/entry.lua, and look at the ['id'] field, it should cover any present and future map.

[El Chapo]

Just for info, IRL weapons 1 to 10 are permanently stored in the INS and should not be changed unless in very particular cases, otherwise the next user will not find what's expected in the INS. 

It would be nice to have this feature in DCS, with for example in the INS the 10 closest airfields or something like that, with CP/PD, etc...

[machinist_]

@Kercheiz Thanks, I also discovered the beacons.lua and radio.lua.

@El Chapo My plan is to use only waypoints 11-20.
With the restriction to use only ILS capable airfields.
Is the number of waypoints on some charts sufficient.

[grim_reaper68]

At Al Dharfa AFB in Persian Gulf, I setup the ILS on the 13L and 31R with the correct heading (128° 109.10mhz and 308° 110.10mhz), but the ILS and the virtual airfield seems to be wrong. Altitude and coordinates of the airfield seems to be correct, also the runway headind and the 3° glideslope,  I can see the path for the ILS but never had the virtual airfield and glideslope tells me that I'm too high even at 100 ft above ground. Altimeter correctly setup. Nothing helps. A test at  Al Minhad AFB works fine.

Another strange thing is the ILS frequency: in the mission editor, ILS 13L is 111.10 MHz, but in game it tells that it's 109.10 (that is given for the 31R).

 

Even made a try with waypoint 3 as landing point, so coordinates are stored into the INS, never get to capture the glideslope. 

[Ramsay]

16 hours ago, grim_reaper68 said:

At Al Dharfa AFB in Persian Gulf, I setup the ILS on the 13L and 31R with the correct heading (128° 109.10mhz and 308° 110.10mhz), but the ILS and the virtual airfield seems to be wrong.

TL;DR:

Al Dhafra's ILS is bugged and has been for a long time - the issue effects all modules.

https://forum.dcs.world/topic/334755-al-dhafra-air-base-ils-issues/?do=findComment&comment=4411274

Detail:

To land at Al Dhafra (zero wind) using the Mirage's ILS / synthetic runway :-

1. Ignore ATC's instructions to land on 13L and plan to line up for 31R
2. Tune ILS to 109.10MHz
3. Prep Waypoint CP/PD = 308°T / 03.0° (if using a landing waypoint - it will have the wrong direction).
4. Line up on final for 31R (306°M) i.e. using TCN 96X
5. Follow normal landing procedures using APP mode, Autopilot, etc. as desired.
6. Once Localiser and Glide Slope are captured - the synthetic runway will appear in the HUD.

Tested using A-10C II and Mirage 2000C, DCS Open Beta Multi-thread 2.9.148335

Edited December 11, 2023 by Ramsay
Typo

[grim_reaper68]

Great news! thanks for the info

 

[RockMyRoot]

On 12/3/2023 at 1:15 AM, grim_reaper68 said:

After a perfect flight, I just noticed some deviation from the synthetic runway with RockMyBoot DTC file. It appears that the correct heading for Kutaisi is at 74° and not 74.6°

Hi Grim,

Thanks for noticing it. Headings in the M2000 INS waypoints includes magnetic declination (here 68° for RWY07 + 6.6°). Unfortunately magnetic declination changes depending the year of the mission you're playing, here my data cartridge is only relevant in 2012... 

Would be great if we could create variables in .dtc files, it would be easyer to adapt any circumstances :

Quote

 

md==6.6 -- magnetic declination 6.6deg

waypoints = {}
waypoints[1] = { name="Batumi RWY13 110.3 16X", lat="N41:36:34", lon="E41:36:01", cp=(120+md), pd =3 }
waypoints[2] = { name="Kutaisi RWY07 109.75 44X", lat="N42:10:39", lon="E42:28:53", cp=(68+md), pd =3 }

 

[grim_reaper68]

Ok, good to know it. So probably there must be a cartridge for every year. Including the missions, that would be a lot of cartidges to make... 

[Ramsay]

46 minutes ago, grim_reaper68 said:

So probably there must be a cartridge for every year.

No, set the cp value using it's TRUE heading, that doesn't change over time.