Seeking all available StaticTemplate ["theatre"] values for available terrains

[ChariotOfFLAME]

I have created a StaticTemplate propagation python script I plan on "releasing" in User Files designed to allow the use of Static Template created on one terrain to be used on all terrains (I understand this is not the intended use of Static Templates). The last piece I am missing is the full list of  ["theatre"] values that can be found at the end of any stm file (and/or the name of the terrain folders in DCS World/Mods/terrains).

Here is what I have so far:

• Caucasus
• Falklands
• Kola
• MarianaIslands
• Syria
• Nevada
• Channel
• PersianGulf
• Normandy
• Sinai
• GermanyCW (TY @Rudel_chw)
• Afghanistan (TY @Brother_Leb)
• Iraq (TY @Brother_Leb)

EDIT: this community is great! Thanks everyone! Here is the post where I shared the duplicator: 

 

Thanks!

Edited May 6 by ChariotOfFLAME

[Rudel_chw]

1 hour ago, ChariotOfFLAME said:

{{value for Cold War Germany}}

 

"GermanyCW"

 

(I don't have the other two maps)

[Brother_Leb]

Not very interesting but...

Iraq = "Iraq"
Afghanistan = "Afghanistan"

[ChariotOfFLAME]

Alright, I’ve got what I need! I’ll share the duplicator once I get back to a computer to finalize the code!

[Rudel_chw]

2 minutes ago, ChariotOfFLAME said:

Alright, I’ve got what I need! I’ll share the duplicator once I get back to a computer to finalize the code!

 

How will you handle the diverse coordinates origins to ensure that the duplicate template is at least within the visible part of the new map? 

My own templates are edited to work at a specific map location (an airbase, a flat spot for weapons range, a historical position for a SAM battery, etc) so I doubt that a straightforward duplicate would be really usable.

[ChariotOfFLAME]

14 minutes ago, Rudel_chw said:

 

How will you handle the diverse coordinates origins to ensure that the duplicate template is at least within the visible part of the new map? 

My own templates are edited to work at a specific map location (an airbase, a flat spot for weapons range, a historical position for a SAM battery, etc) so I doubt that a straightforward duplicate would be really usable.

Static Templates treat the unedited Neutral Bullseye as coordinates [0,0]. This used to be an issue, but now with the multiselect tool, one the steps to saving template for use elsewhere will be moving the units you want to use for the template as close to the original Neutral Bullseye as possible. After converting the file to all environments, when you import the static template, the units will spawn in that relative position to that map’s original Neutral Bullseye.

Due to Nevada having its NB at the very top of the visible map, I highly suggest placing the units directly BELOW NB so you can still see them when you load the template (though the multiselect tool will still work to nab those pesky units above the map)

[Rudel_chw]

2 minutes ago, ChariotOfFLAME said:

one the steps to saving template for use elsewhere will be moving the units you want to use for the template as close to the original Neutral Bullseye as possible.

 

OK, got it   ... seems I will be able to employ your tool to port at the very least my Fleets Templates  

[ChariotOfFLAME]

As promised, here is the duplicator: https://github.com/ChariotOfFLAME/DCS-StaticTemplateDuplicator
NOTE: think of this as a small-group duplicator; it is for use with things like SAM sites, static aircraft displays, beach clutter, etc. It is not for use with map-wide or airport-specific templates.

e.g. use it as a way to create re-usable templates for common groups of units you use frequently across missions in all theatres. As stated above:

On 5/1/2025 at 6:41 PM, ChariotOfFLAME said:

Static Templates treat the unedited Neutral Bullseye as coordinates [0,0]. This used to be an issue, but now with the multiselect tool, one the steps to saving template for use elsewhere will be moving the units you want to use for the template as close to the original Neutral Bullseye as possible. After converting the file to all environments, when you import the static template, the units will spawn in that relative position to that map’s original Neutral Bullseye.

Due to Nevada having its NB at the very top of the visible map, I highly suggest placing the units directly BELOW NB so you can still see them when you load the template (though the multiselect tool will still work to nab those pesky units above the map)

Hope you all like it!

Edited May 6 by ChariotOfFLAME